Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Roles in Incursions: Difference between revisions

From EVE University Wiki
m Picket: removed statement to watchlist members of small corps since "buddy lists" are now consensual only.
Line 337: Line 337:
== Waitlist manager ==
== Waitlist manager ==
''Primary function:''
''Primary function:''
* Carry out your basic role (preferably a damage dealer).
* Carry out your basic role (preferably a damage dealer but can also be done by scout/hacker or picket).
''Secondary function:''
''Secondary function:''
* Keep track of the waiting list.
* Keep track of the waiting list.
Line 346: Line 346:
* None.
* None.
<p>'''<font size=2>Ways to improve</font>'''</p>
<p>'''<font size=2>Ways to improve</font>'''</p>
* Remember that '''first and foremost you need to focus on the actual siterunning''' and the duties of your primary function as a damage dealer or logistics pilot. All the waitlist duties come second to this and your attention should never be diverted to the point where your primary function is compromised. Deal with your waitlist duties inbetween sites, preferably.
* Remember that '''first and foremost you need to focus on the actual siterunning''' and the duties of your primary function as a damage dealer or logistics pilot, alternatively if you're picket you'll need to make sure you're still able to continuously check local for threats. All the waitlist duties come second to this and your attention should never be diverted to the point where your primary function is compromised. Deal with your waitlist duties inbetween sites, preferably.
* Ask to be made Boss, that will allow you to move people around and invite them to the fleet, making your job easier.
* Ask to be made Boss, that will allow you to move people around and invite them to the fleet, making your job easier.
** Utilize the drag-and-drop feature for both fleet invites and for moving people into new position.
** Utilize the drag-and-drop feature for both fleet invites and for moving people into new position.
Line 363: Line 363:
*** Similarly the strategic cruiser or command ship mention is only relevant for assaults if you do the [[Nation Consolidation Network]] site, so skip this too if you're running vanguards for example.
*** Similarly the strategic cruiser or command ship mention is only relevant for assaults if you do the [[Nation Consolidation Network]] site, so skip this too if you're running vanguards for example.
** 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.
** 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.
* When drops are announced ahead of time, get the replacement(s) ready but don't invite them until they should come ongrid.
* 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}}.
* 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.
* 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.
* Keep the MOTD updated with the following information.
** Type of fleet (shield or armour, vanguard or assault etc).
** System the fleet is running in.
** System the fleet is running in.
** Name of the on-demand channel on Mumble.
** Who the booster(s), picket(s) and scout is, as well as a reminder to tip them.
** Who the booster(s), picket(s) and scout is, as well as a reminder to tip them.
** ''Optional:'' Who the anchor is.
** ''Optional:'' Who the anchor is if you're doing assaults.
** 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.
** 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.