Difference between revisions of "WHC System Naming Scheme"

From EVE University Wiki
Jump to: navigation, search
(Removing Meta tag. There is no need to refer to the mapper to explain the system naming scheme as it is agnostic to mapper used. Mapper specific denotation can be described in the mapper sections.)
 
(34 intermediate revisions by 12 users not shown)
Line 1: Line 1:
−
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!
+
{{eunispecific}}
 +
{{Wormhole Links}}
 +
The Wormhole Community 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
 
* This system naming scheme explains how we NAME SYSTEMS in wormhole space
−
* The [[WHC_Bookmarking_Scheme|bookmark naming scheme]] explains how we NAME BOOKMARKS in wormhole space
+
* The [[WHC Bookmarking Scheme|bookmark naming scheme]] explains how we NAME BOOKMARKS in wormhole space
−
* The [[WHC_What_To_Bookmark_Guide|what to bookmark guide]] explains WHAT SHOULD BE BOOKMARKED in wormhole space
+
* The [[WHC What To Bookmark Guide|what to bookmark guide]] explains WHAT SHOULD BE BOOKMARKED in wormhole space
  
  
−
{{TOClimit}}
+
== 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 <em>chain</em>.
 +
* Our home system is named <em>Cake</em>.
 +
* Our static C2 is always named <em>Alpha</em> and takes <em>A</em> as a root name.
 +
* Our static C3 is always named <em>Bravo</em> and takes <em>B</em> 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).
 +
* Alpha and Bravo are technically <em>1 A1</em> and <em>1 B1</em>, but the numbers can be omitted.
 +
* All other incoming or outgoing wormholes from Cake are assigned a unique letter to the map.
 +
* Position numbers get higher as you move further away from Cake.
 +
 
 +
==== Connections ====
 +
* We give names to ALL Connections, even if it's a gated connection! (this includes EOL connections)
 +
 
 +
=== Syntax ===
 +
[[File:WHC Naming Convention Pathfinder Final Final.png|thumb|alt=Screenshot of EVE UNI Mapper showing an example of how system names change with chain depth|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 Cake.
 +
* <math>R</math> : The Root of the chain - selected only for connections to Cake. (A is reserved for Alpha, and B is reserved for Bravo, all other letters are selected in reverse alphabetical order)
 +
* <math>W</math> : The Width of the chain - representative of the number of connections at that depth.
 +
* <math>S</math> : The Security Status of the system or if it leads to Triglavian controlled space.
 +
** {{Co|lime|<em>H</em>}}ighsec
 +
** {{Co|yellow|<em>L</em>}}owsec
 +
** {{Co|red|<em>N</em>}}ullsec
 +
** {{Co|cyan|<em>T</em>}}riglavian
 +
 
 +
==== Examples ====
 +
* <big>'''2 B1L'''</big> Represents
 +
** <math>D</math> : System is 2 jumps out of Cake so Depth is 2
 +
** <math>R</math> : The root system is named B (aka Bravo)
 +
** <math>W</math> : This is the first connection of this depth
 +
** <math>S</math> : {{Co|yellow|<em>L</em>}} tells us that this is a low security system named Reyi
  
−
==Scheme & Examples==
+
* <big>'''3 A2'''</big> Represents
−
[[File:WHCNamingConventionV2.png|600px|thumb|right|Basic Concepts of the naming convention]]
+
** <math>D</math> : System is 3 jumps out of Cake so Depth is 3
−
=== Basic Concepts ===
+
** <math>R</math> : The root system is named A
−
* '''System names'''
+
** <math>W</math> : This is the second connection of this depth
−
** All systems (in K- or W-space) on the mapper have assigned short, unique, code names.
+
** <math>S</math> : No special designation means it is a wormhole system
−
** 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 ===
+
=== Naming ===
−
* Every bookmark is made in the form: '''''D RW(S)'''''
+
==== Root Name ====
−
** '''''D'''''  : The Depth of the chain - the number of jumps away from Innuendo.
+
Only the following letters may be used to name the root of a new chain starting off from Cake, which isn't one of the static connections Alpha or Bravo.
−
** '''''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)
+
{| class="wikitable"
−
** '''''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]
+
| style="color: lime; font-size: larger;" | Z
−
* Certain letters are reserved or are not used for chain names.
+
| style="color: lime; font-size: larger;" | Y
−
** '''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.
+
| style="color: lime; font-size: larger;" | W
−
** '''C''' - "C" is the prefix for the class of wormhole, and should not be used for a chain.
+
| style="color: lime; font-size: larger;" | U
−
** '''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.
+
| style="color: lime; font-size: larger;" | S
−
** '''F''' - "F" is reserved as it may be used on some mappers to denote a 'frigate' or small ships connection.
+
| style="color: lime; font-size: larger;" | R
−
** '''H''' - "H" is reserved for indicating a system is a highsec system.
+
| style="color: lime; font-size: larger;" | Q
−
** '''J''' - "J" is already the embedded Eve name for a Wormhole system.
+
| style="color: lime; font-size: larger;" | O
−
** '''L''' - "L" is reserved for indicating a system is a lowsec system.
+
| style="color: lime; font-size: larger;" | M
−
** '''N''' - "N" is reserved for indicating a system is a nullsec system.
+
| style="color: lime; font-size: larger;" | K
−
** '''P''' - "P" sounds too similar to "B" on voice comms.
+
| style="color: lime; font-size: larger;" | I
−
** '''T''' - "T" is reserved for indicating a system is in the [[Pochven|Pochven]] region.
+
| style="color: lime; font-size: larger;" | E
−
** '''X''' - "X" sounds too similar to "Eggs" on voice comms.
+
| style="color: lime; font-size: larger;" | D
 +
|}
  
 +
