WHC Bookmark Naming Scheme

Bookmarking

Corporate Bookmarks
Always bookmark every probeable site within the Home System. Save the Bookmarks in the Wormhole Campus folder under Corporation Bookmarks.

• When W-Space systems are removed from the Mapper, it is your Job to clean up the OLD bookmarks! The entire Corporation is limited to 500 Bookmarks.

Wormholes

Right click in space and look under Corporation bookmarks, The way back will be at the top, other WHs are listed below.

• Please add bookmarks in K-Space to contain the chain on the mapper.
• Note that it is current campus policy to bookmark all holes, including k-space connections into Innuendo (i.e. *Eggs, *Z1H, etc.)
• DO NOT BOOKMARK Wormholes from Scanner Results. Only Bookmark Wormholes while On-Grid from the Overview or in space.
• Just keep in mind when bookmarking that * gets the current system name while . gets the destination system name and you're good to go (see below).

Holes leading away from Innuendo

Wormholes which take you further away from Innuendo are marked with a leading . (period), and to facilitate navigation and easy of removal we add the destination system name.

Examples:

Wormhole	Bookmark
Innuendo -> Bacon	.Bacon [XYZ]
Innuendo -> Eggs	.Eggs [XYZ]
Bacon -> B2L	.B2L [MNO]
B2 -> B/D1	.B/D1 [STU]

Holes leading toward Innuendo

We mark the way home with a leading * (i.e. the star guides you home), and to facilitate ease of removal we add the current system name. Note that except for certain very rare cases, the bookmark for a hole heading "home" is unique for a given system.

NOTE: Do not use the destination system on * bookmarks. As a side-benefit, you can always tell what system you're in by looking at the * bookmark. NOTE 2: When you first enter a system, you will not know the sig ID, so enter it as [***] so people remember to add the ID once the system has been scouted and scanned. Examples:

Wormhole	Bookmark
Bacon -> Innuendo	*Bacon [***]
Bacon -> Innuendo	*Bacon [XYZ]
B2L -> Bacon	*B2L [XYZ]
B4 -> B3	*B4 [MNO]
B/D1 -> B2	*B/D1 [STU]

End-of-life, Shink, and Crit Wormholes (that are mapped)

If a wormhole is end-of-life, shrink, or crit, we denote it in the mapper (by clicking on the wormhole connection) and denote it in the bookmark by appending EOL, SHRINK, or CRIT.

Examples:

Wormhole	Bookmark
Bacon -> Innuendo	*Bacon [XYZ] EOL
B2L -> Bacon	*B2L [XYZ] CRIT EOL
B4 -> B3	*B4 [MNO] SHRINK

End-of-life and Crit Wormholes (that are not mapped)

For end-of-life and crit wormholes that the scanner doesn't want to jump, use the following format .WH [Sig id] EOL {type of space is leads to} or .WH [Sig id] CRIT {type of space is leads to}

Examples:

.WH [VVV] EOL Low

.WH [WWW] EOL C4-C5

.WH [XXX] CRIT C6

.WH [YYY] EOL CRIT HS

NOTE: "unknown space" is C1-3, "dangerous unknown space" is C4-5, and "deadly unknown space" is C6.

Gate to gate connections

Sometimes when we find a k-space connection, we jump through a gate into the next system to look for more connections, if we find a connection we Bookmark the gates for ease of travel.

Examples:

Gate Connection	Bookmark
Eggs -> E2H	.E2H [Gate]
E2H -> Eggs	*E2H [Gate]
Z1L -> Z2L	.Z2L [Gate]
Z2L -> Z1L	*Z2L [Gate]
Y1N -> Y2N	.Y2N [Gate]
Y2N -> Y1N	*Y2N [Gate]

We do this purely because the transition between using bookmarks in w-space for travel and movement and using gates on the overview is jarring and when you jump into Eggs looking for E2 and you can't find it due to it being a gate is annoying and opposing to our mapping scheme which was created so we don't need to rely on the mapper tool.

Deleting bookmarks

