Anatomy of Incursions: Difference between revisions

Line 33:

= Commanding a fleet =

Remember that EVE is a game where ''"It depends!"'' is the single most important thing to remember. Don't blindly follow set tactics or kill-orders you've read here or somewhere else. Put things into perspective and adjust to what's happening in every site, where the enemies spawn as well as your current fleet composition. This is a good example of where the ''"why"'' (ability to put things into context) is more important than the ''"how"'' or ''"what"'' (rigid kill-order lists etc.), as knowing the ''"why"'' allows you to tackle anything the game throws at you, whereas only knowing the ''"how"'' or ''"what"'' will catch you off-guard whenever something out of order happens.

Remember that EVE is a game where {{co|wheat|''"It depends!"''}} is the single most important thing to remember. Don't blindly follow set tactics or kill-orders you've read here or somewhere else. Put things into perspective and adjust to what's happening in every site, where the enemies spawn as well as your current fleet composition. This is a good example of where the ''"why"'' (ability to put things into context) is more important than the ''"how"'' or ''"what"'' (rigid kill-order lists etc.), as knowing the ''"why"'' allows you to tackle anything the game throws at you, whereas only knowing the ''"how"'' or ''"what"'' will catch you off-guard whenever something out of order happens.

Do not underestimate the dangers of inflexibility or lack of knowledge surrounding the ''"why"''. A fleet led by someone who is flexible and adjusts to the actual situation and fleet composition can easily avoid disasters that would cause immediate losses for a fleet led by someone following a standard kill-order list without taking into consideration the fleet composition. Additionally, having the knowledge of ''"why"'' will allow you to foresee problems before they happen and act proactively instead of reactively.

Line 284:

== Issuing commands ==

It doesn't matter if you're calling target, calling for aligns or something else entirely; Always issue commands with a clear voice and repeat the command if it is really important. If possible, have keywords like ''"Fleet"'' (everyone), ''"Battleships"'' (mostly for align or warp purposes), ''"DD"'' (usually non-snipers excluding the dronebunny), ''"Snipers"'', ''"Logistics"'', ''"Dronebunny"'' or something similar, then follow up with the actual command. For example, ''"Battleships ... align down the gate"'', ''"Logistics ... L up"'', a series of ''"Snipers ... Anthem Neos are primary"'', ''"DD ... Augas are primary, then Deltole"'' and ''"Dronebunny ... go for the Tamas"'' or ''"Fleet ... align to broadcast, drones in."''.

It doesn't matter if you're calling target, calling for aligns or something else entirely; Always issue commands with a clear voice and repeat the command if it is really important. If possible, have keywords like {{co|wheat|''"Fleet"''}} (everyone), {{co|wheat|''"Battleships"''}} (mostly for align or warp purposes), {{co|wheat|''"DD"''}} (usually non-snipers excluding the dronebunny), {{co|wheat|''"Snipers"''}}, {{co|wheat|''"Logistics"''}}, {{co|wheat|''"Dronebunny"''}} or something similar, then follow up with the actual command. For example, {{co|wheat|''"Battleships ... align down the gate"''}}, {{co|wheat|''"Logistics ... L up"''}}, a series of {{co|wheat|''"Snipers ... Anthem Neos are primary"''}}, {{co|wheat|''"DD ... Augas are primary, then Deltole"''}} and {{co|wheat|''"Dronebunny ... go for the Tamas"''}} or {{co|wheat|''"Fleet ... align to broadcast, drones in."''}}.

The use of keywords will make it clear that you're issuing an order and to whom. This helps people realize a command is about to be given, especially if you have open comms allowing people to talk and ask questions while you're running sites. Use existing ''"Break, break!"'' or ''"Check, check!"'' keywords to get people to stop talking if you need to. If possible put yourself as prioritized speaker just in case someone doesn't stop talking. When you give orders to sub-groups of your fleet, have them confirm orders if need be, even if it's just a simple ''"Ok"'', ''"Copy"'' or ''"Roger"''.

The use of keywords will make it clear that you're issuing an order and to whom. This helps people realize a command is about to be given, especially if you have open comms allowing people to talk and ask questions while you're running sites. Use existing {{co|wheat|''"Break, break!"''}} or {{co|wheat|''"Check, check!"''}} keywords to get people to stop talking if you need to. If possible put yourself as prioritized speaker just in case someone doesn't stop talking. When you give orders to sub-groups of your fleet, have them confirm orders if need be, even if it's just a simple {{co|wheat|''"Ok"''}}, {{co|wheat|''"Copy"''}} or {{co|wheat|''"Roger"''}}.

In the example above, calling ''"DD ... Augas are primary, then Deltole"'' that would let the tagger know what to tag and all the damage dealers know what to lock up while waiting for tags. This is especially helpful if you're commanding a fleet as a logistics pilot and someone else tags, or when doing larger sites where tagging is delegated to each group's commander.

In the example above, calling {{co|wheat|''"DD ... Augas are primary, then Deltole"''}} that would let the tagger know what to tag and all the damage dealers know what to lock up while waiting for tags. This is especially helpful if you're commanding a fleet as a logistics pilot and someone else tags, or when doing larger sites where tagging is delegated to each group's commander.

Give people enough commands to know what to do and hit the ground running when they land on grid, but avoid overdoing it. No need to add commands for the entire wave right away, get people started, then amend target calls with secondary or tertiary targets once people have started shooting. The key is to give them enough targets to fill up their pre-locks, so they have secondary targets locked already when the primary goes down.

