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

The Rookie's Guide to Fleet Ops: Difference between revisions

From EVE University Wiki
Line 70: Line 70:
# '''Final pre-undock checks.''' Your FC might well remember to run through these, but whether or not they do, think "RRAPPIDD": Rigs, Repairs, Ammo, Paste, Pod (clean clone), Insurance, Drones, Drugs.
# '''Final pre-undock checks.''' Your FC might well remember to run through these, but whether or not they do, think "RRAPPIDD": Rigs, Repairs, Ammo, Paste, Pod (clean clone), Insurance, Drones, Drugs.


== Mumble ==
==Discord Voice Comms==


You must be on [[Mumble]] for fleet operations. If you're not on Mumble, you cannot join or follow the fleet. The FC does not have time to type everything out or issue broadcasts. You do not need to have a microphone for some fleet roles, but you must be able to listen.
You must be on [[Discord]] voice comms for fleet operations. If you're not on voice in Discord, you cannot join or follow the fleet. The FC does not have time to type everything out or issue broadcasts. You do not need to have a microphone for some fleet roles, but you must be able to listen.


If you have a mic, make sure your push-to-talk button is set up, and is not any button you would use for anything else.
If you have a mic, make sure your push-to-talk button is set up, and is not any button you would use for anything else.
Disable Mumble sound notifications: In the top menu click “Configure” then “Settings…” and go to “Messages” on the left list. From there you can disable popup and sound notifications about events you don't care about. Sound notifications can be loud and prevent you from hearing the FC, especially with a lot of people in Mumble connecting and disconnecting. The sounds are disabled by unchecking the boxes under the “Soundfile” column.


Once you are in a fleet, move yourself to the appropriate channel in order to hear communications with your fleet. Identify the comms context of your fleet:
Once you are in a fleet, move yourself to the appropriate channel in order to hear communications with your fleet. Identify the comms context of your fleet:
Line 83: Line 81:
* Fleets of any larger size almost always default to combat comms throughout, with line members remaining silent so that the FC, scouts &c can talk. If you're unsure, ask about this in fleet chat. Even in fleets with restricted comms, it is usually fine to talk textually in fleet chat.
* Fleets of any larger size almost always default to combat comms throughout, with line members remaining silent so that the FC, scouts &c can talk. If you're unsure, ask about this in fleet chat. Even in fleets with restricted comms, it is usually fine to talk textually in fleet chat.


Some larger fleets will use a more complex set of subchannels. '''Do not join the command subchannel in Mumble unless you are in a command position, or otherwise given authorization to join.''' This is a private Mumble channel which is only for people in command positions, who need information security and clear comms. Joining without authorization may result in you being asked to leave the channel, or in you being kicked from Mumble.
Some larger fleets will use a more complex set of subchannels. '''Do not join the command subchannel in Discord unless you are in a command position, or otherwise given authorization to join.''' This is a private Discord channel which is only for people in command positions, who need information security and clear comms. Joining without authorization may result in you being asked to leave the channel, or in you being kicked from Discord.


== Joining a fleet ==
== Joining a fleet ==