When holes collapse, you need to delete any bookmarks that were related to that chain (unless someone is stuck in that chain and still needs them in which case that person should delete them once they're out). Assuming the bookmarks were named properly, if a connection collapses with a given system name (e.g. B/C1), you should be able to safely delete all bookmarks with the name of that chain in it (B/C-anything in this case).

This is why it is important that * bookmarks have the current system name rather than destination. Otherwise you could have lots of *Inn bookmarks which require you to start looking at actual J-system names to know what needs deleting. EOL wormholes that haven't been explored aren't labelled well in that regard; however, there are typically no issues deleting them as no one has been in there anyway.

IMPORTANT NOTE: With the addition of Null sec data and relic sites, they spawn often and are run quickly. Remember to delete the bookmark and the mapper entry when you complete a site.

Sites

Due to the recent increase in corp bookmarks (250 -> 500), you can feel free to bookmark sites in systems in our chains as you would normally do in Bacon.

Here are some things to keep in mind though: for example, if a system, let's say a C4 which is 8 jumps down the chain, has 27 gas sites and they are not anything that we would care to huff, there is no need to bookmark them in corp.

The basic idea is that having gas/data/relic bookmarks in many systems not too far down our chains not only provides us the opportunity to possibly run them but also (and this, in my opinion, is a bigger selling point) provides quick warp-in points on any gank-gable fleets running said sites - without having to drop combat probes and very likely spooking them.

So again; feel free to bookmark sites in W-Space systems other than Bacon (and even in Low/Null if you find something that is likely to be run by locals). Just be mindful that we still don't have an unlimited number of corp bookmarks so don't go crazy if you see that we're closing in on 500.

• Bookmarks can be made from the scanning results list
• Standard format is "<sigtype> [sig id] <additional info>"
  • [sig id] = [ABC], [BCD], [EFG], etc
• There are 3 types.

1. G(as Sites)

• In C5 or C6 systems: if you choose not to bookmark anything else (besides WH connections, of course), please at least always bookmark the Instrumental or Vital Gas sites.
• Only the first word is important
  • G [ABC] Barren
  • G [DEF] Token
  • G [DEF-2] Bountiful
  • G [GHI] Vast
  • G [NMD] Instrumental (Only found in C5, C6 class W-Space)
  • G [YUI] Vital (Only found in C5, C6 class W-Space)

2. R(elic Sites)

• The first 2 words should be omitted.
• Forgotten Frontier Recursive Depot.
  • R [HJK] Quarantine Outpost
  • R [GHT] Recursive Depot
  • R [JHI] Conversion Module
  • R [ADH] Evacuation Center

3. D(ata Sites)

• The first 2 words should be omitted.
• Unsecured Frontier Database.
  • D [ADF] Database
  • D [DHI] Receiver
  • D [FHI] Digital Nexus
  • D [FJO] Trinity Hub

4. N(ull Sites)

• Pirate Faction sites can be labelled "Null" or the faction name (IE: Angel) as there are no RATS.
  • NR [ABC] Angel
  • NR [DEF] NULL
  • ND [GHI] Serpentis

5. C(ombat Sites)

• When in k-space, Cosmic Signatures can be Combat sites. If they are to be bookmarked, use the initial C. If they are a DED site, they should be named by DED-rating and pirate faction.
  • C [ISO] Radiance
  • C [FOP] Gurista Outpost
  • C [SVV] 6/10 Blood
  • C [SVV] 4/10 Angel

Scanning and the Adorable Newbro

As a newbro in the Wormhole Campus, it is essential that you follow the naming scheme and bookmarking scheme to the letter. There are certain scouting aspects to scanning in a wormhole as well. Here is a summarized lowdown of what you should do when "scanning out a chain" as we call it in wormhole parlance. Note that the below steps are best executed in a covert ops ship.

• D-Scan - D-Scan is your best friend. When you are in a wormhole, ready to scan, first do a maximum D-scan. If you see any of the following:
  • Probes (core or combat) - Probes may not be easy to pin down, but in a scanned wormhole, you can figure out which signature is being scanned and warp to it to potentially identify the offending covert ops/cloaked ship.
  • Ships
  • Force Fields
• Force fields - Rule no. 1 of scanning in a wormhole - first identify its occupants. That means, find out where the active control towers are an add/update them on the mapper. Some moons may be out of D-scan range; note them down, and warp to those planets to check if they have force fields. We are interested only in active POSes - which is why we are looking for force fields.
• Ships - once you identify the active POSes, if you saw any ships on D-scan, verify that they are in the POS. If not, it gets really interesting - they may lead to PvP content!!!
  • If the ships are unpiloted in a POS, make a note in the mapper.
  • If the ships are piloted in a POS, keep an eye on them. Ask for help in mumble/WHC etc to get a support fleet in case they leave the POS.
  • If the ships are not in a POS - D-scan them down! Once you have an idea where they are, ping for PVP on the WHC Campus Slack. If the wormhole has been scanned down already, warp to the data and relic sites first, and then warp to the cosmic anomalies to get on grid with the fleet. Try to provide a good warpin for your waiting friends!
• IF the POSes are all quiet and there are no piloted ships on D, then you can drop your probes and start scanning all the signatures in the wormhole.

Keep an eye out on D-scan though - you never know what could pop up :)

Now that you have scanned down the signatures, follow the naming convention to name the sites and wormholes. If you claim a new letter for the wormhole chain - announce it in mumble or fleet chat - eg, "Claiming P Chain". When you jump into a new wormhole, rinse and repeat.