User:Laz orti

LSC Exploration

This guide is intend to establish practical guidelines and to offer a repository of information for exploration around the LSC. If you enjoy scanning down data and relic sites, sleeper caches, and combat signatures, please use this guide to ensure that your activities benefit your fellow LSCers and the broader E-Uni community.

General Exploration Resources

Exploration Overview
Exploration 101
Exploration Skills
Cosmic Signatures
Dotlan EveMaps
JonnyPew Exploration Videos

Bookmarking

Corporate Bookmarks
Always bookmark every probable site while you are out exploring around the LSC. Save the bookmarks in the LSC Exploration folder under Corporation Bookmarks.

• The goal is to maintain the quality and organization of our LSC Exploration bookmarks.
• Please be kind and take the time to fully scan down the system and to add proper bookmarks to LSC Exploration. This not only will help your fellow LSC explorers, but will also help you notice new cosmic signatures should you return to the system.
• Please only put proper bookmarks related to scanned-down cosmic signatures into the LSC Exploration folder. All other bookmarks belong in your personal bookmark folder.
• There is no need to add a bookmark to LSC Exploration if you are planning to immediately run the site that you've just found. Place the bookmark in your personal folder.
• The entire Corporation is limited to 500 Bookmarks. it is your job to clean up the OLD bookmarks! If you have a freshman title, you unfortunately cannot remove from the LSC Exploration folder any bookmarks that you haven't personally made. However, you can (and should) remove any bookmarks that you made that are no longer valid. Sophomores should remove any bookmarks that are no longer valid.

Bookmarking Scheme

In an attempt to have one E-Uni standard, the LSC will defer to the WHC and adopt the WHC Bookmarking Scheme.

Sites
Bookmarking sites that you will not run provides others in the LSC with the opportunity to run them, and also makes it easier for everyone to know if a new signature has appeared.

• If you scan down a combat site that you are not going to run, bookmark it and let people in fleet know. They may even send you a finder's fee if they decide to run it.
• If you do data and relic sites, please pop all of the cans so that the site despawns (and respawns elsewhere). For those cans that are empty or full of junk, just run your analyzer on it twice without doing the hacking game.
• Bookmarks can be made from the scanning results list. Right-click on a fully-scanned result and select "save."
• Standard format is <sigtype> [sig id] <additional info>, where:
  • <sigtype> = a one letter designation of the signature type; G for gas, R for relic, D for Data, and C for combat
  • [sig id] = [ABC], [BCD], [EFG], etc.; the first three letters of the signature id
  • <additional info> = the name of the site from the scanner; this is the default name that appears when you select save
• Examples:
  • R [ABC] Decayed Serpentis Mass Grave
  • C [DEF] Serpentis Hideout
  • G [GHI] Sparkling Nebula

Wormholes

• Take the time to warp to it at 100km. From your overview, right-click on the wormhole and select "show info" to see what you have. Indicate whether it is to High, Low, Null, or W-space in the <additional info>.
  • W [ABC] C1-C3
  • W [DEF] High
  • W [GHI] Null
• You can tell what type of wormhole space the wormhole leads to by looking at its description text.
• If you jump through the wormhole, please include specific <additional info>.
• DO NOT BOOKMARK wormholes from Scanner Results. Only bookmark wormholes while on-grid from your overview or in space.
  • Except: if you did not warp to the wormhole, bookmark it from the scanner results and keep the name as "Unstable Wormhole."

• 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.

Caution: if you use the destination system on * bookmarks they become confusing as we'll have all kinds of *Inn bookmarks for example which makes it hard to quickly see what can be deleted when chains collapse. As a side-benefit, you can always tell what system you're in by looking at the * bookmark.

Examples:

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

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

For end-of-life wormholes that the scanner doesn't want to jump into the format is .EOL {type of space is leads to} [Sig id]

Examples:

.EOL Low [VVV]

.EOL C4-C5 [WWW]

.EOL dangerous [XXX]

.EOL HS [YYY]

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.