===== Reserved Letters =====
 +
Certain letters are reserved or are not used for chain names.
 +
{| class="wikitable"
 +
|-
 +
| style="padding: 5px; color: red;" | A || Reserved for Alpha, and while it is used in our naming scheme, it is only to be used for Alpha and the Alpha chain.
 +
|-
 +
| style="padding: 5px; color: red;" | B || Reserved for Bravo, and while it is used in our naming scheme, it is only to be used for Bravo and the Bravo chain.
 +
|-
 +
| style="padding: 5px; color: red;" | C || The prefix for the class of wormhole, and should not be used for a chain.
 +
|-
 +
| style="padding: 5px; color: red;" | F || Reserved as it may be used on some mappers to denote a 'frigate' or small ships connection.
 +
|-
 +
| style="padding: 5px; color: red;" | G || Logistical terminology concerns, also sounds like both B and E.
 +
|-
 +
| style="padding: 5px; color: red;" | H || Reserved for indicating a system is a highsec system.
 +
|-
 +
| style="padding: 5px; color: red;" | J || Already embedded in the EVE name for a Wormhole system.
 +
|-
 +
| style="padding: 5px; color: red;" | L || Reserved for indicating a system is a lowsec system.
 +
|-
 +
| style="padding: 5px; color: red;" | N || Reserved for indicating a system is a nullsec system.
 +
|-
 +
| style="padding: 5px; color: red;" | P || Sounds too similar to "B" on voice comms.
 +
|-
 +
| style="padding: 5px; color: red;" | T || Reserved for indicating a system is in the [[Pochven]] region.
 +
|-
 +
| style="padding: 5px; color: red;" | X || Sounds too similar to "Eggs" on voice comms, the previous name for the Echo chain.
 +
|-
 +
| style="padding: 5px; color: red;" | V || Sounds too similar to "B" on voice comms.
 +
|}
  
−
* We give names to ALL Connections, even if it's a gated connection! (this included EOL connections)
+
==== 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 scanner's preference.
  
−
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.
+
* Every connection away from Cake increments the <math>D</math> number by one.
−
Each wormhole discovered in a system increments the '''W''' 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). If the chain has more than one defining letter, separate the last chain defining letter from the rest with "/" (forward slash).
+
* K-Space systems and wormholes are suffixed with {{Co|lime|<em>H</em>}} (for highsec), {{Co|yellow|<em>L</em>}} (for lowsec), {{Co|red|<em>N</em>}} (for nullsec) and {{Co|cyan|<em>T</em>}} (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 A2, when the same system is part of both Bravo and Alpha chains)
  
−
Here is a easier to read version of the decision making process. Note that it doesn't include the bookmarking scheme format.
+
==== System Naming Process ====
 +
Here is a easier to read version of the decision making process. Note that it doesn't include the bookmarking scheme format. See [[WHC Bookmark Naming Scheme]] for how to name bookmarks.
 
# Scan system
 
# Scan system
−
# Ignore the wormhole that leads back
+
# Warp to newly scanned wormhole
−
# Warp to wormhole
+
# Check wormhole info for where it leads to
−
# Check where it leads to
+
# Increment <math>D</math> by 1 relative to current system
−
# Name it as <current system name>, except:
+
# Keep <math>R</math> the same as current system
−
#*Increment the '''D''' value by one
+
# Check Locations in Neocom to find the first available <math>W</math> at that depth for the current chain, otherwise set <math>W</math> to 1.
−
#*If the name you now have is already used, keep incrementing the '''W''' value by one until it no longer is
+
#* Remember to set {{Co|lime|<em>H</em>}}/{{Co|yellow|<em>L</em>}}/{{Co|red|<em>N</em>}}/{{Co|cyan|<em>T</em>}} for highsec/lowsec/nullsec/triglavian respectively if the destination is known space
−
#*Remember to set H/L/N for highsec/lowsec/nullsec respectively if the destination is known space
+
# Go back to point 2
−
# Go back to point 3
+
 
 +
===== Example =====
 +
