|
|
| Line 344: |
Line 344: |
| == Waitlist manager == | | == Waitlist manager == |
| ''Primary function:'' | | ''Primary function:'' |
| * Keep the fleet running smoothly by maintaining an organized cue of players ready to instantly fill fleet roles as existing fleet members retire. | | * Carry out your basic role in the fleet (if you're ongrid with the fleet that comes first, waitlist second). |
| * If you have the Boss Star (typical case): watch Fleet History for disconnects. Know your fleet composition. If the Wing Commander disconnects, put someone with appropriate Wing Command skills in the Wing Commander position. Loss of Wing Commander removes wing boosts, which must be maintained. | | * Advertise the running fleet in the ingame chat channel and keep track of the people wanting to join the fleet. |
| | |
| Remember: Waitlist Manager is a secondary job. Your basic role (Picket, Scout/Hacker or Damage Dealer) has priority, except for the rare few seconds required to reassign a Wing Commander.
| |
|
| |
|
| ''Secondary function:'' | | ''Secondary function:'' |
| | | * Add people to the fleet and maintain the fleet's message of the day. |
| * Advertise the running fleet on Incursions.E-UNI. Keep track of the waiting list by order of precedence, first name (opsec!) and role. | |
| * Check that capsuleers are in-system and in Mumble.
| |
| * Check that ships are properly fitted (shield tanks for shield fleets, armour tank for armour fleets, travel fittings have been removed, etc.) Ask Fleet Commander for approval of any fit you are not familiar with. Ask approval in general.
| |
| * Make sure out-of-corp alts and alumni do not have outstanding Wars Declared or Kill Rights against them, endangering the fleet.
| |
| * Typically, Wait List Manager has the boss star- or is "Fleet Boss". Fleet Boss can invite new players in to fleet, move fleet members or revoke capabilities. Use extreme care, consult with Fleet Commander about such actions. Consult the Fleet Composition via the Fleet menu. Know the capsuleers qualified for the Wing Command position. If the Wing Commander disconnects, thus removing wing boosts, put someone else with appropriate Wing Command skills in the Wing Commander spot.
| |
| * Fleet Boss maintains the MOTD (Message of the Day). This Fleet Window message catalogs the Fleet Commander, Drone Bunny and Logistics Pilots. Off Grid positions are listed for tip-outs: Picket(s), Scout/Hacker, Off Grid Booster.
| |
|
| |
|
| ''Requirements:'' | | ''Requirements:'' |
| * Ability to multi-task and pay attention to administrative details. | | * Ability to multi-task and pay attention to administrative details. |
| <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 site-running''', the duties of your primary function as a damage dealer or logistics pilot. Picket needs to continuously check local for threats. All the wait-list duties come second to this. Your attention should never be diverted to the point where your primary function is compromised. Deal with your Wait List duties in-between sites, preferably. | | ''Gameplay:'' |
| * Ask to be made Fleet Boss: this allows you to move people around and invite them to the fleet. Verify moves with the Fleet Commander. Keep FC informed and in control, while removing administrative details. | | * Remember that the role of waitlist manager comes second to any other role you hold in the fleet. If you're a damage dealer, logistics, ongrid booster, scout/hacker or picket, those duties come first. |
| ** Utilize the drag-and-drop feature for both fleet invites and for moving people into new position. If fleet members request role changes, facilitate those changes for them when required or to relieve them of an administrative task they may be unfamiliar with. | | ** If you find yourself overwhelmed you can leave waitlist duties for when a site is finished and you're warping to the next site. In most cases that'll give you more than enough time to update the waitlist and sort out any changes to the message of the day while warping. |
| | * Routinely post advertisement in the {{co|coral|incursions.e-uni}} channel every 5-10 minutes, so people are informed of the running fleet or their place in the cue. |
| | ** One easy way of doing this is to post the advert between every site. |
| | ** You can either keep a copy of the advert/waitlist in your ingame notepad (reliable, but formatting and auto-links won't copy over) or use the {{button|CTRL}} + {{button|Up}}/{{button|Down}} function to edit your previous messages on the fly (keeps font formatting but is limited to how far back it goes). |
| | ** A concise waitlist message has the benefit of not spamming out everything else in chat. Some useful shorthands would be {{co|lime|+l}} (dd + any logi), {{co|lime|+s}} (dd + scimitar), {{co|lime|+b}} (dd + basilisk) or just {{co|lime|l/s/b}} (any logi or scimitar/basilisk only). If you're running assaults you'd also specify {{co|lime|T3/sc}} (strategic cruiser), {{co|lime|cs}} (command ship) and {{co|lime|sn}} (sniper). |
| | ** A short {{co|coral|"SFWL"}} (shield fleet waitlist) abbreviation or just calling it {{co|coral|"Vanguards"}} works for a shield fleet running Vanguard sites because that's what the Uni does most of the time. |
| | * Before adding someone to the waitlist, check the following: |
| | ** Check that the pilot is in the staging system and on Mumble. If a pilot x-up before they are ready in the staging system, tell them to x-up again when they arrive in the staging system. Priority goes to the people who prepared and are ready in system. |
| | ** Check that the ship is properly fitted according to our [[fitting principles]] (feel free to ask your fleet commander if you're not sure). |
| | ** Check that out-of-corp alts and alumni are not at war or have active [[Kill Rights|kill rights]] on them, as that might endanger the fleet. |
| | * Ask to be made '''fleet boss'''; this allows you to move people around and invite them to the fleet and update the message of the day. |
| | ** Be sure to keep the commander updated when people are invited to the fleet, the goal is to keep the fleet commander informed and in control while removing administrative details. |
| | ** The drag-and-drop feature is very handy for both fleet invites and for moving people into new position. |
| ** Be sure to enable ''free-move'' so people can move themselves in and out of positions when needed. | | ** Be sure to enable ''free-move'' so people can move themselves in and out of positions when needed. |
| * Make note of fits and regular fleet members. Ask for advice if you are not sure of a fit. See [[Fitting principles|fitting principles]] for guidance. Experienced WL Managers might ask for the resist profile, raw shield hit points, engagement range if not obvious from the fit. When in doubt, Fleet Commander always has final approval. | | ** When a fleet pilot announces their retirement from a role ahead of time, get the replacement ready but don't invite them to fleet until it's time for them to actually come ongrid or replace one of the offgrids. |
| * The official wait list consists of people who are ready and in system. You may wish to keep an informal list of those who are still making their way to the focus. Ask them to X-up to get on the official list when they are prepared and in system.
| | *** Simply ask the first person in the waitlist to x-up again to be invited. |
| * Post advertisement in the {{co|coral|incursions.e-uni}} channel. Post the updated waiting list every five to ten minutes to remind people the fleet is still active.
| | *** If the first person in the cue isn't responding, keep them on the waitlist but skip them for this time and pick the next one on the waitlist. If they repeatedly fail to respond, feel free to drop them from the waitlist. |
| ** Hint: Keep a copy of the fleet advertisement/ waitlist in your ingame notepad. It's easy to edit and copy. (font-formatting isn't maintained.)
| | ** Remember to inform the fleet commander that you added someone to the fleet and who that person is as well as the role they'll take. |
| ** The {{button|CTRL}} + {{button|Up}}/{{button|Down}} function in your chat-window keeps font formatting and allows editing, but is somewhat unreliable.
| | ** Keep the message of the day (MOTD) updated with the following information: |
| ** Advertise to let people know a shield or armour fleet is running or forming and what type of sites you're doing.
| | *** System the fleet is running in, fleet commander, logistics pilots, dronebunny as well as picket(s) and scout (and a reminder to tip the later two, see [[#Unpaid_roles_and_tipping|unpaid roles and tipping]] below for more information). |
| ** Keep track of the logistics pilot's ability and ships: logistics IV or V, what logistics they bring.
| | *** {{co|plum|(Optional)}} If you're running non-vanguards, like assauls, who the '''anchor''' is. |
| ** Make note of people with {{sk|Wing Command|II}} or better, to be put in the wing command position.
| | *** People who pay attention will know does what, as logistics {{co|coral|"L"}}-up each site, the dronebunny {{co|coral|"DDD"}}-up and the anchor {{co|coral|"AAA"}}-up at the beginning of every site. Pickets and scout/hackers are in the offgrid squad in fleet etc. That said, it doesn't hurt to keep this in the message of the day, as long as it is kept up-to-date (as it allows quick reload and right-click on offgrids to tip or for newly invited pilots to quickly catch up). |
| ** A concise waitlist message has the benefit of not spamming out everything else in chat.
| |
| *** Useful shorthands: {{co|lime|+l}} (dd + any logi), {{co|lime|+s}} (dd + scimitar), {{co|lime|+b4/5}} (dd + basilisk, logistics 4 or 5) or just {{co|lime|l/s/b}} [b4-5] (any logi or scimitar/basilisk only), {{co|lime|T3/sc}} (strategic cruiser), {{co|lime|cs}} (command ship) and {{co|lime|sn}} (sniper).
| |
| | |
| ** A short '''SFWL''' (shield fleet waitlist) abbreviation or just calling it '''Vanguards''' works for a shield fleet running Vanguard sites because that's what the Uni does most of the time.
| |
| * When a fleet pilot announces their retirement from a role ahead of time, get the replacement(s) ready but don't invite them to fleet until the retiring pilot has stopped playing. A retiring pilot may appreciate your assistance moving them offgrid to facilitate their tip-outs. At this time, invite a the first ready player from the wait list. | |
| * Get confirmation that new players are ready to go before inviting to fleet. If the Wait List Manager is in-system, they can invite a player by verbal confirmations from the Local window. Picket will need to request a second X-up in{{co|coral|incursions.e-uni}}. | |
| * If someone isn't responding on mumble or in incursions.e-uni, you may try initiating a Conversation with them. You may also pick the next person who is prepared in the waitlist. Your job to keep the fleet running, not chase down afk capsuleers. | |
| * Keep the MOTD updated with the following information: | |
| ** System the fleet is running in, Fleet Commander, Logistics Pilots, Drone Bunny | |
| ** Offgrid positions: booster(s), picket(s) and scout, as well as a reminder to tip them.
| |
| ** ''Optional:'' For an Assault system- Who the Anchor is. | |
| ** Who the logistics are, dronebunny identity, who the anchor is and so forth, may be omitted from the MOTD by Fleet Commander's custom, Fleet Boss error or delay. 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. Pilots should be in the habit of looking for this information to always know who the logi, dronebunny and anchor are, even if the message of the day isn't updated. Pilots can immediately change to the new person covering each role in the event personnel changes. | |
|
| |
|
| == Wing Commander == | | == Wing Commander == |
