Roles in Incursions: Difference between revisions

Line 80:

* If the one taking primary aggro is taking damage rapidly as you land on site, put one or two reppers on them before sorting out the capacitor transmitter chain (then apply the rest of your reppers if needed).

* Pre-lock everyone in Vanguards (Advanced Target Management III allows you to lock all 10 members).

* Locking from the watch list is incredibly fast and efficient (CTRL + ~~leftclick)~~.

* Locking from the watch list is incredibly fast and efficient using {{button|CTRL}} + {{button|LMB}}.

* Have your fleet members on your overview, so you can see if you have members in the fleet that you haven't locked up (the icon will tell if it's a locket fleet member or not).

* Use only as many reppers as you need, don't over-repair because then you'll be too slow to respond to shifting aggro.

Line 247:

''Gameplay:''

* Pay attention. It's a very boring job but it has to be done. If you find yourself losing focus, just say so and remove yourself. No harm, no foul. It's just that we'll count on you looking at local.

** A useful technique for watching local is to ~~'''~~SHIFT~~'''~~-click to highlight all names currently in local, alternatively just use ~~'''~~CTRL + A~~'''~~ to select everyone currently in local. New arrivals to the system will appear a different color, making it easier to keep track, especially in busy systems.

** A useful technique for watching local is to {{button|SHIFT}}-click to highlight all names currently in local, alternatively just use {{button|CTRL}} + {{button|A}} to select everyone currently in local. New arrivals to the system will appear a different color, making it easier to keep track, especially in busy systems.

** In the settings buttons immediately under the "local" chat window title, "show compact member list" can be clicked to allow more names to be seen at once. Again, this is most useful for busy systems. See [[Identifying War Targets in Local]] for more information.

** In the settings buttons immediately under the '''local''' chat window title, '''show compact member list''' can be clicked to allow more names to be seen at once. Again, this is most useful for busy systems. See [[Identifying War Targets in Local]] for more information.

* If you don't have a cloak, sit docked in a station with the local window up, that'll be sufficient. Alternatively sit at a safespot in a cheap shuttle or a rookie ship.

* With a cloak you can sit on grid, in view of the gate you're picketing, to combine both local and a visual on the enemy capsuleer or fleet. That way you could not only announce to the fleet that a war target is coming, but also what ship he's flying.

* If war targets are active in the nearby systems, it would help if you reported to the fleet commander on a regular basis.

** Whenever you hear the fleet commander call for the wing warp out of their current site, chime up and say something like ''"Picket reporting in, all quiet!"''.

** Whenever you hear the fleet commander call for the wing warp out of their current site, chime up and say something like ''"Picket reporting in, all quiet!"'' or ''"Picket system clear!"'' if you want to be short and to the point.

* If the corporation has very few members, keep them watch listed in your contacts list.

* Have the intel channel up, for extra information about enemy movements.

Line 325:

* Make note of fits and ask for advice if you are not sure if the fit is adequate or not. See [[Fitting principles|fitting principles]] for guidance on tank and don't forget that you could easily ask the pilot what their resist profile is, their raw shield hit points, their engagement range and so forth, if it's not obvious from the fit itself.

* Separate people who are ready and in system from those who are still making their way there (or simply ask them to X-up when they get there).

* Catch up in the incursions.e-uni channel and update the waiting list between sites, then post the updated waiting list to remind people you are still forming/active.

* Catch up in the {{co|coral|incursions.e-uni}} channel and update the waiting list between sites, then post the updated waiting list to remind people you are still forming/active.

