Anatomy of Incursions: Difference between revisions

Line 20:

=== 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), ''"DD"'' (usually excluding the dronebunny), ''"Snipers"'', ''"Logistics"'', ''"Dronebunny"'' or something similar, then follow up with the actual command. ~~The use of keywords will make it clear that you~~'~~re issuing in order and to whom~~. ~~Have them confirm orders if need be~~, ~~even if it~~'~~s just~~ a ~~simple~~ ''"Ok"'', ''"~~Copy~~"'' or ''"~~Roger!~~"''.

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), ''"DD"'' (usually excluding the dronebunny), ''"Snipers"'', ''"Logistics"'', ''"Dronebunny"'' or something similar, then follow up with the actual command. For example, ''"Fleet ... 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."''.

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!"'' keywords to get people to stop talking if you need to. Put yourself as prioritized speaker, if you own the channel, just in case someone doesn't. ~~It also serves~~ a ~~purpose in letting~~ the tagger know what to tag. This is especially helpful if you're commanding a fleet as a logistics pilot, or when doing larger sites where tagging is delegated to each group's commander.

The use of keywords will make it clear that you're issuing in 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. Put yourself as prioritized speaker, if you own the channel, just in case someone doesn't. 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"''.

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.

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.

=== Stay calm ===

@@ Line 20: / Line 20: @@
 === 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), ''"DD"'' (usually excluding the dronebunny), ''"Snipers"'', ''"Logistics"'', ''"Dronebunny"'' or something similar, then follow up with the actual command. The use of keywords will make it clear that you're issuing in order and to whom. Have them confirm orders if need be, even if it's just a simple ''"Ok"'', ''"Copy"'' or ''"Roger!"''.
+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), ''"DD"'' (usually excluding the dronebunny), ''"Snipers"'', ''"Logistics"'', ''"Dronebunny"'' or something similar, then follow up with the actual command. For example, ''"Fleet ... 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."''.
-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!"'' keywords to get people to stop talking if you need to. Put yourself as prioritized speaker, if you own the channel, just in case someone doesn't. It also serves a purpose in letting the tagger know what to tag. This is especially helpful if you're commanding a fleet as a logistics pilot, or when doing larger sites where tagging is delegated to each group's commander.
+The use of keywords will make it clear that you're issuing in 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. Put yourself as prioritized speaker, if you own the channel, just in case someone doesn't. 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"''.
+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.
+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.
 === Stay calm ===