Anatomy of Incursions: Difference between revisions

Line 22:

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."''.

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"''.

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. 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.

Line 43:

If you don't, you'll end up with a fleet where things quickly degrade; People forgetting to broadcast, lock up new targets, reapply their guns after reloading, not responding fast enough to sudden commands etc. In such situations things spiral out of control really fast.

The simplest and most effective way of keeping things under control; your fleet safe and engaged, is to take control over fleet warps, aligning, entering, new waves and leaving sites.

The simplest and most effective way of keeping things under control; your fleet safe and engaged, is to take control over fleet warps, aligning, entering sites, new waves and leaving sites.

= Standard tactics =

@@ Line 22: / Line 22: @@
 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."''.
-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"''.
+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. 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.
@@ Line 43: / Line 43: @@
 If you don't, you'll end up with a fleet where things quickly degrade; People forgetting to broadcast, lock up new targets, reapply their guns after reloading, not responding fast enough to sudden commands etc. In such situations things spiral out of control really fast.
-The simplest and most effective way of keeping things under control; your fleet safe and engaged, is to take control over fleet warps, aligning, entering, new waves and leaving sites.
+The simplest and most effective way of keeping things under control; your fleet safe and engaged, is to take control over fleet warps, aligning, entering sites, new waves and leaving sites.
 = Standard tactics =