** Keeping a copy of the waitlist in your ingame notepad is a good idea, for easy editing and copying (font-formatting isn't copied over).

** You can also use the CTRL + Up/Down function in your chat-window (keeps the formatting, allows editing, but is somewhat unreliable/unpredictable).

** You can also use the {{button|CTRL}} + {{button|Up}}/{{button|Down}} function in your chat-window (keeps the formatting, allows editing, but is somewhat unreliable/unpredictable).

** Make sure to let people know if it's a shield or armour fleet, what type of sites you're doing, if the fleet is forming or active etc.

** Keep track of whether or not logistics pilots are logistics IV or V, what logistics they can bring (or both) etc.

Line 337:

** A short '''SFWL''' (shield fleet waitlist) abbreviation or just calling it '''Vanguards''' works for a shield fleet doing vanguards, since that's what we do most of the time.

* When drops are announced ahead of time, get the replacement(s) ready.

* Remember that you can invite people from local (where they should be, ready to go, if they are on the waitlist) even though they haven't spoken up recently in ''incursions.e-uni''.

* Remember that you can invite people from local (where they should be, ready to go, if they are on the waitlist) even though they haven't spoken up recently in {{co|coral|incursions.e-uni}}.

* If someone isn't responding on mumble or in incursions.e-uni, you could always try initiating a conversation with them (it'll fail if they are offline for example). Or you can just skip them and go for the next person in the waitlist, because it is not your job to make sure they are ready.

* Keep the MOTD updated with the following information.

Line 345:

** Who the booster(s), picket(s) and scout is, as well as a reminder to tip them.

** ''Optional:'' Who the anchor is.

** While there are other important things to know about a fleet, who the logistics are, who the dronebunny is and so forth, these things aren't best promoted in the MOTD. Logistics 'L' up each site and ~~you can have your~~ dronebunny 'DDD' up every site ~~instead, as~~ that would ~~be a constant reminder not only~~ who the dronebunny is, ~~but also~~ to ~~actually launch your drones and assign them~~.

** While there are other important things to know about a fleet, who the logistics are, who the dronebunny is, who the anchor is and so forth, these things aren't always best promoted in the MOTD. Logistics {{co|coral|"L"}} up each site and the dronebunny {{co|coral|"DDD"}} and the anchor {{co|coral|"AAA"}} up at the beginning of every site. If people get into the habit of looking for that they would always know who the logi, dronebunny and anchor is, even if the message of the day isn't updated and they'd immediately change to the new person should they be swapped out.

== Wing Commander ==

@@ Line 80: / Line 80: @@
 * If the one taking primary aggro is taking damage rapidly as you land on site, put one or two reppers on them before sorting out the capacitor transmitter chain (then apply the rest of your reppers if needed).
 * Pre-lock everyone in Vanguards (Advanced Target Management III allows you to lock all 10 members).
-* Locking from the watch list is incredibly fast and efficient (CTRL + leftclick).
+* Locking from the watch list is incredibly fast and efficient using {{button|CTRL}} + {{button|LMB}}.
 * Have your fleet members on your overview, so you can see if you have members in the fleet that you haven't locked up (the icon will tell if it's a locket fleet member or not).
 * Use only as many reppers as you need, don't over-repair because then you'll be too slow to respond to shifting aggro.
@@ Line 247: / Line 247: @@
 ''Gameplay:''
 * Pay attention. It's a very boring job but it has to be done. If you find yourself losing focus, just say so and remove yourself. No harm, no foul. It's just that we'll count on you looking at local.
-** A useful technique for watching local is to '''SHIFT'''-click to highlight all names currently in local, alternatively just use '''CTRL + A''' to select everyone currently in local. New arrivals to the system will appear a different color, making it easier to keep track, especially in busy systems.
+** A useful technique for watching local is to {{button|SHIFT}}-click to highlight all names currently in local, alternatively just use {{button|CTRL}} + {{button|A}} to select everyone currently in local. New arrivals to the system will appear a different color, making it easier to keep track, especially in busy systems.
-** In the settings buttons immediately under the "local" chat window title, "show compact member list" can be clicked to allow more names to be seen at once. Again, this is most useful for busy systems. See [[Identifying War Targets in Local]] for more information.
+** In the settings buttons immediately under the '''local''' chat window title, '''show compact member list''' can be clicked to allow more names to be seen at once. Again, this is most useful for busy systems. See [[Identifying War Targets in Local]] for more information.
 * If you don't have a cloak, sit docked in a station with the local window up, that'll be sufficient. Alternatively sit at a safespot in a cheap shuttle or a rookie ship.
 * With a cloak you can sit on grid, in view of the gate you're picketing, to combine both local and a visual on the enemy capsuleer or fleet. That way you could not only announce to the fleet that a war target is coming, but also what ship he's flying.
 * If war targets are active in the nearby systems, it would help if you reported to the fleet commander on a regular basis.
