View source for Basic Survival In NullSec



== Overview Configuration ==
''Main article: [[Overview Settings]]''

'''EVE's default overview settings are configured for high-security space and must be modified for nullsec operations.''' The default overview settings prioritize game mechanics such as security status and Crimewatch flags that are irrelevant in Nullsec. In Nullsec, we rely on alliance standings to distinguish friend from foe.

If you are returning from a break, take the time to verify that your current overview includes all current ships, structures, and NPCs added while you were gone. If a new ship is not on your overview, you will not see it until you are already dying to it.

Consult [[Overview Settings]] when joining the alliance, after game reinstalls, and following major patches. Incorrect overview configuration will cause misidentification of hostiles and friendlies.

== Monitoring Local Chat ==

Local chat displays all pilots currently in-system. Properly configured overview settings assign color-coded indicators showing alliance standings:

* '''Red/Orange icon:''' Negative alliance standing - hostile to GSF and/or our allies
* '''Red star:''' Active war target - can freely shoot you in all space including highsec
* '''Flashy skull:''' Suspect or criminal timer - recently engaged in PVP activity in High/lowsec. This is largely irrelevant in nullsec, and many overviews will hide this either partially or completely.
* '''Grey:''' Neutral - assume hostile intent
* '''Light blue/Blue/Green:''' Members of Goonswarm, The Imperium, and other allied entities
* '''Purple:''' Fleet members

Goonswarm and our allies operate on the principle of "Not Blue, Shoot It" (NBSI). If you see someone without Blue standings in local, assume they are hostile and are actively trying to pick a fight. Local is you best source on information about what is present in the same system as you. When in space, always keep an eye on local and use caution if a non-blue character is in the same system.

== Intel Channel Usage ==

All nullsec entities use [[Intel channels]] to track hostiles as they move through our space. In these channels, when a friendly player sees a non-blue player in local they will report:

