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
Uryence (talk | contribs)
During the Op: Updated to reflect current procedures. Text no longer assumes a male FC.
Uryence (talk | contribs)
Mumble: A note on speaking in the third person.
Line 75: Line 75:
Disable Mumble sound notifications: In the Setting screen ''Configure Settings'' you can find ''Advanced settings'' check-box in the bottom left corner. With it checked you can access the Messages settings. 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.
Disable Mumble sound notifications: In the Setting screen ''Configure Settings'' you can find ''Advanced settings'' check-box in the bottom left corner. With it checked you can access the Messages settings. 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.


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. In small gangs—roughly, less than 15 pilots—voice chat is often relatively open, entering a "combat comms" state restricted to vital information only during combat itself. 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.
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:
 
* In small gangs—roughly, less than 15 pilots—voice chat is often relatively open, entering a "combat comms" state restricted to vital information only during combat itself. During combat comms, try to speak in the third person, and be precise: "I am being attacked" tells the gang almost nothing, but "An [[Atron]] has tackled Uryence at the Juliet Hotel gate in [[NSC|Papa Charlie Nine]], grid otherwise clear so far" tells the gang quite a lot. You don't have to be this collected if you're new, but it's something to aim for!
* 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 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.