User:Menelmir

Guide to running a fleet

This checklist summarises the process for organising an EVE University fleet in advance using the typical EVE University process and support services. Such fleets typically form at EVE University staging areas using EVE University PvP doctrines which are eligible for SRP. If you want to run or ping for something at short notice using existing contract ships, or from a market location like Jita etc you may do. There are no strict rules around who can form and ping for a fleet, or what ships you fly, but the rules around SRP might be different.

Before the Fleet (start minimum of 5 days before the fleet)

• Decide broadly where your fleet will be going. Is it a fleet you will be taking to low sec for gate camping? Do you want to yeet out to null for hunting? Is it suitable for roaming in Pochven? If you are not sure, ask! The FC Team is here to help.

• Decide on a doctrine from the doctrines forum, based on the type of fleet you will be running. Familiarise yourself with the ships within the doctrine, the strengths and weaknesses and the ideal engagement type. If you are not sure on this, ask in Discord and someone can help you choosing a doctrine. our Magic Merlin doctrine is ideal for a first fleet if you are still not sure. Consider what ship brand new players should fly in order to participate.

• Decide on a date and time for the fleet that works for you. It is important you choose a time that works for you personally. This might mean lower numbers in quiet timezones, but any fleet in a low activity timezone is a win. Put up a forum post and a calendar event to let people know the fleet is happening. Include the date and time, location for undock, doctrine and anything else the fleet needs to know. (N.B. You will need the Sophomore title to post a calendar event. If you don't have that yet, just ask in Discord and someone can put up the calendar event for you).

• Consider whether you need anyone else to support you with the fleet. If you have not run many fleets before, would you like a more experienced FC to come along as a 2IC or for advice and feedback? If so, ask in the FC channels in Discord if someone can join you. If you are a more experienced FC, can you take a more inexperienced FC along with you to give them some experience? Again, ask in the FC channels in Discord. Work out what specialist roles you will need, like scouts - any snowflake roles? If you know people who are strong in those roles, message them and ask them if they will be available.

• Prepare fleet doctrines. Ensure fleet members have access to the necessary ship fittings and doctrines for the planned fleet. The EVE University Production Department can put all the ships you need on contract in Stacmon/PC9 for your fleet if you fill out a Fleet Support Program request with logistics, which needs 5 days notice.

• You may also like to put up a ‘pre-ping’ to hype for the fleet 24 hours beforehand (post in ⁠ping-uni-wide for Strat-Ops, or ⁠ping-pvp for others)

On the day of the fleet

• Make sure the doctrine ships are available. Try to check a few hours before the fleet so there is time to fix any issues. If you have requested ships through the Fleet Support Program, check they are up on contract. If not, drop a line to logistics checking they will be available in time for the fleet. You can do this by pinging @Production Officer in ⁠ping-misc in Discord

• If you have arranged for another FC to join you, or any scouts or snowflake roles, arrange to meet with them before you ping for the fleet. Make sure you discuss doctrine, plan the route/destination for the fleet, the ideal engagement type, tactics and any questions or requests you have for them.

• Once you are ready, form the fleet in-game and set the MOTD and the fleet advert. It is best to do this around 30 minutes before you plan to undock the fleet so you have time to set everything up as you want it. Make sure you include in the MOTD which mumble channel you are using, what ships and required in order of preference, any bookmark folder fleet members may need access to, a list of everyone the fleet members should have on their watchlist (FC, 2IC, scouts), any filaments, drugs or implants the fleet members should purchase and anything else crucial the fleet needs to know. Having this information in the MOTD will reduce questions and make it easier to answer them. [TODO: Sample MOTDs]

• Put out a ping on Discord for the fleet using the ping tool [TODO: Ping tool here]. Make sure you mention in the ping what the doctrine is, by setting out which ships are required in order of preference. If ships are available on contract, mention this in the ping. Also make sure you announce the fleet is up in the Alliance chat channel in-game, with a link to the fleet advert.

• (Optional) Set up a Fleet Credit Link using the instructions [TODO: FAT Stuff here].

During the fleet

• As people join the fleet, check what ships they are flying in the Fleet Composition window. If you are using the Fleet Support Programme direct people to Corp Contracts. If you need people to move to different ships don’t be afraid to tell them. If anyone asks or tries to bring a ship which you have not requested and do not need, tell them to reship into something else. Be polite but firm - you are in charge of the fleet. If you need for example 3 more logi, ask people to ‘x up’ to switch from DD to logi and ask the first 3 people to reship. If you have given a list of ship preferences in the ping it should not take too long for people to get in the correct ships in a fleet composition you are happy with.

• Take care of the new players. Bear in mind that in EVE Uni there will normally be at least one person on their first ever fleet, so they will need more support. Consider assigning someone from the fleet as a person for the new players to ask questions to during the fleet so you can concentrate on leading the fleet. It can also be helpful for newer players for instructions to be broadcast, so consider assigning someone - like the 2IC - to broadcast your instructions.

• Remind all fleet members to check their clone to make sure they do not have expensive implants, to make sure their ship is fully fitted (including rigs if they are in the cargo), to insure their ships and to rename them if you desire. You may want to set out briefly the goal of the fleet. There is a checklist of possible discussion points below.

• Undock the fleet as soon as you have everything sorted.

• Once you are undocked, give instructions on safety settings. Briefly explain broadcasting if you have a logi wing - if the fleet has a number of new players consider doing a trial broadcast. If you have several new players consider getting them to anchor on you. If your logi will be cap-chaining have them test this out. In the meantime your scouts can be heading out to the fleet destination to hunt for targets (with one staying to +1 the fleet)

• When the fleet is ready to depart, give the destination, send out your +1 first and then navigate the fleet.

• Be prepared to adapt fleet tactics, strategies, or objectives based on evolving circumstances or unexpected developments.

After the Fleet

• Conduct a short debrief with fleet members. This does not have to be more than a few minutes long. Encourage fleet members to provide feedback on the fleet experience, including successes, challenges, and areas for improvement. Link members to the Ship Replacement Program if necessary.

• Take a moment to reflect, both personally and with any other FC team members who were on the fleet, on the fleet performance. Consider the objectives of the fleet and identify any lessons learned. Remember that we are all constantly learning.

• Submit an after-action report (AAR). Document the fleet operation, including a summary of events, notable engagements, and outcomes. You can make use of the AAR tool and the Battle Report Tool which will make this much easier.

New player speech checklist

With credit to Arkady Martin for this list.

This is intended as the BIG LIST (TM) for possible talking points to include in a newbro speech. Adapt/select as you see fit for your specific fleet and the experience level of the participants.

Many of the items below have in-game UI pointers and/or explanatory gifs/images available that can be helpful to post in fleet chat. These are included in the MOTD of the 'Intro to Fleets' in-game chat channel.

Feel free to assign some of these to your Fleet Instructors (if you have any), as some of the below are things they can help newbros get setup with during the formup.

During Form-Up

• Initial setup
• Whisper key in Mumble
• Fleet members free to reload the MOTD at any point (reload only visible to them, not the entire fleet)
• Ship related
• Clean clone (or purposefully chosen implants, perhaps doctrine-provided)
• Correct ship active
• Rigs fitted
• Ship repaired
• All modules online
• Ammo, drones, nanite paste, scripts, cap boosters
• Ship insurance
• Ship name
• Replacement modules, if any (e.g. specific hardeners, racial jammers, TD/GD balance over the fleet)
• Fleet mechanics
• Home station
• Shared bookmark folder
• Watch list
• Fleet commands
• Anchoring or individual piloting, how to anchor
• Broadcast history
• When to broadcast, how to broadcast
• Keyboard shortcut for broadcast
• Broadcast filtering (especially for logi pilots)
• Destination/waypoints, number of jumps, autopilot settings (shorter, safer, avoidance systems, etc.)
• Invitation to have dotlan open to follow along with fleet location
• How to find fleet using in-game map
• Neutral/negative standings with Edencom and Triglavians
• Special considerations regarding intended engagements (e.g. combat timers, deadspace mechanics and ship restrictions at FW plexes, gate/station guns, security status, bubble mechanics, wormhole polarisation, tethering)
• Reshipping procedure
• No chat in local without permission

On Undock

• Stop ship
• Safety setting
• Orbit / keep-at-range defaults
• Auto-repeat / auto-reload off for certain modules (e.g. ancillary reppers)
• Initial ammo, scripts
• Cap boosters loaded
• Saved Locations window
• Reminder about fleet/wing anchor(s)
• Advance notice to consume combat boosters ahead of first engagement (doctrine-provided or from login rewards)
• Mentally identify modules to have running all the time, also candidates for overheating
• Advanced notice regarding orders for prop mod on/off, drones out/in, ammo switches during battles
• Reminder about colours of jams
• Possibility of split routes
• Standing orders for initial fleet movement