More actions
No edit summary |
|||
| Line 35: | Line 35: | ||
* <code>.D36 GKU HS eol crit</code> - a wormhole found in the D3 system leading away from Cake into a high-sec system. It has less than 10% of its mass remaining and is close to end of its lifetime. | * <code>.D36 GKU HS eol crit</code> - a wormhole found in the D3 system leading away from Cake into a high-sec system. It has less than 10% of its mass remaining and is close to end of its lifetime. | ||
* <code>.D36 GKU</code> - the same wormhole found several hours earlier, before many ships moved through it. This bookmarker chose not to add a system tag, which is perfectly fine. | * <code>.D36 GKU</code> - the same wormhole found several hours earlier, before many ships moved through it. This bookmarker chose not to add a system tag, which is perfectly fine. | ||
Rarely, wormholes can connect two systems which already exist in the chain. For these loops, do not modify either existing system and simply choose the older name to continue with (e.g., a newly-jumped wormhole leading from B32 linking to an existing system A15 would still have a *B32 bookmark in A15, but further wormholes would use the A15 prefix). This ''can'' lead to confusion if a loop is followed by the original chain is disconnected. No system is perfect, and renaming a whole chain is overly burdensome, so we simply live with these rare cases. | |||
=== Bookmarking Non-Wormhole Signatures === | === Bookmarking Non-Wormhole Signatures === | ||
| Line 58: | Line 60: | ||
Bookmarks dropped in space for navigation, often called “tactical bookmarks” or just “tacs”, should be prefixed with a <code>z</code> and a space, followed by whatever the pilot wishes. | Bookmarks dropped in space for navigation, often called “tactical bookmarks” or just “tacs”, should be prefixed with a <code>z</code> and a space, followed by whatever the pilot wishes. | ||
Tactical bookmarks dropped near a wormhole are still prefixed with <code>z</code> and a space, but are usually also given the name of the hole they are near. For instance, <code>z .A21 200km</code> might be a bookmark 200km away from the actual <code>.A21</code> bookmark. Bookmarks very far from a wormhole but still on grid | Tactical bookmarks dropped near a wormhole are still prefixed with <code>z</code> and a space, but are usually also given the name of the hole they are near. For instance, <code>z .A21 200km</code> might be a bookmark 200km away from the actual <code>.A21</code> bookmark. Bookmarks very far (at least 500km, but usually far more) from a wormhole but still on grid—commonly called “perches”—also generally use this scheme. For instance, <code>z .A21 perch</code> might be a bookmark 35,000km away from the <code>.A21</code> bookmark. Do not use a raw bookmark prefix for these tacs: use <code>z .A21 perch</code>, not just <code>.A21 perch</code>. | ||
=== Cleaning Up Bookmarks === | |||
'''Always''' set a 2-day expiration timer on your bookmarks. All wormholes have a lifespan of less than this, and EVE has a limit of 500 bookmarks per shared folder, so accumulating unreachable bookmarks is bad. | |||
When a part of the chain is disconnected and need not be saved, delete all wormhole bookmarks with the same prefix. For instance, if the Alpha wormhole in Cake has been rolled off, remove all bookmarks with a <code>.A</code> or <code>*A</code> prefix. Non-wormhole signatures do not need to be deleted. They will expire naturally two days after their creation if the expiration timer was set correctly. | |||
If the bookmarks in a chain do need to be preserved after it has been disconnected (someone has been rolled out, for instance), move all the bookmarks with the prefix of the disconnected chain into the "Isolated Chains" subfolder. Do not bother moving non-wormhole bookmarks, as the content is no longer relevant. They will expire naturally. Once the disconnected chain is no longer needed, delete all the related bookmarks in the "Isolated Chains" subfolder. | |||
=== Using Wanderer === | === Using Wanderer === | ||
[[File:Chain-example.png|800px|thumb|right|Example chain, as seen in Wanderer]] | |||
Every wormhole group relies on third-party tools for creating a visual map of their currently-connected space. These tools are commonly called "mappers". WHC uses a mapper called "Wanderer", and our server can be found here: [https://wanderer.eveuniversity.org/whc https://wanderer.eveuniversity.org/whc] | |||
==== Set up ==== | |||
When you open wanderer for the first time, you will be asked to log in. You may choose any character you have at WHC; more can be added later. Once you have logged in, select the "whc" map. You'll be presented with a chain like the example one to the right. | |||
If you wish to configure map options, use the gear icon in the bottom right. Of these, the most important options are "Widgets", which enable or disable various info panes in the interface. | |||
Click the "Characters Tracking" button on the left-hand side of the screen, then choose the "WHC" map. Click the checkbox next to each character. This allows your characters to show up on the mapper and help | |||
==== Creating a connection ==== | |||
=== | ==== Naming a system ==== | ||