WHC System Naming Scheme

This page should be updated due to game changes.
Reason: Page needs an overhaul due to new EVE Uni Mapper

The Wormhole Campus uses a set of rules and guidelines to generate logical names for the many Wormhole Space systems it might be connected to. The original names of the systems (aka J-Sig) are difficult to convey over comms and chat, so we use better ones!

• This system naming scheme explains how we NAME SYSTEMS in wormhole space
• The bookmark naming scheme explains how we NAME BOOKMARKS in wormhole space
• The what to bookmark guide explains WHAT SHOULD BE BOOKMARKED in wormhole space

Template:TOClimit

Scheme & Examples

Basic Concepts of the naming convention

Basic Concepts

• System names
  • All systems (in K- or W-space) on the mapper have assigned short, unique, code names.
  • Their name depends on their position in a chain.
  • Our home system is named Innuendo (often shortened to Innu).
  • Our static C3 is always named Bacon and takes B as a root name.
  • Our static Highsec is always named Eggs and takes E as a root name.
• Chain
  • A chain is a list of systems each connected to the next by a wormhole.
  • Each chain has a unique identifier (usually a single letter, chosen in reverse alphabetical order).
  • Eggs and Bacon are technically 1 E1 and 1 B1, but the numbers can be omitted.
  • All other incoming or outgoing wormholes from Innuendo are assigned a unique letter to the map.
  • Position numbers get higher as you move further away from Innuendo.

Rules

• Every bookmark is made in the form: D RW(S)
  • D : The Depth of the chain - the number of jumps away from Innuendo.
  • R : The Root of the chain - selected only for connections to Innuendo. (B is reserved for Bacon, and E is reserved for Eggs, all other letters are selected in reverse alphabetical order)
  • W : The Width of the chain - representative of number of subchains / connections within a system.
  • S : The Security Status of the system - this is only relevant for K-space systems [(H)ighsec, (L)owsec, (N)ullsec]
• Certain letters are reserved or are not used for chain names.
  • B - This is reserved for Bacon, and while it is used in our naming scheme, it is to only be used for Bacon and the Bacon chain.
  • C - "C" is the prefix for the class of wormhole, and should not be used for a chain.
  • E - This is reserved for Eggs, and while it is used in our naming scheme, it is to only be used for Eggs and the Eggs chain.
  • F - "F" is reserved as it may be used on some mappers to denote a 'frigate' or small ships connection.
  • H - "H" is reserved for indicating a system is a highsec system.
  • J - "J" is already the embedded Eve name for a Wormhole system.
  • L - "L" is reserved for indicating a system is a lowsec system.
  • N - "N" is reserved for indicating a system is a nullsec system.
  • P - "P" sounds too similar to "B" on voice comms.
  • T - "T" is reserved for indicating a system is in the Pochven region.
  • X - "X" sounds too similar to "Eggs" on voice comms.

• We give names to ALL Connections, even if it's a gated connection! (this included EOL connections)

Each W-Space system is named as a derivative of the previously discovered adjacent system. Wormholes are bookmarked in order of discovery or the scanners preference. Every connection away from Innuendo increments the D number by one. Each wormhole discovered in a system increments the W number by one. K-Space systems and wormholes are suffixed with H (for highsec), L (for lowsec), N (for nullsec). If the chain has more than one defining letter, separate the last chain defining letter from the rest with "/" (forward slash).

Here is a easier to read version of the decision making process. Note that it doesn't include the bookmarking scheme format.

1. Scan system
2. Ignore the wormhole that leads back
3. Warp to wormhole
4. Check where it leads to
5. Name it as <current system name>, except:
   • Increment the D value by one
   • If the name you now have is already used, keep incrementing the W value by one until it no longer is
   • Remember to set H/L/N for highsec/lowsec/nullsec respectively if the destination is known space
6. Go back to point 3

Examples

Assume you are scanning

in a fresh system. You have entered the system from 1 B1 (aka Bacon). You find 3 unscouted wormholes and the 4th is your way back. You ignore the one that goes back towards Innuendo;

• The first wormhole you find leads to lowsec. You should name the system behind it 2 B1L.
  • 2: because 2 comes after 1 (1+1=2)
  • B: because you are in the B chain
  • 1: because it is the first (1st) system you're naming
  • L: because it leads to lowsec
• The second wormhole you find leads to "dangerous unknown space". You should name the system 2 B2.
  • 2: because 2 comes after 1 (1+1=2)
  • B: because you are in the B chain
  • 2: because it is the second (2nd) system you're naming
• The third wormhole you find leads to another C3. You should name the system 2 B3.
  • 2: because 2 comes after 1 (1+1=2)
  • B: because you are in the B chain
  • 3: because it is the third (3rd) system you're naming

Pros & Cons

Unsurprisingly, any mapping structure has certain trade-offs in readability, standalone performance, ease of naming as well as quite a few other considerations. Here's a list of the advantages and disadvantages to our mapping scheme.

Advantages

• Compact: Compared to other schemes with the aforementioned quality, this scheme generates relatively compact names.
• Unique System Names: Each system has a unique name so you can give a call out without fear of people going to a different system.

Disadvantages

• Difficult to Learn: Compared to mapping schemes where each chain isn't differentiated, players might end up going through 2 B1 to get to 3 B2 but it might actually be in 2 B2
• Prone to Mistakes: Due to the chance of having multiple scanners naming a system will need to be called out over comms and in fleet chat so that somebody knows that the name has been taken and does not get used.