@@ Line 33: / Line 33: @@
 = Commanding a fleet =
-Remember that EVE is a game where ''"It depends!"'' is the single most important thing to remember. Don't blindly follow set tactics or kill-orders you've read here or somewhere else. Put things into perspective and adjust to what's happening in every site, where the enemies spawn as well as your current fleet composition. This is a good example of where the ''"why"'' (ability to put things into context) is more important than the ''"how"'' or ''"what"'' (rigid kill-order lists etc.), as knowing the ''"why"'' allows you to tackle anything the game throws at you, whereas only knowing the ''"how"'' or ''"what"'' will catch you off-guard whenever something out of order happens.
+Remember that EVE is a game where {{co|wheat|''"It depends!"''}} is the single most important thing to remember. Don't blindly follow set tactics or kill-orders you've read here or somewhere else. Put things into perspective and adjust to what's happening in every site, where the enemies spawn as well as your current fleet composition. This is a good example of where the ''"why"'' (ability to put things into context) is more important than the ''"how"'' or ''"what"'' (rigid kill-order lists etc.), as knowing the ''"why"'' allows you to tackle anything the game throws at you, whereas only knowing the ''"how"'' or ''"what"'' will catch you off-guard whenever something out of order happens.
 Do not underestimate the dangers of inflexibility or lack of knowledge surrounding the ''"why"''. A fleet led by someone who is flexible and adjusts to the actual situation and fleet composition can easily avoid disasters that would cause immediate losses for a fleet led by someone following a standard kill-order list without taking into consideration the fleet composition. Additionally, having the knowledge of ''"why"'' will allow you to foresee problems before they happen and act proactively instead of reactively.
@@ Line 284: / Line 284: @@
 == Issuing commands ==
-It doesn't matter if you're calling target, calling for aligns or something else entirely; Always issue commands with a clear voice and repeat the command if it is really important. If possible, have keywords like ''"Fleet"'' (everyone), ''"Battleships"'' (mostly for align or warp purposes), ''"DD"'' (usually non-snipers excluding the dronebunny), ''"Snipers"'', ''"Logistics"'', ''"Dronebunny"'' or something similar, then follow up with the actual command. For example, ''"Battleships ... align down the gate"'', ''"Logistics ... L up"'', a series of ''"Snipers ... Anthem Neos are primary"'', ''"DD ... Augas are primary, then Deltole"'' and ''"Dronebunny ... go for the Tamas"'' or ''"Fleet ... align to broadcast, drones in."''.
+It doesn't matter if you're calling target, calling for aligns or something else entirely; Always issue commands with a clear voice and repeat the command if it is really important. If possible, have keywords like {{co|wheat|''"Fleet"''}} (everyone), {{co|wheat|''"Battleships"''}} (mostly for align or warp purposes), {{co|wheat|''"DD"''}} (usually non-snipers excluding the dronebunny), {{co|wheat|''"Snipers"''}}, {{co|wheat|''"Logistics"''}}, {{co|wheat|''"Dronebunny"''}} or something similar, then follow up with the actual command. For example, {{co|wheat|''"Battleships ... align down the gate"''}}, {{co|wheat|''"Logistics ... L up"''}}, a series of {{co|wheat|''"Snipers ... Anthem Neos are primary"''}}, {{co|wheat|''"DD ... Augas are primary, then Deltole"''}} and {{co|wheat|''"Dronebunny ... go for the Tamas"''}} or {{co|wheat|''"Fleet ... align to broadcast, drones in."''}}.
-The use of keywords will make it clear that you're issuing an order and to whom. This helps people realize a command is about to be given, especially if you have open comms allowing people to talk and ask questions while you're running sites. Use existing ''"Break, break!"'' or ''"Check, check!"'' keywords to get people to stop talking if you need to. If possible put yourself as prioritized speaker just in case someone doesn't stop talking. When you give orders to sub-groups of your fleet, have them confirm orders if need be, even if it's just a simple ''"Ok"'', ''"Copy"'' or ''"Roger"''.
+The use of keywords will make it clear that you're issuing an order and to whom. This helps people realize a command is about to be given, especially if you have open comms allowing people to talk and ask questions while you're running sites. Use existing {{co|wheat|''"Break, break!"''}} or {{co|wheat|''"Check, check!"''}} keywords to get people to stop talking if you need to. If possible put yourself as prioritized speaker just in case someone doesn't stop talking. When you give orders to sub-groups of your fleet, have them confirm orders if need be, even if it's just a simple {{co|wheat|''"Ok"''}}, {{co|wheat|''"Copy"''}} or {{co|wheat|''"Roger"''}}.
-In the example above, calling ''"DD ... Augas are primary, then Deltole"'' that would let the tagger know what to tag and all the damage dealers know what to lock up while waiting for tags. This is especially helpful if you're commanding a fleet as a logistics pilot and someone else tags, or when doing larger sites where tagging is delegated to each group's commander.
+In the example above, calling {{co|wheat|''"DD ... Augas are primary, then Deltole"''}} that would let the tagger know what to tag and all the damage dealers know what to lock up while waiting for tags. This is especially helpful if you're commanding a fleet as a logistics pilot and someone else tags, or when doing larger sites where tagging is delegated to each group's commander.
 Give people enough commands to know what to do and hit the ground running when they land on grid, but avoid overdoing it. No need to add commands for the entire wave right away, get people started, then amend target calls with secondary or tertiary targets once people have started shooting. The key is to give them enough targets to fill up their pre-locks, so they have secondary targets locked already when the primary goes down.