https://wiki.eveuniversity.org/api.php?action=feedcontributions&user=Zokr+McLan&feedformat=atomEVE University Wiki - User contributions [en]2024-03-28T14:11:57ZUser contributionsMediaWiki 1.33.1https://wiki.eveuniversity.org/index.php?title=Incursions&diff=147980Incursions2019-11-01T22:42:37Z<p>Zokr McLan: /* Number of Incursions and respawns */ Only 1 HiSec Spawn</p>
<hr />
<div>{{Incursions links}}<br />
{| style="border:1px solid #582806; background:#000000; margin:1em;"<br />
| valign="middle" style="padding:8px;" | [[image:Incursionlogosmall.png|64px|link=http://wiki.eveuniversity.org/EVE_University_Incursion_Community]]<br />
| valign="middle" style="padding:5px;" | This is a page about '''Incursions''' in general. If you are looking to join or just get more information about the [[EVE University Incursion Community]] then follow that link, as we have additional roles that do not require any specific skills (which are perfect for new players) and we do things slightly different from public communities to both accommodate for new player and the fact we're almost always at war.<br />
|}<br />
= What are Incursions? =<br />
Incursions are automated events introduced with the '''Incursion''' expansion in which the NPC faction known as the [[Sansha's Nation]], led by '''Sansha Kuvakei''', invade space in an attempt to conquer it for themselves. Capsuleers must fight off Sansha's forces in order to return the contested space back into an area which can be more safely occupied.<br />
<br />
==== High-end PvE fleet content ====<br />
Incursions are high-end PvE fleet content, well above that of regular level four missions and have more in common with level five missions than anything else. The introduction of incursions to the game added some much needed incentive for fleet content in highsec. It also gave people a very controlled environment to train up their skills as a logistics pilot as well as giving people a feel for organized fleets outside of general PvP.<br />
<br />
Contrary to missions, incursion fleets rely on buffers and resists supported by logistics ships in order to survive. The ships you face in incursions use electronic warfare, capacitor warfare as well as playing on speed and signature to their advantage. This forces incursion fleets to find ways around that in order to be successful.<br />
<br />
Due to the restrictions to fleet size, each member of the fleet matters. You cannot compensate for lack of skill or efficiency by simply adding more ships. As such, incursions are not for the brand new player, but more geared towards those who've spent at least a few months in the game able to fly '''battleships''', '''logistics''' or more advanced ships.<br />
<br />
==== A lucrative endeavour ====<br />
Incursions in highsec are a very profitable activity, assuming you find a community that runs continuous fleets. A normal fleet running vanguard sites can make about 60 million ISK per hour running sites; more advanced fleets have the potential of making 100+ million ISK per hour. Some of the public communities who specialize and exclusively run the larger headquarter sites can easily break 200+ million ISK per hour. Incursions also give you CONCORD loyalty points.<br />
<br />
See [[Incursion sites]] for more details about payouts and how these sites differ from each other.<br />
<br />
==== Nomadic in nature ====<br />
Incursions are nomadic by nature with a single focus lasting anywhere from a day up to over a week, forcing the incursion community to constantly move in order to continue taking part of the content. See [[#Spawn mechanics of Incursions|Spawn mechanics of Incursions]] below for more information on the spawn mechanics, or the [[How to find Incursions]] for more information on how to find them and safely move between incursions.<br />
<br />
==== Communities ====<br />
Since joining the same corporation or alliance would leave you wide open for war declarations, incursion runners remain in their corporations and alliances and instead affiliate themselves with various communities. Most communities operate in the same way: They have a public channel that anyone can join with all the information a pilot might need being available in their channel's message of the day. Fits are usually available through mailing lists or some other way that is readily available.<br />
<br />
EVE University maintains an active Incursion Community of current unistas, alumni and their alts. This community is one of the oldest Incursion communities in EVE Online and is one of the only communities to run under an almost constant state of war. This near constant state of war along with our primary focus of teaching has lead to slightly different operating procedures compared to other communities. We also have roles that do not require any specific skills, that other communities simply don't need or want. See the [[EVE University Incursion Community]] page for more information.<br />
<br />
== Lore ==<br />
{|<br />
| valign="top" | The following quote is from the EVE Chronicle [https://fiction.eveonline.com/stories/chronicles/uplifted Uplifted]:<br><br><br />
{{quote|Then the wormhole let out a searing burst of white light, and they came through, bulbous metallic vessels covered in wicked, uneven spines. Hundreds poured from the shimmering portal, covering light years of distance in a single instant to cloud the skies above the helpless planet. Almost fishlike, darting in loose formation and changing direction simultaneously, they spread out in all directions. With synchronized releases of focused electromagnetic blasts, they smoothly wiped all defensive structures and communications satellites from orbit. For many people on the surface, the sudden glare of golden laser beams lancing across the night sky was the first sign that Sansha’s Nation had arrived.<br />
<br />
When it had secured the entire lower orbital altitude, the armada held position until a second wave of ships emerged from the wormhole. These new vessels were different, though, lacking the bulky warp drives that took up so much space in the combat vessels; instead, their cavernous cargo holds had a very specific purpose, housing rows and rows, layer upon layer of holding cells designed to store humanoid “passengers”. The ships dropped through the atmosphere unimpeded, by squadrons, a perfectly orchestrated meteor shower.}}<br />
| valign="top" |<br />
[[image:CDIA_Files_Sansha.png|thumb|right|250px|CCP has released both the [http://www.youtube.com/watch?v=ejX0Rym0NZw&list=PLF614A7A6461E61E1 Incursion trailer] and the [http://www.youtube.com/watch?v=nJKcK-Fv80I&list=PLF614A7A6461E61E1 CDIA Files: Sansha Incursions] videos concerning Sansha Kuvakei and Incursions. They also made a more cinematic version of Incursions, called [http://www.youtube.com/watch?v=YezGrLuosg0 Incursion - Cinema Cut].]]<br />
|}<br />
<br />
= Effects of Incursions =<br />
[[image:incursions_info_panel.png|thumb|275px|This incursion information shows in all systems, letting you know there is an incursion going on. It also shows what kind of system it is, the current influence and if the mothership has been sighted yet.]]<br />
When a constellation comes under the siege from Sansha's forces, the sirens sound in your Captain's Quarters to warn you; the nebulae gets a brownish hue making it obvious that something is different; beacons will appear in your overview; rats are replaced, and you suffer system wide penalties, which all make it harder to continue your usual business in not just the system but the entire constellation.<br />
<br />
Read more about the actual sites and how many people it takes to run them on the [[Incursion sites]] page, or continue reading if you're just interested in how this affects you being in, or just passing through, an incursion constellation.<br />
<br />
The image to the right is an example of what the information panel might look like. The panel will have different names pending on the style of incursion system. In addition to ''"Sansha Vanguard"'', there are also ''"Sansha Staging"'' and ''"Sansha Headquarters"''. Clicking on the ''"Incursion Profile"'' part takes you to the '''Journal''' and '''Loyalty Point Log'''.<br />
<br />
Once the Sansha forces withdraw from the constellation or the [[Incursion sites#Mothership sites|mothership site]] is finished, the incursion is over; the information panel will then disappear, and things immediately go back to normal.<br />
<div style="clear: both"></div><br />
== Constellation Penalties ==<br />
During an incursion there are constellation wide penalties. The strength of the tank and weapon penalties are tied to both the level of activity and how much influence Sansha's forces have in the constellation. As players run sites, the Sansha's influence drops, and along with it, the penalties until they are effectively cancelled at zero influence.<br />
{|<br />
| valign="top" | [[image:icon_incursion_effect_cyno.png]]<br />
| valign="top" style="padding-bottom:8px;" | '''{{co|coral|System-wide cynosural field jammers are in effect.}}'''<br>Cynosural field jamming has no impact in high security space, but can be quite damaging for a nullsec alliance if one of their logistics hubs is locked down. This penalty is absolute and always in effect even at zero influence, but does not stop you from lighting a covert cynosural field.<br />
|-<br />
| valign="top" | [[image:icon_incursion_effect_bounties.png]]<br />
| valign="top" style="padding-bottom:8px;" | '''{{co|coral|Financial systems compromised. 50% reduction in CONCORD bounties.}}'''<br>The 50% reduction in CONCORD bounties are always in full effect and doesn't scale with the influence.<br />
|-<br />
| valign="top" | [[image:icon_incursion_effect_resists.png]]<br />
| valign="top" style="padding-bottom:8px;" | '''{{co|coral|Vessel integrity compromised. Shield and armor resistances reduced.}}'''<br>At full influence, a Vanguard system suffers a 10% penalty to resists. In Assaults the penalty is 25% and in Headquarter systems the penalty is as much as 50% penalty to your resists. Due to the way resists work, it practically means that a ship with resist of 73% drops to 70% in Vanguard, 66% in Assaults and as low as 59% in Headquarter sites. Semantics aside you ultimately do take up to 10%, 25% or 50% more damage depending on the type of system you're in and the level of influence.<br />
|-<br />
| valign="top" | [[image:icon_incursion_effect_damage.png]]<br />
| valign="top" style="padding-bottom:8px;" | '''{{co|coral|Capsule interference detected. Turret, launcher, drone and smartbomb damage reduced.}}'''<br>At full influence, you do 10% less damage in Vanguards, 25% less damage in Assaults and as much as 50% less damage in Headquarter sites.<br />
|}<br />
<br />
These penalties apply to everyone within an Incursion Constellation regardless of whether or not they are actively resisting Sansha's Nation.<br />
<br />
== Native spawns are replaced ==<br />
Whenever a constellation is under an incursion, the normal belt rats as well as the rats that spawn in ice belts will be replaced by Sansha Incursion rats. These NPCs will be much stronger, tougher, more deadly than your run of the mill Sansha Mission rats and mining ships; weaker combat ships will stand no chance against them. The rats that spawn in ice belts tend to be larger cruiser- or even battlecruiser-sized ships.<br />
<br />
All the mission rats and exploration site rats will remain the same, but if you linger in a completed site or a cleared out pocket, eventually regular rats will spawn every once in a while, and they will be replaced by the Sansha Incursion rats.<br />
<br />
Due to the native spawns being replaced and the constellation penalties added, certain activities are discouraged. For example, it's very inefficient to do [[Missions|missions]] because your income from bounties are cut in half. [[Mining]] is also not advised due to the native rats being replaced by much stronger Sansha Incursion rats, not to mention all static belts are turned into [[Nation Industrial Proxy]] scout-sites. [[Exploration]] however, can often be done without much trouble. Just don't linger too long in a finished site as Sansha will eventually spawn there too (see above).<br />
<br />
The [[Constellation layouts for Incursions]] page contains a list of all <b>known</b> Incursion Constellations and pages like [http://evemaps.dotlan.net/incursions dotlan] and [http://incursions.shadowlauch.de/ Shadowlauch] show active incursions. So while spawning is random for incursions it is quite easy to avoid them entirely.<br />
<br />
== Gate camps in low and null security space ==<br />
In low and null security space, the constellations under incursion will have Sansha ''"gate camps"'' for lack of a better word. There will be groups of Sansha Incursion rats at gates in these system, catching people unaware of the danger they pose. It is easy to mistake these for normal rats and under-estimate how hard they are to kill, and most importantly, how much of a punch they pack. See the anatomy page for a list of [[Anatomy_of_Incursions#Facilitating_a_controlled_warp-out|warp disruptor capable]] incursion rats, or the [[Sansha's Manual]] for more information about all of them.<br />
<br />
Please keep in mind that Sansha rats are much tougher than normal rats and may prove difficult for lone ships or poorly equipped fleets to handle, it is advised to avoid Incursion systems in low and null security space when possible to avoid unnecessary losses.<br />
<br />
= Spawn mechanics of Incursions =<br />
While it is impossible to predict exactly where a new spawn may occur, or exactly how long it'll last, there are several aspects of their spawn mechanics that are systematic and easy to predict.<br />
<br />
== Number of Incursions and respawns ==<br />
{{note|The '''Invasion''' patch on May 28th 2019 made some changes to incursion spawns. It was not properly documented, just mentioned on the [https://support.eveonline.com/hc/en-us/articles/360005796699-Triglavian-Invasion Triglavian Incursions] support page where it said ''"lowering the amount of available Sansha Incursions"''. We're still waiting to see the full effect of the changes, but it looks like highsec incursions are limited to a single constellation while low- nullsec incursions remain the same.}}<br />
There can be up to five incursions up at any given time, one in highsec and four in low- and nullsec. The incursions will all spawn new incursions in the same type of security space as the one they are replacing. This means that whenever a highsec incursion is despawned, either by Sansha withdrawing or when someone finishes the mothership site, a new highsec incursion will soon spawn in its place.<br />
<br />
The delay between an incursion ending and a new one spawning is [http://community.eveonline.com/news/dev-blogs/incursion-changes-in-hyperion/ 12 - 36 hours according to CCP], but there has been respawns recorded to have been delayed for far longer than 36 hours.<br />
<br />
== Constellation layouts ==<br />
While the incursions will spawn in a random constellation, the systems of a given constellation will always have the same type of sites. There is only one requirement for a constellation to be a potential incursions constellation it must have at least 6 systems with the same security status (high, low, null), some systems are also taken out of the ''"incursion rotation"'', such as major trade hubs and starter systems.<br />
<br />
See [[Constellation layouts for Incursions|constellation layouts]] for more information on what systems will have vanguard, assault or headquarter sites, without having to visit the constellation first.<br />
<br />
== Longevity ==<br />
Incursions can theoretically last close to eight days (but realistically last much less), and go through three different stages; {{co|lightgreen|Established}}, {{co|coral|Mobilized}} and {{co|crimson|Withdrawing}}.<br />
{| class="wikitable" style="font-size:90%;"<br />
|- valign="top" align="center"<br />
! align="left" valign="top" style="background:#222222;" | Stage<br />
! align="left" valign="top" style="background:#222222;" | Explanation<br />
|- valign="top"<br />
| nowrap align="center" style="background-color:#111111;" | '''Incursion {{co|lightgreen|established}}'''<br>(up to 5 days)<br />
| Whenever an incursion spawns, this will be the first stage. Sansha Kuvakei's forces are trying to take control of the systems. While beating down the influence seems to increase the chance of a this stage lasting longer, the exact mechanics are unknown (ie, this can be as short as a day).<br />
|- valign="top"<br />
| nowrap align="center" style="background-color:#111111;" | '''Incursion {{co|coral|mobilized}}'''<br>(2 full days)<br />
| The incursion has been around for a bit and Sansha Kuvakei's forces are either getting ready to finish off the incursion or they are losing too much ground and prepare to withdraw from the constellation. This phase always lasts 48 hours unless someone runs the mothership site prematurely.<br />
|- valign="top"<br />
| nowrap align="center" style="background-color:#111111;" | '''Incursion {{co|crimson|withdrawing}}'''<br>(1 full day)<br />
| The incursion is ending, either due to Sansha Kuvakei's forces overrunning the constellation or because the incursion community managed to keep them at bay. If the mothership site is not completed within 24 hours, the incursion simply disappears (and no loyalty points are paid out).<br />
|}<br />
<small><references /></small><br />
==== Mothership sighted ====<br />
The mothership site can occur as early as within the first {{co|lightgreen|established}} stage, the influence only needs to hit 0% and a single headquarters site must be run. Once the mothership has been sighted, the incursion can be ended by destroying the mothership at any time. As such there is no guaranteed longevity for incursions, other than the brief period before the mothership site is unlocked (which can be mere hours).<br />
<br />
==== Community drama ====<br />
Sometimes it's a tactical decision in order to spawn a new incursion for the weekend. Other times they just try to beat the crowd and do it just before it enters the {{co|crimson|withdrawing}} stage. Sadly, sometimes they finish the mothership site several days in advance for various personal reasons, often contributed to petty things like hurt egos and lost competitions.<br />
[[Category:Incursions]]</div>Zokr McLanhttps://wiki.eveuniversity.org/index.php?title=Nation_Rebirth_Facility&diff=147417Nation Rebirth Facility2019-10-05T12:02:32Z<p>Zokr McLan: /* Hints and Tips */ Fixed Link to valhalla project, previous link was nsfw</p>
<hr />
<div>{{cleanup}}<br />
{{incursions_sites}}<br />
<div style="float:right; font-size:80%; line-height:125%; list-style-type:none; text-indent:0in; margin-left:0px; padding:0.5em;">__TOC__</div><br />
{{important note box|Please keep in mind that this is how the [[EVE University Incursion Community]] recommends you run this site. Different communities may have different approaches to this site.}}<br />
=Intelligence Reports=<br />
{{incursion sites|headquarters}}<br />
''Preferred List''<br/><br />
*'''6-10 Logistics'''<br/><br />
*'''10-15 Damage Dealers'''<br/><br />
*'''10-15 Snipers'''<br/><br />
<br />
===Military Intelligence===<br />
Your objective is to destroy the Sansha fleet guarding the cloning facility. You will not be able to destroy the facility itself, your only objective is to remove the defensive fleet.<br />
<br />
===Background Intelligence===<br />
Although many parts of the Nation's cloning process are still not fully documented and understood, a few central aspects of the logistics behind their battlefield applications are clearly visible. Front-line cloning is handled in complexes that self-identify as "Nation Rebirth Facilities." Since this facility enables rapid reinforcement of the Nation's squadrons, its tactical importance must not be underestimated. For its own part, the Nation understands this potential weakness, and has made sure that cloning facilities are both highly mobile and heavily defended.<br />
<br />
''Synopsis from ISHAEKA-0085. DED Special Operations.''<br/><br />
''Authorized for Capsuleer dissemination.''<br />
<br />
<br />
<br />
<br />
<br />
<br />
=Rewards=<br />
[[File:HQ_rpr.PNG|right|Full Fleet Headquarters Reward Payout Ratio]]<br />
<br />
<br />
<br />
'''High Sec Payout'''<br />
* 31,500,000 ISK<br />
* 7,000 CONCORD LP <br />
<br />
<br />
<br />
<br />
'''Low / Null Sec Payout'''<br />
* 45,000,000 ISK <br />
* 10,000 CONCORD LP<br />
<br />
<br />
<br />
<br />
=Achieving Objectives Successfully=<br />
<br />
<br />
After watchlist has been provided in fleet chat, the fleet will enter site. Anchor will make their way approximately 15 kilometers to the upper right side of the tower. Once the rest of the fleet enters the site, the fleet will follow anchor with the "Orbit" or "Keep in Range" command. With everyone in the fleet having set their "Orbit" or "Keep in Range" command to anchor, anchor will then 'pull' the fleet approximately 15 kilometers to the upper right side of the tower. This is done to allow the fleet's DD ships to attack the ships that would otherwise be too far for anything but Snipers to hit. As the anchors become more comfortable with the spawn points of the Sansha rats they may move around to provide better initial DPS.<br />
<br />
Upon completion of last wave, Payout is received, and the fleet may leave the site.<br />
<br />
=Watchlist=<br />
<br />
===Logistics===<br />
<br />
*Anchor<br />
*Logistics Commander<br />
*Cap Chain Partner<br />
*Fleet Commander<br />
<br />
===Damage Dealer / Sniper / Drone Bunny===<br />
<br />
*Anchor<br />
*Drone Bunny<br />
*Cap Chain Partner *<br />
<br />
''Note: If you need a cap chain partner, be aware of the distance necessary to facilitate the transfer properly and co-ordinate with your partner or partners for less confusion in the battlefield.''<br />
<br />
<br />
=Pirates / Kill Order=<br />
<br />
'''Anchor'''<br />
<br />
Anchor will want to move approximately 15 kilometers to the upper right side of the tower, and stop when reaching the 15 kilometer mark. Once in that spot, no further action is necessary (other than firing) from anchor.<br />
<br />
===Wave 1===<br />
'''Full Fleet DPS (DPS and Snipers)'''<br />
<br />
Mara Paleo - Sansha Logistics (Tag 0)<br/><br />
Uitra Telen - Sansha Booster (Tag 1)<br/><br />
Deltole Tegmentum - Warp Scrambler / Neut (Tag 2)<br/><br />
Romi Thalamus - Sansha DD (Tag 3-5)<br/><br />
Ostingele Tectums - Sansha High DPS DD (Tag 6-8)<br/><br />
Vylade Dien - Sansha Booster (Tag J) - *TRIGGER - Wave 2*<br/><br />
<br />
<br />
'''Drone Bunny'''<br />
<br />
Schmaeel Medullas - Warp Scrambler / Webber (Tag X)<br/><br />
Renyn Metens - Webber (Tag Y)<br/><br />
<br />
''Note: After all Sansha frigates are down, Drone Bunny can start shooting DPS targets in numbered order until more frigates spawn''<br />
<br />
<br />
<br />
<br />
===Wave 2===<br />
'''DPS Only'''<br />
<br />
Uitra Telen - Sansha Booster (Tag 1)<br/><br />
Romi Thalamus - Sansha DD (Tag 2-4)<br/><br />
Ostingele Tectums - Sansha High DPS DD (Tag 5-7)<br/><br />
<br />
<br />
'''Snipers Only'''<br />
<br />
Antem Neos - Sansha Sniper DD (Tag A-B)<br/><br />
Yulai Crus Cerebi - Sansha DD (Only 3 of the 4) (Tag E-G)<br/><br />
<br />
<br />
'''Drone Bunny'''<br />
<br />
Schmaeel Medullas - Warp Scrambler / Webber (Tag X)<br/><br />
Tama Cerebellums - Warp Scrambler (Tag Y)<br/><br />
<br />
''Note: After all Sansha frigates are down, Drone Bunny can start shooting DPS targets in numbered order until more frigates spawn''<br />
<br />
<br />
'''Full Fleet DPS (DPS, Snipers and Drone Bunny)'''<br />
<br />
Yulai Crus Cerebi - Sansha DD (Tag J) - *TRIGGER - Wave 3*<br/><br />
<br />
<br />
<br />
<br />
===Wave 3===<br />
'''Full Fleet DPS (DPS and Snipers)'''<br />
<br />
Mara Paleo - Sansha Logistics (Tag 0-1)<br/><br />
Vylade Dien - Sansha Booster (Tag 2)<br/><br />
Antem Neos - Sansha Sniper DD (Tag 3-5)<br/><br />
Yulai Crus Cerebi - Sansha DD (Tag J) - *TRIGGER - Wave 4*<br/><br />
<br />
<br />
'''Drone Bunny'''<br />
<br />
Tama Cerebellums - Warp Scrambler (Tag X)<br/><br />
<br />
<br />
<br />
<br />
===Wave 4 / Finále===<br />
''Attention - This wave has a significant alpha strike. Broadcasting for shields and capacitor when initially being yellow-boxed will save your ship.''<br />
<br />
Outuni Mesen - Neut / Warp Scrambler / Webber (Tag 0-1)<br/><br />
Deltole Tegmentum - Warp Scrambler / Neut (Tag 2)<br/><br />
Ostingele Tectums - Sansha High DPS DD (Tag 3-7)<br/><br />
<br />
<br />
=Hints and Tips=<br />
*''If nobody has gated in (aka 'preloaded') the site before the fleet enters site, the rats will be located at extreme range from the warp in point. If someone preloaded the site, all of the rats may be located on top of the fleet. Logistics will need to make repairing the shields of Sansha's primary target, their top priority before setting up Energy Transfers, due to the alpha strike of the preloaded site.''<br />
*''[http://testing.the-valhalla-project.co.uk/ The Valhalla Project] has created an advanced guide to ensure optimal positions of the fleet located [http://puu.sh/nVjpG/cf662b39f6.jpg here]. Moving the fleet around like this is a more advanced tactic and may take a bit of practice to get exactly right but it will lead to faster site times.<br />
<br />
Special thanks to veteran Shield HQ Fleet Commander 'nomatech' for his input as well as many of the links that were sorted, to bring you these details.<br />
[[Category:Incursions sites]]</div>Zokr McLanhttps://wiki.eveuniversity.org/index.php?title=WHC_What_To_Bookmark_Guide&diff=145059WHC What To Bookmark Guide2019-08-30T18:36:15Z<p>Zokr McLan: Added Category WHC</p>
<hr />
<div>The entire Eve University corporation is limited to 500 bookmarks. Therefore, we don't bookmark ''everything'' that we find in wormhole space or connected K-space. This is a quick guide explaining what you should bookmark and what you can leave alone.<br />
<br />
* The [[WHC_System_Naming_Scheme|system naming scheme]] explains how we NAME SYSTEMS in wormhole space<br />
* The [[WHC_Bookmark_Naming_Scheme|bookmark naming scheme]] explains how we NAME BOOKMARKS in wormhole space<br />
* This what to bookmark guide explains WHAT SHOULD BE BOOKMARKED in wormhole space<br />
<br />
<br />
{{TOClimit}}<br />
<br />
==Important Reminders==<br />
<br />
* When you scan a signature down fully enough to know what kind of site it is (gas, relic, data, etc...), that information should go in the mapper by copying the information from your scan window and pasting it into the mapper. (Ask someone who's been around longer if you don't know how to do this!)<br />
* Add systems to the mapper and bookmark the "away" or "dot" wormhole as soon as you find and name it. Without jumping through a wormhole, you can figure out whether the hole is high/low/null/wormhole, whether it's frig, whether it's eol, whether it's shrink or crit. Make sure that information makes it into the system name, the mapper, and the bookmark.<br />
<br />
==Quick guide==<br />
<br />
===I am in ''Innuendo'', ''Bacon'', ''Eggs'', or another ''one jump'' system===<br />
<br />
* Bookmark ALL WORMHOLES (warp to the sig, bookmark the hole and NOT the sig)!<br />
:* '''Scan''' it all the way down!<br />
:* Warp to the sig, '''Check''' what's on the other side (high/low/null/unknown), check shrink/eol status, check whether it's a frig hole ("only the smallest ships").<br />
:* Figure out the new '''Name''' (ex: 2 B9N), '''Update''' the mapper.<br />
:* '''Bookmark''' the exit wormhole (NOT THE SIG! ex: ".2 B9N [ABC] EOL FRIG").<br />
* Bookmark EVERYTHING ELSE (bookmark the sigs)<br />
<br />
===I am more than one jump away from Innuendo===<br />
<br />
* Bookmark ALL WORMHOLES (warp to the sig, bookmark the hole and NOT the sig)!<br />
:* '''Scan''' it all the way down!<br />
:* Warp to the sig, '''Check''' what's on the other side (high/low/null/unknown), check shrink/eol status, check whether it's a frig hole ("only the smallest ships").<br />
:* Figure out the new '''Name''' (ex: 2 B9N), '''Update''' the mapper.<br />
:* '''Bookmark''' the exit wormhole (NOT THE SIG! ex: ".2 B9N [ABC] EOL FRIG").<br />
* Gas<br />
:* Scan and bookmark level 3 gas sites (Vital and Instrumental)<br />
:* Ignore level 1 and 2 gas sites<br />
* Relic/Data<br />
:* Scan and bookmark Null Relic/Data site (has a pirate name, like "Guristas", in the title)<br />
:* Ignore Sleeper Relic/Data site (has the word "Forbidden" or "Unsecured" in the title)<br />
* Combat - ignore<br />
<br />
===I scanned down/am scanning down a===<br />
* Wormhole<br />
:* '''Scan''' it all the way down!<br />
:* Warp to the sig, '''Check''' what's on the other side (high/low/null/unknown), check shrink/eol status, check whether it's a frig hole ("only the smallest ships").<br />
:* Figure out the new '''Name''' (ex: 2 B9N), '''Update''' the mapper.<br />
:* '''Bookmark''' the exit wormhole (NOT THE SIG! ex: ".2 B9N [ABC] EOL FRIG").<br />
* Level 1 or 2 gas site<br />
:* Are you in ''Innuendo'', ''Bacon'', ''Eggs'', or another ''one jump'' system?<br />
::* '''Scan''' it all the way down<br />
::* '''Bookmark''' (ex: "G [ABC] [[Barren_Perimeter_Reservoir|Barren]]").<br />
:* Are you more than one jump from Innuendo?<br />
::* Don't scan all the way down (make sure to put your scan progress in the mapper), don't bookmark.<br />
* Level 3+ gas site<br />
:* '''Scan''' it all the way down, '''update''' the mapper and '''bookmark''' with G (ex: "G [ABC] [[Vital_Core_Reservoir|Vital]]").<br />
* Null Relic/Data site (has a pirate name, like "Guristas", in the title)<br />
:* '''Scan''' it all the way down<br />
:* '''Bookmark''' with NR or ND (ex: "NR [ABC] Guristas").<br />
* Sleeper Relic/Data site (has the word "Forbidden" or "Unsecured" in the title)<br />
:* Are you in ''Innuendo'', ''Bacon'', ''Eggs'', or another ''one jump'' system?<br />
::* '''Scan''' it all the way down<br />
::* '''Bookmark''' it with R or D, omitting the first two words of the name (ex: "R [ABC] [[Forgotten_Frontier_Quarantine_Outpost|Quarantine Outpost]]").<br />
:* Are you more than one jump from Innuendo?<br />
::* Don't scan all the way down (make sure to put your scan progress in the mapper), don't bookmark.<br />
* Combat sig<br />
:* Are you in ''Eggs'', or another ''one jump'' system?<br />
::* '''Scan''' it all the way down<br />
::* '''Bookmark''' it with C (ex: "C [ABC] Haunted Yard").<br />
:* Are you more than one jump from Innuendo?<br />
::* Don't scan all the way down (make sure to put your scan progress in the mapper), don't bookmark.<br />
<br />
[[Category:WHC]]</div>Zokr McLanhttps://wiki.eveuniversity.org/index.php?title=WHC_Bookmark_Naming_Scheme&diff=145058WHC Bookmark Naming Scheme2019-08-30T18:35:52Z<p>Zokr McLan: Corrected Category</p>
<hr />
<div>The Wormhole Campus uses a set of rules and guidelines to generate logical names for the many [[Wormhole Space]] bookmarks it needs to keep.<br />
<br />
'''Bookmarks are vital.''' Bookmarking correctly is a job that everyone participates in, but can be a matter of life and death that you get these right.<br />
<br />
* This bookmark naming scheme explains how we NAME BOOKMARKS in wormhole space<br />
* This [[WHC_System_Naming_Scheme|system naming scheme]] explains how we NAME SYSTEMS in wormhole space<br />
* The [[WHC_What_To_Bookmark_Guide|what to bookmark guide]] explains WHAT SHOULD BE BOOKMARKED in wormhole space<br />
<br />
<br />
{{TOClimit}}<br />
<br />
===Bookmarking===<br />
{{Wormhole Links}}<br />
'''Corporate Bookmarks'''<br/><br />
Always bookmark every probeable site within the Home System. Save the Bookmarks in the Wormhole Campus folder under Corporation Bookmarks. <br />
*When W-Space systems are removed from the [https://mapper.eveuniversity.org/map/3/ mapper], <u>'''it is your Job to clean up the OLD bookmarks!'''</u> The entire Corporation is limited to 500 Bookmarks. <br />
*Be sure to review [[WHC Mapping Scheme]] along with this page in order to completely understand the scheme. Also the mapper comes with a very nice example.<br />
<br />
====Wormholes====<br />
Right click in space and look under Corporation bookmarks, The way back will be at the top, other WHs are listed below.<br />
*Please add bookmarks in K-Space to contain the chain on the mapper. <br />
*Note that it is current campus policy to bookmark all holes, including k-space connections into Innuendo (i.e. *Eggs, *1 Z1H, etc.)<br />
*DO NOT BOOKMARK Wormholes from Scanner Results. Only Bookmark Wormholes while On-Grid from the Overview or in space.<br />
* 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).<br />
<br />
<br/>[[Image:WHCRightClickCorpBookmarks.jpg]]<br/><br />
<br />
=====Holes leading '''away''' from Innuendo=====<br />
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''.<br />
<br />
Examples:<br />
{| class="wikitable"<br />
! style="text-align:left;" | Wormhole<br />
! Bookmark<br />
|-<br />
| ''Innuendo -> Bacon'' || .Bacon [XYZ]<br />
|-<br />
| ''Innuendo -> Eggs'' || .Eggs [XYZ]<br />
|-<br />
| ''Bacon -> 2 B2L'' || .2 B2L [MNO]<br />
|-<br />
| ''2 B2L -> 3 B1'' || .3 B1 [STU]<br />
|}<br />
<br />
=====Holes leading '''toward''' Innuendo=====<br />
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. <br />
<br />
'''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.<br />
'''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.<br />
Examples:<br />
{| class="wikitable"<br />
! style="text-align:left;" | Wormhole<br />
! Bookmark<br />
|-<br />
| ''Bacon -> Innuendo'' || *Bacon [***]<br />
|-<br />
| ''Bacon -> Innuendo'' || *Bacon [XYZ]<br />
|-<br />
| ''2 B2L -> Bacon'' || *2 B2L [XYZ]<br />
|-<br />
| ''4 B2 -> 3 B5'' || *4 B2 [MNO]<br />
|-<br />
| ''3 B5 -> 2 B2L'' || *3 B5 [STU]<br />
|}<br />
<br />
=====End-of-life, Shrink, Frig, and Crit Wormholes (that are mapped) =====<br />
If a wormhole is end-of-life, shrink, frig ("Only the smallest ships can pass"), 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.<br />
<br />
Examples:<br />
{| class="wikitable"<br />
! style="text-align:left;" | Wormhole<br />
! Bookmark<br />
|-<br />
| ''Bacon -> Innuendo'' || *Bacon [XYZ] EOL<br />
|-<br />
| ''2 B2L -> Bacon'' || *2 B2L [XYZ] CRIT EOL<br />
|-<br />
| ''4 B2 -> 3 B1'' || *4 B2 [MNO] SHRINK<br />
|-<br />
| ''5 E2 -> 6 E1N'' || .6 E1N [NOO] FRIG CRIT EOL<br />
|}<br />
<br />
=====Gate to gate connections =====<br />
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.<br />
<br />
Examples:<br />
{| class="wikitable"<br />
! style="text-align:left;" | Gate Connection<br />
! Bookmark<br />
|-<br />
| ''Eggs -> 2 E2H '' || .2 E2H [Gate]<br />
|-<br />
| ''2 E2H -> Eggs'' || *2 E2H [Gate]<br />
|-<br />
| ''1 Z1L -> 2 Z2L '' || .2 Z2L [Gate]<br />
|-<br />
| ''2 Z2L -> 1 Z1L'' || *2 Z2L [Gate]<br />
|-<br />
| ''3 Y1N -> 4 Y3N '' || .4 Y3N [Gate]<br />
|-<br />
| ''4 Y3N -> 3 Y1N'' || *4 Y3N [Gate]<br />
|}<br />
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 2 E2H and you can't find it due to its being a gate it is annoying and frustrates the purpose of our bookmarking scheme, which was created so we don't need to rely on the mapper tool for navigation.<br />
<br />
===== Deleting bookmarks =====<br />
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).<br />
<br />
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.<br />
<br />
'''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.<br />
<br />
====Sites====<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
*Bookmarks can be made from the scanning results list<br />
*Standard format is "<sigtype> [sig id] <additional info>"<br />
**<code>[sig id]</code> = [ABC], [BCD], [EFG], etc<br />
*There are 5 types:<br />
<br />
===== G(as Sites) =====<br />
<br />
*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.<br />
*Only the <u>''first''</u> word is important<br />
**G [ABC] Barren<br />
**G [DEF] Token<br />
**G [DEF-2] Bountiful<br />
**G [GHI] Vast<br />
**G [NMD] Instrumental ''(Only found in C5, C6 class W-Space)''<br />
**G [YUI] Vital ''(Only found in C5, C6 class W-Space)''<br />
<br/><br />
<br />
===== R(elic Sites) =====<br />
<br />
These instructions are for '''sleeper''' relic sites. If it doesn't have "Forgotten" or "Unsecured" in the name, it's not a sleeper relic site! (See "Null Sites" below.)<br />
<br />
*The <u>''first 2 words''</u> should be <u>''omitted.''</u> <br />
*<strike>Forgotten Frontier</strike> Recursive Depot. <br />
**R [HJK] Quarantine Outpost<br />
**R [GHT] Recursive Depot<br />
**R [JHI] Conversion Module<br />
**R [ADH] Evacuation Center<br />
<br/><br />
<br />
===== D(ata Sites) =====<br />
<br />
These instructions are for '''sleeper''' data sites. If it doesn't have "Forgotten" or "Unsecured" in the name, it's not a sleeper data site! (See "Null Sites" below.)<br />
<br />
*The <u>''first 2 words''</u> should be <u>''omitted.''</u> <br />
*<strike>Unsecured Frontier</strike> Database. <br />
**D [ADF] Database<br />
**D [DHI] Receiver<br />
**D [FHI] Digital Nexus<br />
**D [FJO] Trinity Hub<br />
<br/><br />
<br />
===== N(ull Sites) =====<br />
<br />
It's kind of weird that we call these "Null" sites, but they are the kind of exploration sites you find in Null-Sec (no sleepers shooting at you!) They're also called "Pirate" sites.<br />
<br />
*Pirate Relic and Data sites should be labeled with the relevant faction (IE: Angel).<br />
**NR [ABC] Angel<br />
**ND [GHI] Serpentis<br />
<br/><br />
<br />
===== C(ombat Sites) =====<br />
<br />
*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.<br />
**C [ISO] Radiance<br />
**C [FOP] Gurista Outpost<br />
**C [SVV] 6/10 Blood<br />
**C [SVV] 4/10 Angel<br />
[[Category:WHC]]</div>Zokr McLanhttps://wiki.eveuniversity.org/index.php?title=WHC_Bookmark_Naming_Scheme&diff=145056WHC Bookmark Naming Scheme2019-08-30T18:34:23Z<p>Zokr McLan: Added Category</p>
<hr />
<div>The Wormhole Campus uses a set of rules and guidelines to generate logical names for the many [[Wormhole Space]] bookmarks it needs to keep.<br />
<br />
'''Bookmarks are vital.''' Bookmarking correctly is a job that everyone participates in, but can be a matter of life and death that you get these right.<br />
<br />
* This bookmark naming scheme explains how we NAME BOOKMARKS in wormhole space<br />
* This [[WHC_System_Naming_Scheme|system naming scheme]] explains how we NAME SYSTEMS in wormhole space<br />
* The [[WHC_What_To_Bookmark_Guide|what to bookmark guide]] explains WHAT SHOULD BE BOOKMARKED in wormhole space<br />
<br />
<br />
{{TOClimit}}<br />
<br />
===Bookmarking===<br />
{{Wormhole Links}}<br />
'''Corporate Bookmarks'''<br/><br />
Always bookmark every probeable site within the Home System. Save the Bookmarks in the Wormhole Campus folder under Corporation Bookmarks. <br />
*When W-Space systems are removed from the [https://mapper.eveuniversity.org/map/3/ mapper], <u>'''it is your Job to clean up the OLD bookmarks!'''</u> The entire Corporation is limited to 500 Bookmarks. <br />
*Be sure to review [[WHC Mapping Scheme]] along with this page in order to completely understand the scheme. Also the mapper comes with a very nice example.<br />
<br />
====Wormholes====<br />
Right click in space and look under Corporation bookmarks, The way back will be at the top, other WHs are listed below.<br />
*Please add bookmarks in K-Space to contain the chain on the mapper. <br />
*Note that it is current campus policy to bookmark all holes, including k-space connections into Innuendo (i.e. *Eggs, *1 Z1H, etc.)<br />
*DO NOT BOOKMARK Wormholes from Scanner Results. Only Bookmark Wormholes while On-Grid from the Overview or in space.<br />
* 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).<br />
<br />
<br/>[[Image:WHCRightClickCorpBookmarks.jpg]]<br/><br />
<br />
=====Holes leading '''away''' from Innuendo=====<br />
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''.<br />
<br />
Examples:<br />
{| class="wikitable"<br />
! style="text-align:left;" | Wormhole<br />
! Bookmark<br />
|-<br />
| ''Innuendo -> Bacon'' || .Bacon [XYZ]<br />
|-<br />
| ''Innuendo -> Eggs'' || .Eggs [XYZ]<br />
|-<br />
| ''Bacon -> 2 B2L'' || .2 B2L [MNO]<br />
|-<br />
| ''2 B2L -> 3 B1'' || .3 B1 [STU]<br />
|}<br />
<br />
=====Holes leading '''toward''' Innuendo=====<br />
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. <br />
<br />
'''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.<br />
'''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.<br />
Examples:<br />
{| class="wikitable"<br />
! style="text-align:left;" | Wormhole<br />
! Bookmark<br />
|-<br />
| ''Bacon -> Innuendo'' || *Bacon [***]<br />
|-<br />
| ''Bacon -> Innuendo'' || *Bacon [XYZ]<br />
|-<br />
| ''2 B2L -> Bacon'' || *2 B2L [XYZ]<br />
|-<br />
| ''4 B2 -> 3 B5'' || *4 B2 [MNO]<br />
|-<br />
| ''3 B5 -> 2 B2L'' || *3 B5 [STU]<br />
|}<br />
<br />
=====End-of-life, Shrink, Frig, and Crit Wormholes (that are mapped) =====<br />
If a wormhole is end-of-life, shrink, frig ("Only the smallest ships can pass"), 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.<br />
<br />
Examples:<br />
{| class="wikitable"<br />
! style="text-align:left;" | Wormhole<br />
! Bookmark<br />
|-<br />
| ''Bacon -> Innuendo'' || *Bacon [XYZ] EOL<br />
|-<br />
| ''2 B2L -> Bacon'' || *2 B2L [XYZ] CRIT EOL<br />
|-<br />
| ''4 B2 -> 3 B1'' || *4 B2 [MNO] SHRINK<br />
|-<br />
| ''5 E2 -> 6 E1N'' || .6 E1N [NOO] FRIG CRIT EOL<br />
|}<br />
<br />
=====Gate to gate connections =====<br />
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.<br />
<br />
Examples:<br />
{| class="wikitable"<br />
! style="text-align:left;" | Gate Connection<br />
! Bookmark<br />
|-<br />
| ''Eggs -> 2 E2H '' || .2 E2H [Gate]<br />
|-<br />
| ''2 E2H -> Eggs'' || *2 E2H [Gate]<br />
|-<br />
| ''1 Z1L -> 2 Z2L '' || .2 Z2L [Gate]<br />
|-<br />
| ''2 Z2L -> 1 Z1L'' || *2 Z2L [Gate]<br />
|-<br />
| ''3 Y1N -> 4 Y3N '' || .4 Y3N [Gate]<br />
|-<br />
| ''4 Y3N -> 3 Y1N'' || *4 Y3N [Gate]<br />
|}<br />
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 2 E2H and you can't find it due to its being a gate it is annoying and frustrates the purpose of our bookmarking scheme, which was created so we don't need to rely on the mapper tool for navigation.<br />
<br />
===== Deleting bookmarks =====<br />
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).<br />
<br />
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.<br />
<br />
'''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.<br />
<br />
====Sites====<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
*Bookmarks can be made from the scanning results list<br />
*Standard format is "<sigtype> [sig id] <additional info>"<br />
**<code>[sig id]</code> = [ABC], [BCD], [EFG], etc<br />
*There are 5 types:<br />
<br />
===== G(as Sites) =====<br />
<br />
*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.<br />
*Only the <u>''first''</u> word is important<br />
**G [ABC] Barren<br />
**G [DEF] Token<br />
**G [DEF-2] Bountiful<br />
**G [GHI] Vast<br />
**G [NMD] Instrumental ''(Only found in C5, C6 class W-Space)''<br />
**G [YUI] Vital ''(Only found in C5, C6 class W-Space)''<br />
<br/><br />
<br />
===== R(elic Sites) =====<br />
<br />
These instructions are for '''sleeper''' relic sites. If it doesn't have "Forgotten" or "Unsecured" in the name, it's not a sleeper relic site! (See "Null Sites" below.)<br />
<br />
*The <u>''first 2 words''</u> should be <u>''omitted.''</u> <br />
*<strike>Forgotten Frontier</strike> Recursive Depot. <br />
**R [HJK] Quarantine Outpost<br />
**R [GHT] Recursive Depot<br />
**R [JHI] Conversion Module<br />
**R [ADH] Evacuation Center<br />
<br/><br />
<br />
===== D(ata Sites) =====<br />
<br />
These instructions are for '''sleeper''' data sites. If it doesn't have "Forgotten" or "Unsecured" in the name, it's not a sleeper data site! (See "Null Sites" below.)<br />
<br />
*The <u>''first 2 words''</u> should be <u>''omitted.''</u> <br />
*<strike>Unsecured Frontier</strike> Database. <br />
**D [ADF] Database<br />
**D [DHI] Receiver<br />
**D [FHI] Digital Nexus<br />
**D [FJO] Trinity Hub<br />
<br/><br />
<br />
===== N(ull Sites) =====<br />
<br />
It's kind of weird that we call these "Null" sites, but they are the kind of exploration sites you find in Null-Sec (no sleepers shooting at you!) They're also called "Pirate" sites.<br />
<br />
*Pirate Relic and Data sites should be labeled with the relevant faction (IE: Angel).<br />
**NR [ABC] Angel<br />
**ND [GHI] Serpentis<br />
<br/><br />
<br />
===== C(ombat Sites) =====<br />
<br />
*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.<br />
**C [ISO] Radiance<br />
**C [FOP] Gurista Outpost<br />
**C [SVV] 6/10 Blood<br />
**C [SVV] 4/10 Angel<br />
[[Category:Wormholes]]</div>Zokr McLan