* The system they're in
* The name of the hostile character
* The ship that character is in (if they do not know, they will use the term 'nv' for 'No vision'

The Imperium maintains a set of intel channels, with different channels for different regions of our space. Always keep an eye on the relevant intel channel for the space you're flying in, and help report any non-blues you see.

'''Channel management tip:''' You can drag channels into separate windows in the UI so you can simultaneously monitor intel, local, and fleet communications. If you have multiple chat channels open in the same window, the tabbed channels will flash yellow on new messages.

'''Reporting protocol:''' Report hostile contacts only after securing your own safety. Use format: System name, pilot name, ship count and types (example: "1-SMEB Sa Matra +3 Maledictions"). This alerts alliance members and aids fleet commanders in defensive operations.

== Insta-Warp Travel ==

If you simply need to move a character around space, the best way to do so is using an insta-warp ship. An insta-warp ship is an ship that has an align time of less than 2 seconds. Because of how the EVE servers communicate with your game client, a sub-2 second align time make it effectively impossible for an enemy to lock on to your ship to shoot you before you enter warp. While you are not unkillable, a proper insta-warp ship significantly reduces risk as you move around.

'''Insta-Warp Ship Types'''
* All Shuttles insta-warp by default. Additionally, shuttles are passively immune to warp disruption bubbles, making you even harder to catch.
* T1 frigates can be made into insta-warp ships. However, they lack the bubble immunity of shuttles. This makes them fairly easy to catch for a prepared camp.
* Interceptors can also be fit to be insta-warp ships. Additionally, interceptors have the space to fit some tank and can fit Interdiction Nullifiers, giving them a limited version of the bubble immunity available to shuttles. Keep in mind, these ships require fairly high skills to be effective.

'''Fitting:'''
* Combine Inertial Stabilizer modules with Low Friction Nozzle Joint rigs
* Consult this [http://i.imgur.com/7rYYJpY.png alignment chart] for component combinations
* The Spaceship Command and Evasive Maneuvering skills will improve the align time of your ships. Ensure these skills are at least at level IV.

The biggest threat to insta-warp ships are smartbombers. Hostiles trying to catch insta-warp ships will set themselves up in a ship equipped with smartbombs on the gate you are warping to, allowing them to kill your fragile insta-warp ship while you exit warp.

'''Best practices:'''
* Don't warp directly between gates with hostiles in Local. Instead warp to bookmarks, celestials, or cosmic signatures before warping to your exit stargate so you land on the gate from a direction that a smartbomber is not expecting.
* Verify that your fit has a sub-2 second align time using [https://wiki.goonswarm.org/w/Pyfa pyfa] or the in-game fitting tool
* Don't use an insta-warp ship to carry high-value but low-volume goods. Many an EVE player have lost large amounts of money assuming that their insta-warp ship was unkillable.

== Station Security Procedures ==

'''Do not undock with hostile or neutral pilots in local without intel confirmation that undock is clear.''' Hostiles typically monitor stations first.

Citadels provide superior security versus NPC stations:
* Tether mechanics offer protection
* Tight tether orbits prevent bumping attacks

During hostile presence:

*  Check Fleet Finder for active defense fleets
*  Reship to defense doctrine if available
*  Consider that fleet formation alone may deter hostiles

== Navigation Best Practices ==

'''Disable autopilot.''' Autopilot creates vulnerability during gate approach. Manual navigation is mandatory in nullsec.

''' If neutral is in system always warp to the closest structure to the Ansiblex or Jump gate ''' 

=== Alliance Jump Gates ===

[[Alliance:Stargate|Ansiblex Jump Gates]] are alliance-maintained infrastructure providing rapid, secure transit through controlled space.

'''Jump gate protocol:'''
*  Upon jump completion, immediately warp to citadel or exit gate
*  Verify intel channels for destination system hostiles
*  Be aware: Cloaked hostile camps at jump gates are common

=== Warp-to-Zero Protocol ===

Always use warp-to-zero on gates. Minimize time vulnerable between celestials.

== Emergency Procedures ==

=== Safespot Usage ===

When hostiles enter system and station/citadel docking is unavailable, use emergency procedures.

'''Citadel advantages:'''
* Direct warp-in to tether
* Unexpected approach angles from safespots possible

'''Temporary measures:'''
* Celestial warp-at-100km: Safer than stations/belts, but discoverable via planetary scanning
* '''Safespots:''' Bookmarks created mid-warp between celestials, placed in unpredictable locations

Recent probe mechanics have reduced safespot effectiveness, but they remain viable against fleets without dedicated scanning ships. Do not remain stationary for extended periods.

Reference: [https://wiki.eveuniversity.org/Safe_spots EVE University Safespot Guide]

== Combat Engagement Philosophy ==

Hostile forces seek advantageous engagements, not fair fights. Typical hostile compositions include fast tackle (Interceptors, Dramiels) or Recon ships that will disengage from unfavorable engagements.

'''Recommended approach:'''
* Avoid solo engagement unless properly equipped and skilled
* Form coordinated fleet response
* Utilize tactical ambush positioning

== Combat Readiness ==

Maintain a fitted PVP ship for immediate deployment. This enables rapid response to defense fleet participation.

[https://goonfleet.com/index.php/forum/266-fleet-doctrines-and-reimbursement/ Current Fleet Doctrines]

== Equipment Recommendations ==

=== Cloaking Devices ===

Cloaking modules prevent overview detection while maintaining local chat visibility. Essential general travel security.

'''Covert Ops Cloaking Device:'''
* '''Superior capability:''' Allows warping while cloaked
* '''Compatible hulls:''' [https://wiki.eveuniversity.org/Covert_Ops Covert Ops], [https://wiki.eveuniversity.org/Stealth_Bombers Stealth Bombers], [https://wiki.eveuniversity.org/Cruisers#Recon_Ships Recon Ships], [https://wiki.eveuniversity.org/Blockade_Runners Blockade Runners], configured [https://wiki.eveuniversity.org/Strategic_Cruisers Strategic Cruisers]

'''Limitations:'''
* De-cloaking proximity: 2,500m to objects, ships, or drones
* Cannot target while cloaked
* Significantly reduced velocity when active
* Persistent penalty: 2x target lock time
* Cannot activate if already targeted

'''Optimal usage:'''
* Deploy from safespots or perch bookmarks near operational area
* Risk: Competent scanner can probe safespot location
* Response: If combat probes detected, relocate to distant safespot and proceed to friendly citadel

=== Warp Core Stabilizers ===

'''[https://www.eveonline.com/news/view/nullification-and-warp-module-update-live-now Great Escape Update]:''' WCS are now activated modules.

WCS provide 2 points of warp disruption resistance when activated.

'''Limitations:'''
* Ineffective against warp disruption bubbles (Interdictor or deployable)
* Penalties: Reduced maximum targeting range, decreased drone bandwidth

=== Speed Modifications ===

'''Nanofiber Internal Structure:'''
Increases ship agility, reducing alignment time. Recommended for low-agility hulls (industrials) to decrease gate-to-gate transit time.

'''Propulsion Modules:'''
* '''MicroWarpDrive (MWD):''' Significant speed increase, capacitor-intensive
* '''Afterburner (AB):''' Moderate speed increase, capacitor-efficient

Both provide critical mobility for bubble escape or gate crash maneuvers. Capacitor usage required.