WHC System Naming Scheme

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

Scheme

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 called the root name (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.

Connections

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

Syntax

Basic Mapper Naming Conventions

Every bookmark is made in the form:

[math]D\ RW(S)[/math]

Where:

• [math]D[/math] : The Depth of the chain - the number of jumps away from Innuendo.
• [math]R[/math] : 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)
• [math]W[/math] : The Width of the chain - representative of number of connections at that depth.
• [math]S[/math] : The Security Status of the system or if it leads to Triglavian controlled space. [Highsec, Lowsec, Nullsec, Triglavian]

Examples

• 2 B1L Represents
  • [math]D[/math] : System is 2 jumps out of Innuendo so Depth is 2
  • [math]R[/math] : The root system is named B (aka Bacon)
  • [math]W[/math] : This is the first connection of this depth
  • [math]S[/math] : L tells us that this is a low security system named Reyi.

• 3 B2 Represents
  • [math]D[/math] : System is 3 jumps out of Innuendo so Depth is 3
  • [math]R[/math] : The root system is named B (aka Bacon)
  • [math]W[/math] : The system at this depth is identified uniquely by the number 2.
  • [math]S[/math] : No special designation means it is a wormhole system

Naming

Root Name

Only the following letters may be used to name the root of a new chain starting off from Innuendo, that isn't one of the static connections Bacon or Eggs.

Z

Y

W

V

U

S

R

Q

O

M

I

G

D

A

Reserved Letters

Certain letters are reserved or are not used for chain names.

B	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	The prefix for the class of wormhole, and should not be used for a chain.
E	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	Reserved as it may be used on some mappers to denote a 'frigate' or small ships connection.
H	Reserved for indicating a system is a highsec system.
J	Already the embedded in the Eve name for a Wormhole system.
K	Used to refer to ksapce aka known-space.
L	Reserved for indicating a system is a lowsec system.
N	Reserved for indicating a system is a nullsec system.
P	Sounds too similar to "B" on voice comms.
T	Reserved for indicating a system is in the Pochven region.
X	Sounds too similar to "Eggs" on voice comms.

System Names in Chain

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 [math]D[/math] number by one.
• Each wormhole discovered in all systems at that depth increments the [math]W[/math] number by one.
• K-Space systems and wormholes are suffixed with H (for highsec), L (for lowsec), N (for nullsec) and T (for Triglavian space)
• If the chain has more than one defining letter, separate the last chain defining letter from the rest with "/" (forward slash). (Example: 2 B1/3 E2, when the same system is part of both Bacon and Eggs chains)

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. Increment [math]D[/math] by 1 relative to current system
6. Keep [math]R[/math] the same as current system
7. If there is another system scanned at the same depth as the one you are one check people and places to find the first available [math]W[/math] at that depth for the current chain, otherwise set [math]W[/math] to 1.
   • Remember to set H/L/N/T for highsec/lowsec/nullsec/triglavian respectively if the destination is known space
8. Go back to point 3

Example

Assume you are scanning in a fresh system. You have entered the system from 1 B1 (aka Bacon). You find 3 unexplored 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.

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.
• Difficult to Navigate: Names can be reserved for any amount of width at a certain depth which makes it harder to navigate full path without understanding the shortform.