User:Uryence/Gate camps: Difference between revisions

Line 81:

== Avoiding camps ==

If you want to be sure to avoid gatecamps, ensure your journey is [[Scouting|scouted]] by someone else or by an alt. Outside of high sec, where camps are obscured by general traffic, sensible scouting more-or-less guarantees that you won't unknowingly toss your main ship into a camp. This is the single best method to avoid gatecamp problems.

=== Routefinding ===

Many chokepoints in EVE's geography are fairly obvious if you look at a map, and you can forewarn yourself simply by looking at the shape of the gate network. Similarly, if you plan to take the [[Thera]] entrance hole nearest to Jita, you should immediately ask yourself whether it is likely to be camped.

Near-up-to-date data can add another useful layer. Dotlan can show you recent figures for ship and pod kills in a system. If you see a chokepoint system with high ship kills, there's a decent chance of a gatecamp there. Manually checking a system on [https://zkillboard.com zKillboard] will give you even more up-to-date information.

The third-party [https://eve-gatecheck.space/eve/ Gatecamp Check] tool can automate some of this intel-gathering work. This tool will scout your route using zKillboard and try to identify any camps along the route, coloring the camped systems in red. If smartbombs, interdictors or HICs are present on the kill reports for the camp it will post a large warning for that system. Since this website pulls from zKillboard, it can be delayed for 15–30 minutes in reporting a new camp. If you are camping and you want to avoid intel detection, this gives you a rough idea of how often you might want to consider shifting position!

=== Fitting ===

@@ Line 81: / Line 81: @@
 == Avoiding camps ==
+If you want to be sure to avoid gatecamps, ensure your journey is [[Scouting|scouted]] by someone else or by an alt. Outside of high sec, where camps are obscured by general traffic, sensible scouting more-or-less guarantees that you won't unknowingly toss your main ship into a camp. This is the single best method to avoid gatecamp problems.
 === Routefinding ===
+Many chokepoints in EVE's geography are fairly obvious if you look at a map, and you can forewarn yourself simply by looking at the shape of the gate network. Similarly, if you plan to take the [[Thera]] entrance hole nearest to Jita, you should immediately ask yourself whether it is likely to be camped.
+Near-up-to-date data can add another useful layer. Dotlan can show you recent figures for ship and pod kills in a system. If you see a chokepoint system with high ship kills, there's a decent chance of a gatecamp there. Manually checking a system on [https://zkillboard.com zKillboard] will give you even more up-to-date information.
+The third-party [https://eve-gatecheck.space/eve/ Gatecamp Check] tool can automate some of this intel-gathering work. This tool will scout your route using zKillboard and try to identify any camps along the route, coloring the camped systems in red. If smartbombs, interdictors or HICs are present on the kill reports for the camp it will post a large warning for that system. Since this website pulls from zKillboard, it can be delayed for 15–30 minutes in reporting a new camp. If you are camping and you want to avoid intel detection, this gives you a rough idea of how often you might want to consider shifting position!
 === Fitting ===