More actions
| Line 9: | Line 9: | ||
*Pay attention to local, how many people are around (if feasible). A spike in player numbers in lowsec is probably a good indicator that someone's on the way. Keep the local tab seperated out, and an eye on the icons in overview for nasty colours. Check corp bios, especially for kill policies. | *Pay attention to local, how many people are around (if feasible). A spike in player numbers in lowsec is probably a good indicator that someone's on the way. Keep the local tab seperated out, and an eye on the icons in overview for nasty colours. Check corp bios, especially for kill policies. | ||
*Wormhole space: Bad idea to type into Local, as it alerts everyone to your presence. Use scan probes+directional scanner to see who else is there. | *Wormhole space: Bad idea to type into Local, as it alerts everyone to your presence. Use scan probes+directional scanner to see who else is there. | ||
*Use combat probes to check before warping to a point, or use the directional scanner (max range, and 360 degrees) | *Use combat probes to check before warping to a point, or use the directional scanner (max range, and 360 degrees). Assign someone in the fleet to spam directional scans. | ||
*Know the shipnames in your group. Having a list of shipnames or a naming convention is a good way to know if that ship warping in is an ally or not. | *Know the shipnames in your group. Having a list of shipnames or a naming convention is a good way to know if that ship warping in is an ally or not. | ||
*Prepare alternate routes. The border between highsec and lowsec (the highsec-lowsec interface) tends to have lots of pirates. | *Prepare alternate routes. The border between highsec and lowsec (the highsec-lowsec interface) tends to have lots of pirates. | ||