-** Whenever you hear the fleet commander call for the wing warp out of their current site, chime up and say something like ''"Picket reporting in, all quiet!"''.
+** Whenever you hear the fleet commander call for the wing warp out of their current site, chime up and say something like ''"Picket reporting in, all quiet!"'' or ''"Picket system clear!"'' if you want to be short and to the point.
 * If the corporation has very few members, keep them watch listed in your contacts list.
 * Have the intel channel up, for extra information about enemy movements.
@@ Line 325: / Line 325: @@
 * Make note of fits and ask for advice if you are not sure if the fit is adequate or not. See [[Fitting principles|fitting principles]] for guidance on tank and don't forget that you could easily ask the pilot what their resist profile is, their raw shield hit points, their engagement range and so forth, if it's not obvious from the fit itself.
 * Separate people who are ready and in system from those who are still making their way there (or simply ask them to X-up when they get there).
-* Catch up in the incursions.e-uni channel and update the waiting list between sites, then post the updated waiting list to remind people you are still forming/active.
+* Catch up in the {{co|coral|incursions.e-uni}} channel and update the waiting list between sites, then post the updated waiting list to remind people you are still forming/active.
 ** Keeping a copy of the waitlist in your ingame notepad is a good idea, for easy editing and copying (font-formatting isn't copied over).
-** You can also use the CTRL + Up/Down function in your chat-window (keeps the formatting, allows editing, but is somewhat unreliable/unpredictable).
+** You can also use the {{button|CTRL}} + {{button|Up}}/{{button|Down}} function in your chat-window (keeps the formatting, allows editing, but is somewhat unreliable/unpredictable).
 ** Make sure to let people know if it's a shield or armour fleet, what type of sites you're doing, if the fleet is forming or active etc.
 ** Keep track of whether or not logistics pilots are logistics IV or V, what logistics they can bring (or both) etc.
@@ Line 337: / Line 337: @@
 ** A short '''SFWL''' (shield fleet waitlist) abbreviation or just calling it '''Vanguards''' works for a shield fleet doing vanguards, since that's what we do most of the time.
 * When drops are announced ahead of time, get the replacement(s) ready.
-* Remember that you can invite people from local (where they should be, ready to go, if they are on the waitlist) even though they haven't spoken up recently in ''incursions.e-uni''.
+* Remember that you can invite people from local (where they should be, ready to go, if they are on the waitlist) even though they haven't spoken up recently in {{co|coral|incursions.e-uni}}.
 * If someone isn't responding on mumble or in incursions.e-uni, you could always try initiating a conversation with them (it'll fail if they are offline for example). Or you can just skip them and go for the next person in the waitlist, because it is not your job to make sure they are ready.
 * Keep the MOTD updated with the following information.
@@ Line 345: / Line 345: @@
 ** Who the booster(s), picket(s) and scout is, as well as a reminder to tip them.
 ** ''Optional:'' Who the anchor is.
-** While there are other important things to know about a fleet, who the logistics are, who the dronebunny is and so forth, these things aren't best promoted in the MOTD. Logistics 'L' up each site and you can have your dronebunny 'DDD' up every site instead, as that would be a constant reminder not only who the dronebunny is, but also to actually launch your drones and assign them.
+** While there are other important things to know about a fleet, who the logistics are, who the dronebunny is, who the anchor is and so forth, these things aren't always best promoted in the MOTD. Logistics {{co|coral|"L"}} up each site and the dronebunny {{co|coral|"DDD"}} and the anchor {{co|coral|"AAA"}} up at the beginning of every site. If people get into the habit of looking for that they would always know who the logi, dronebunny and anchor is, even if the message of the day isn't updated and they'd immediately change to the new person should they be swapped out.
 == Wing Commander ==