====== A BRAVE Guide to Surviving Nullsec ======
**Nullsec**, short for **"Null Security Space"**, comprises every system in EVE that has a security status at or below 0.0. These are the regions of space where wars between the great alliances and coalitions have been fought, and where the powerful pirate factions make their home. There are no ships of CONCORD or one of the major governments ready to come to your aid in null sec, no batteries of heavy guns on the gates that will save you if you are tackled.
As long as you are undocked, you are always in danger of having your ship destroyed and your pod obliterated.
Brave finds itself constantly at war. Even in the farthest-flung systems in Eve at 4 a.m., there is still a chance that a lurking enemy went unreported in intel. With players from around the world ingame, what would be odd hours for you could be primetime elsewhere. Despite the dangers, there are essential skills you can develop and use to both increase your odds of survival and frustrate your enemies.
{{INLINETOC 2-2}}
===== Local Chat =====
The most important tool to gauge your surroundings is the **Local Chat channel**. This channel will show you everyone currently in your solar system. **A properly set up overview can let you immediately distinguish allies from enemies with one glance.**
Effectively using Local Chat requires little set up. Simply drag the local window out giving it a separate pane and stretch the window lengthwise. Click "Member List Settings" (looks like 3 people) enable "Show Compact Member list". Properly set up your local chat should resemble this. Watching Local chat like a hawk can save your life.
A common window layout technique is to position your Local Chat window behind and to the side of your other chat windows, so that only the total player count and list of names is visible:
|{{ https://raw.githubusercontent.com/bravecollective/wiki-files/main/imgur/yt4W135.jpg?500 }}|
This allows you to keep an eye on how many neutrals/reds are in system without sacrificing screen space to local chatter. Please remember that in null sec **everything that is not blue or green (depending on your overview settings) is to be considered hostile.**
You can keep an eye on who is entering the system you are in by highlighting the list of individuals in local and pressing CTRL+A. This will highlight the list as it currently stands. Anyone who enters local will not have their name highlighted, leaving you with an at-a-glance view of any new neuts that probably want to kill you.
===== Intel Channels =====
Paired with Local chat, **intel channels** will give you a good idea of any enemies in the area. It is important to remember intel channels are only effective if people are reporting intel! If you see hostiles or neutrals in your system it is imperative you report them to the proper channel.
* **[[https://github.com/Slazanger/SMT/releases|SMT]]** - The Intel Map tool. Anything reported in the delve.imperium in-game chat channel can be shown here. If you're not using this, you're doing it wrong. Note: this also works great on a tablet or a separate laptop.
* You may need to adjust the filters on the initial install of SMT to ensure it is watching the proper channel(s). To do this, open the program and go to **File** -> **Preferences** -> **Intel**. Adjust the **Channel Filters** to match the in-game channel name(s) you want to watch (e.g. "**delve.imperium**").
* **delve.imperium** - In-Game Chat Channel where Intel is provided. When linking intel, the format used is usually:
* //System// - //Name Of Pilot// - //Ship Pilot Is Flying
* (if n/a, write 'nv', which means 'no visual')//
for example:
//HED-GP// - //Lychton Kondur// - //Ibis//.
Lastly, if someone asks for the status of a system, it generally means whether there are neutrals or reds in the system, or in a specific place in system, so if you can safely answer the question for them by quickly checking or already know, do so in the Intel channel.
* Use delve.imperium while flying in Delve.
* Use querious.imperium while flying in Querious.
===== Jump Gates, Jump Bridges, and Jump Fatigue =====
Jump gates have been established throughout Brave space to provide you with a quick means of traversing long distances. However, they have dangers associated with them that could spell disaster for the unaware.
There are jump bridges **and** jump gates; they are not the same. Titans and Black Ops ships can make jump bridges, while The Ansiblex Jump Gate is a POS (player owned structure). Also the Jump Gates do not have any jump fatigue while the jump bridges still have jump fatigue.
|{{ https://raw.githubusercontent.com/bravecollective/wiki-files/main/imgur/jLrcgMZ.png }}|
|There is a fee associated with the jump gates to cover their cost. This pays for the ozone usage of the gate and you will no longer be prompted to pay the gate fee each time you use a gate. Please head to your wallet and under the Automatic Pay Settings click the box and have it set to 300 ISK. Also you will be charged 300 ISK per volume of your ship not 300 ISK for a single trip. Don't worry a cruiser only costs 63,900 ISK per jump. |
You need to understand the mechanics of **jump fatigue**. Repeated use of jump drives or jump bridges will trigger two cooldowns. One is a hard cap on when you can jump again, your jump timer. The second is jump fatigue, a timer that increases your hard jump timer each time you make a jump while it's active.
|{{ http://puu.sh/mtysy/079e4e51cf.jpg }}| {{http://cdn1.eveonline.com/www/newssystem/media/66636/1/CooldownTimer1.png}}|{{http://cdn1.eveonline.com/www/newssystem/media/66636/1/CooldownTimer2.png}}|
|The two timers at the top tell you if you can jump at all (the orange one)\\ and how long the next red timer will be (the blueish one)|The higher the Jump Fatigue Timer is, the longer the next Reactivation Timer will be.\\ The exact length will be shown if you hover over it.|If you have a Jump Reactivation Timer, you can't use a jump bridge, jump your capital or blops or JF or be jumped by a titan or blops.\\ **You can however use Stargates and jump gates.**|
For more info please read [[https://www.eveonline.com/article/phs7yj/navigation-structures-inbound|CCP's dev-blog]]
To calculate your fatigue, you can use [[http://fatigue.nakamura-labs.com/|Nakamura Lab's Jump Fatigue calulator]].
===== Autopilot =====
Under **no circumstances** should you **ever** use autopilot. Brave is constantly at war with highsec corporations that do nothing other than lurk on gates, seeking to destroy you. Brave is constantly at war with nullsec corporations that will obliterate a hapless capsuleer who is gently autopiloting toward a gate, and opportunistic neuts will jump on such a ship in a moment's notice. If you value your assets, do not use this feature.
===== Insta-dock/Undock Bookmarks =====
Stations are large. Often, right clicking a station and selecting warp to 0 still won't put you quite within range of the station dock. It can put you as far as 10km out, which is plenty of time for someone to lock onto you and blow you up. Similarly, when you undock and select "Warp to...", it takes a moment for your ship to align to that place before you warp. Again, this is enough time for someone to lock you and blow you up.
Fortunately, there are rather simple ways around this. An **Insta-Undock** is a point in space in a straight line from undocking a station, that you can warp to with zero align time. For our high-traffic systems/stations, there will be "instaundock" bookmarks saved as Corporation Bookmarks. To access the menu, just right click on an empty area of space. It is advisable to make your own insta-dock and undock bookmarks as well; often, people will know where our corporate undock bookmarks are set and wait there for you. Be sure to dock at the station as soon as you land at the insta-dock bookmark - if it is camped, hold the D key and spam-click on the station to dock as fast as possible.
For more detailed information, please also read our relevant guides:
* [[public:dojo:wiki:how_to_survive_the_undock]]
* [[public:dojo:wiki:instadock-instaundock]]
==== Undocking Procedures ====
The undock of any station is one of the areas pilots have the greatest false sense of security. You are not safe on the station undock even if there is only one hostile in system. It is important to note that immediately after undocking you are invulnerable and unable to be locked for 30 seconds. Any action taken by you will remove this effect save for completely stopping your ship. If you need to undock with hostiles in system, immediately stop your ship and check your surroundings. If the undock looks clear you are fine to continue, but if the undock is red you can redock after your session timer expires. Currently the session change timer is set for 10 seconds meaning that you will be unable to redock with a station for the first 10 seconds in space. It is imperative that you do not try to redock with a station in these 10 seconds or you will become vulnerable. More advanced undocking techniques are covered in the intermediate section.
|{{https://raw.githubusercontent.com/bravecollective/wiki-files/main/imgur/Daf6QJU.png?400}}|
|If you are in a bubble immune ship, you can ignore the bubble, ofc. ;)|
===== Tactical Bookmarks =====
Aside from setting up your overview, **tactical bookmarks** are one of the most strategically important steps a pilot can take to prevent death. Tactical bookmarks can provide instant undocks, "safe" spots in systems, and perches for celestials.
Your first task in any new friendly system is to make an instant undock bookmark for the station. If the undock is being camped without bubbles this will give you the chance to escape. Instant undocks are especially useful in high traffic systems, like our staging system or Jita. In highsec systems it's usually a better idea to use a neutral alt to make these bookmarks then contract them to your main character.
Safe spots and tactical perches are more useful in gathering intel on a system than helping you escape. A safe spot works by putting your ship outside of normal vectors between celestials, hopefully limiting the chance of you being scanned. It is important to note that if you're not cloaked you will be found. Tactical perches, on the other hand, serve to let you avoid bubbles as well as allow you to scan gates before you land on them.
==== Safe Spot Bookmarks ====
To create a **safe spot** bookmark in a system, open your People & Places menu. Warp between two fairly wide-spaced celestials, e.g. a stargate and the sun, then while you are in warp click press CTRL+B and 'Submit' to save a spot partway between the two locations. Rename it to "Safe". Now when you right-click in open space the new bookmark will appear in your destinations list and you can warp to it.
This creates a very unsafe safe, since it will be in line between the two celestials. To make it harder to find, you can create two of those safes (use different celestials to make them) and then create another one by warping between the two safes (That's the recommended way to make a safe).
Note that even though nobody else will be able to warp to your personal safe spot, a ship with Combat Probes will still be able to find you unless you are cloaked.
==== Tactical Perch Bookmarks ====
A **tactical perch** is simply a bookmark in space that is on-grid with a stargate, station, or other celestial object that you want to get a look at without getting too close. Since it is not usually possible to create these in the heat of battle, it is a good idea to make your own perches in systems you expect to be active in.
Let's say you want to create a perch on a stargate. After checking local to make sure there are no enemies around, warp to the gate at 100km range, then turn around and burn away from the gate in a random direction (it's a good idea to have a ship equipped with a MWD at this point). When you have reached around 200-250km distance, open your People & Places menu and create a new bookmark. Name it something like "250km off HED-GP gate".
Now when you are active in this system and want to look at the gate without the risk of landing on top of someone, you can warp to your new perch.
===== The Directional Scanner =====
An often underused utility by newbros is the **directional scanner, or "d-scan"**. This tool allows you to know what is around you in space up to 14AU away. The scanner is most useful when used in conjunction with tactical bookmarks allowing pilots to safely navigate around hostiles. With proper overview settings, you can detect bubbles this way. If you enter warp before a bubble is active, you will not be caught by that bubble. Warping within 14 AU of your target stargate and narrow angle D-scanning towards the gate is a good way to stay safe in null. (Of course it doesn't protect you from the other side of the gate.) Be aware that the direction of your D-scan is based on your camera, and is unrelated to the direction your ship is facing.
There are many excellent YouTube tutorials demonstrating how and why to d-scan.
When scouting for a fleet, it is also helpful to be able to show your FC what you have found on D-Scan. There are many third party tools that allow you to do this, like [[https://intel.bravecollective.com/dscan/|The Brave D-Scan Tool]].
How these tools generally work is that you first D-Scan as per usual in-game, and then once you have done this, select the box where the results are found and press Ctrl+A, then Ctrl+C. After that, go to any of the tools linked above, and they will generally ask you to paste these results that you have just copied into a text box (Ctrl+V). Depending on the third-party tool used, follow any further prompts on the website.
Note: After the [[http://community.eveonline.com/news/dev-blogs/dev-blog-coming-to-eve-online-proteus/|January 13th, 2015 patch ("Proteus")]], Combat Recon ships (Curse, Rook, Lachesis, and Huginn) are now undetectable by D-scan.
===== Aggression Timers =====
**Aggression timers** are small countdown clocks that appear in the top-left of your screen. Since CONCORD are not active in null-sec, the main concern with aggression timers is that they can prevent you from using a stargate or docking at a station for 60 seconds following combat with another player.
This can sometimes cause problems for fleets, since if some players have timers and some don't, the fleet can become separated by jumping through a gate. On fleets you will often hear the FC say "Do not aggress" when an enemy is on-grid; this is because the FC wants to be able to escape the system safely without waiting out aggression timers.
| **Non-Capsuleer Log-Off Timer** (5 Minutes) |
| {{https://support.eveonline.com/hc/en-us/article_attachments/201415692/Crimewatch2_0_NPCTimer.png}} |
Also known as //NPC Flag//, this flag becomes active when you activate any offensive module against an NPC vessel of any kind, or when an NPC vessel activates an offensive module on you. This flag lasts for five minutes, and will cause ships to remain in space for a full 5 minutes after logging off. This 5 minute timer is not extended even if NPCs continue their aggression after the player logs off (unlike the capsuleer timer).
| **Capsuleer Log-Off Timer** (15 Minutes) |
| {{https://support.eveonline.com/hc/en-us/article_attachments/201415682/Crimewatch2_0_PVPTimer.png}} |
Also known as //PVP Flag// is similar to the NPC flag, this flag is activated when you use an offensive module on another player (including non-targeted weapons like Smartbombs) or another player uses such an effect on you. This flag lasts for fifteen minutes, and affected ships will remain in space after logging off for a full 15 minutes. If the ship is aggressed by another player while this timer is active, the timer will reset, potentially keeping the ship in space indefinitely.
| **Weapons Timer** (60 Seconds) |
| {{https://support.eveonline.com/hc/en-us/article_attachments/201391041/Crimewatch2_0_WeaponsTimerActive.png}} |
Also known as //Weapons Flag//, this flag becomes active when you activate any offensive module (weapons, stasis webifier etc) upon another player or NPC entity, including non-targeted modules such as Smartbombs. Regardless of the Security status of the solar system, having an active Weapons flag will prevent you from docking in any station, jumping through a stargate, ejecting from or boarding another ship while in space, and storing a ship in a corporation or fleet hangar. This flag lasts for 60 seconds, starting from the moment you open fire, and will renew each time you take further offensive action – meaning that you will have to wait a full 60 seconds after the last offensive action before being able to dock, jump etc (even if you lose your ship).
| **Suspect Timer** (15 Minutes) |
| {{https://support.eveonline.com/hc/en-us/article_attachments/201416672/Crimewatch2_0_SuspectTimer.png}} |
Only applicable in Empire-owned space (0.1 to 1.0), the //Suspect Flag// allows any other player to attack you without penalty for the duration of the timer. CONCORD and gate guns will not defend you, and the attacker will not receive a reduction in Security Standings. The Suspect flag lasts for 15 minutes, and actions that will activate the flag differ depending on the Security Status of the solar system. Pod killing a capsuleer with an active Suspect Timer will not result in security status loss or CONCORD response.
In** high-security space**, you can acquire a Suspect flag by stealing from a container or wreck, and by providing a remote assistance to other players in possession of an active Suspect Flag, Criminal Flag or Limited Engagement, or players who have Outlaw status (have -5 Security Status or lower). You can also be given a Suspect flag if a player activates a kill right on you.
In **low-security space**, targeting a player's ship (not their capsule) with any offensive module, including Smartbombs and other non-targeted weapons, will provoke a Suspect flag. Stealing from a container will also provoke the flag, though assisting outlaw players in low security space will not.
| **Criminal Timer** (15 Minutes) |
| {{https://support.eveonline.com/hc/en-us/article_attachments/201391151/Crimewatch2_0_CriminalTimer.png}} |
Like the Suspect flag, the //Criminal flag// only applies in Empire space. The Criminal flag, if triggered, will always override a Suspect flag, and any further actions that would ordinarily provoke a Suspect flag will be extend the Criminal timer by the same amount. As with the Suspect flag, the Security Status of the star system will affect the actions that provoke the flag.
In **high-security space**, activating any offensive module on another player's ship or capsule, that you are not legitimately allowed to attack (corpmates, war targets, for example), (including non-targeted modules like Smartbombs) will provoke a Criminal flag, as will assisting a player with a Criminal flag. If you receive a Criminal flag in high security space (or jump into high security space with an active criminal timer acquired elsewhere), you will not be able to initiate warp, or jump through a stargate and CONCORD will spawn and attack you, gate/station sentry guns will fire upon you, and any player may fire on you without penalty. Any jettisoned wrecks or containers will be auto-abandoned, allowing any other player to take from them without penalty.
While in **low security space**, you will acquire a Criminal flag for activating any offensive module against a player's capsule, and for directly assisting any other player in possession of a Criminal flag. If you receive a Criminal flag in low security space, you will not be prevented from warping or jumping, and CONCORD will not spawn to attack you – but you will be fired upon by gate/station sentries, your jettisoned wrecks and containers will be auto-abandoned, and any player may fire upon you without penalty.
| **Limited Engagement Timer** (5 Minutes) |
| {{https://support.eveonline.com/hc/en-us/article_attachments/201391141/Crimewatch2_0_LETimer.png}} |
//Limited Engagements// are created when a player attacks another player in possession of a Criminal or Suspect flag, or is considered an Outlaw. They only exist between players (not corporations, alliances etc), and allow each party the right to attack the other without legal penalty. Limited Engagements are considered to be active while hostilities are ongoing, and will remain active for five minutes after the last offensive action has been committed.
===== Avoiding Bubbles =====
**Warp disruption fields**, or more commonly **“bubbles”**, are nullsec exclusive mechanics that prevent ships from engaging their warp drives when inside them. Bubbles serve many purposes and come in various sizes, but with some simple planning and caution they are usually easy to avoid.
It is a good idea to get into the mindset that nearly every gate in nullsec is bubbled, as carelessness can often get you killed. Common areas to bubble include stations, gates, jump bridges, or any high traffic celestials. The number of bubbles and their placement will be dictated by how much your enemies want to kill you. A five man gate camp might have one or two bubbles on a gate on a vector from a station, while a dedicated operation might have upwards of twenty bubbles strategically placed around the system.
Avoiding bubbles usually boils down to whether or not you have tactical bookmarks for a specific celestial. Warping to a perch and scanning the gate will inform you of hostile presence as well as any bubbles in space. If you’re caught without a tactical look for any celestials in range of your destination, such as an asteroid belt or moon, and perform the scan from there.
You can avoid most bubbles by simply not warping directly from a high traffic area (such as a station) to a gate. Simply bouncing from a planet on the outer edge of a solar system can save your life.
...you can read this too: [[http://www.evealtruist.com/2012/03/bubble-mechanics.html|Azual Skoll's short(ish) guide on bubbles]].
===== Escaping Gate Camps =====
|{{http://3.bp.blogspot.com/-QxJPTsgimcM/UNJjvWHEWbI/AAAAAAAAAUk/bLdwTELOwCc/s400/camp-flowchart.png}}|
|The most important thing about surviving gate camps: **STAY CALM!**|
===== Additional Tips=====
When local is up press CTRL+A this will mark all who is in local if someone enters the eye will catch it.
If you end up travelling in your ratting ship fit Warp Core Stabilizer in the low slot (will save you from really bad gank attempts) , leave the ratting ship in your target ratting system and only travel when needed with it.
If you travel and find local has neutrals and you dont have ping bookmarks press alt+shift+x to add moons in space not overview find a moon that is close to the gate you want to travel to and activate tracking camera narrow the dscan and you can now check for bubble camp,this also allows you to warp from not being inline to drag bubbels.
Note that moons can have pos towers on it it so only use it in a pinch.
{{tag>general guide firstweek all english}}