Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

User:Uryence/Scouting: Difference between revisions

From EVE University Wiki
Uryence (talk | contribs)
Uryence (talk | contribs)
Line 323: Line 323:


You might also decide to, or be asked to, return to the intel-gathering part of scouting. If so, move out of the fight or even totally off-grid, and return to using d-scan and Local to monitor the surrounding space. Combat comms can be busy, so triage the information you pass on to the FC: a new gang spiking Local is significant and must be reported; a single newly-arriving damage-dealing ship at or below the size class of the existing enemies might not be crucial if the FC is busy communicating a tactical move; a single potential hard cyno definitely requires a call-out ("FC, hostile Pilgrim just jumped in from Agoze").
You might also decide to, or be asked to, return to the intel-gathering part of scouting. If so, move out of the fight or even totally off-grid, and return to using d-scan and Local to monitor the surrounding space. Combat comms can be busy, so triage the information you pass on to the FC: a new gang spiking Local is significant and must be reported; a single newly-arriving damage-dealing ship at or below the size class of the existing enemies might not be crucial if the FC is busy communicating a tactical move; a single potential hard cyno definitely requires a call-out ("FC, hostile Pilgrim just jumped in from Agoze").
==== After combat ====
The moments after a fight, whether victorious, disastrous, or somewhere in between, are often some of the most dangerous in a fleet's life. Stay calm, look at d-scan, Local, and the map, and communicate with the FC about your next steps, whether those are hunting, extraction, or something else.


=== How to say it ===
=== How to say it ===