Assume you are scanning in a fresh system. You have entered the system from <em>1 B1</em> (aka <em>Bravo</em>). You find 3 unexplored wormholes and the 4th is your way back. You ignore the one that goes back towards Cake. If you were deeper in the chain, you would have checked Locations for the width of the chain at your current depth.
 +
 
 +
* The first wormhole you find leads to lowsec. You should name the system behind it <em>2 B1L</em>.
 +
** 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 <em>2 B2</em>.
 +
** 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
  
−
===Examples===
+
* The third wormhole you find leads to "unknown space". You should name the system <em>2 B3</em>.
−
=====Assume you are scanning=====
+
** 2: because 2 comes after 1 (1+1=2)
−
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;
+
** B: because you are in the B chain
−
*The first wormhole you find leads to lowsec. You should name the system behind it 2 B1L.
+
** 3: because it is the third (3rd) system you're naming
−
**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===
+
== 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.
+
Unsurprisingly, any mapping structure has certain trade-offs in readability, standalone performance, ease of naming as well as quite a few other considerations.
  
−
=====Advantages=====
+
==== Advantages ====
−
*'''Compact''': Compared to other schemes with the aforementioned quality, this scheme generates relatively compact names.
+
* <strong>Compact</strong>: 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.
+
* <strong>Unique System Names</strong>: Each system has a unique name so you can give a call out without fear of people going to a different system.
  
−
=====Disadvantages=====
+
==== 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
+
* <strong>Difficult to Learn</strong>: 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.
+
* <strong>Prone to Mistakes</strong>: 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.
 +
* <strong>Difficult to Navigate</strong>: Names can be reserved for any width at a certain depth, making it harder to navigate the full path without understanding the short form.
  
 
[[Category:Wormholes]]
 
[[Category:Wormholes]]
 
[[Category:WHC]]
 
[[Category:WHC]]

Latest revision as of 11:09, 19 April 2024

E-UNI Emblem.png This page is specific to EVE University. Other corporations or groups in the game may operate differently.
For a summary of EVE University's rules and code of conduct, see EVE University Rules.
Apocrypha sleeper.jpg
Wormholes
Life in wormholes
EVE University specific
Reference
NPCs
External links

The Wormhole Community 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 Cake.
  • Our static C2 is always named Alpha and takes A as a root name.
  • Our static C3 is always named Bravo and takes B 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).
  • Alpha and Bravo are technically 1 A1 and 1 B1, but the numbers can be omitted.
  • All other incoming or outgoing wormholes from Cake are assigned a unique letter to the map.
  • Position numbers get higher as you move further away from Cake.

Connections

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

Syntax

Screenshot of EVE UNI Mapper showing an example of how system names change with chain depth
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 Cake.
  • [math]R[/math] : The Root of the chain - selected only for connections to Cake. (A is reserved for Alpha, and B is reserved for Bravo, all other letters are selected in reverse alphabetical order)
  • [math]W[/math] : The Width of the chain - representative of the 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 Cake so Depth is 2
    • [math]R[/math] : The root system is named B (aka Bravo)
    • [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 A2 Represents
    • [math]D[/math] : System is 3 jumps out of Cake so Depth is 3
    • [math]R[/math] : The root system is named A
    • [math]W[/math] : This is the second connection of this depth
    • [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 Cake, which isn't one of the static connections Alpha or Bravo.

Z Y W U S R Q O M K I E D
Reserved Letters

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

A Reserved for Alpha, and while it is used in our naming scheme, it is only to be used for Alpha and the Alpha chain.
B Reserved for Bravo, and while it is used in our naming scheme, it is only to be used for Bravo and the Bravo chain.
C The prefix for the class of wormhole, and should not be used for a chain.
F Reserved as it may be used on some mappers to denote a 'frigate' or small ships connection.
G Logistical terminology concerns, also sounds like both B and E.
H Reserved for indicating a system is a highsec system.
J Already embedded in the EVE name for a Wormhole system.
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, the previous name for the Echo chain.
V Sounds too similar to "B" 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 scanner's preference.

  • Every connection away from Cake 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 A2, when the same system is part of both Bravo and Alpha chains)

System Naming Process

Here is a easier to read version of the decision making process. Note that it doesn't include the bookmarking scheme format. See WHC Bookmark Naming Scheme for how to name bookmarks.

  1. Scan system
  2. Warp to newly scanned wormhole
  3. Check wormhole info for where it leads to
  4. Increment [math]D[/math] by 1 relative to current system
  5. Keep [math]R[/math] the same as current system
  6. Check Locations in Neocom 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
  7. Go back to point 2
Example

Assume you are scanning in a fresh system. You have entered the system from 1 B1 (aka Bravo). You find 3 unexplored wormholes and the 4th is your way back. You ignore the one that goes back towards Cake. If you were deeper in the chain, you would have checked Locations for the width of the chain at your current depth.

  • 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 "unknown space". 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 width at a certain depth, making it harder to navigate the full path without understanding the short form.
Retrieved from "https://wiki.eveuniversity.org/index.php?title=WHC_System_Naming_Scheme&oldid=215024"