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
Remove {{Update}}. Fix typo.
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
{{Update|[[#Mumble]] disable sound notifications need some attention.}}
{{eunispecific}}
{{eunispecific}}
{{related class|Fleets (CORE class)}}
{{related class|Fleets (CORE class)}}
Line 17: Line 16:


=== Command ===
=== Command ===
* FC: Fleet Commander
* FC: Fleet Commander
* WC: Wing Commander
* WC: Wing Commander
Line 23: Line 21:


=== Movement ===
=== Movement ===
* HOC: Hold On Contact
* HOC: Hold On Contact
* JJJ: Jump Jump Jump
* JJJ: Jump Jump Jump
Line 32: Line 29:


=== Identifiers ===
=== Identifiers ===
* POS: Player Owned Structure
* POS: Player Owned Structure
* WT: War Targets
* WT: War Targets
Line 41: Line 37:


=== Mechanics ===
=== Mechanics ===
* PVP: Player vs Player
* PVP: Player vs Player
* PVE: Player vs Environment
* PVE: Player vs Environment
Line 53: Line 48:


== Pre-fleet checklists ==
== Pre-fleet checklists ==
Players who are very new to the game can and should do the following UI preparations before a fleet forms:
Players who are very new to the game can and should do the following UI preparations before a fleet forms:


Line 70: Line 64:
# '''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.


==Discord Voice Comms==
==Voice Comms==
 
You must be on [[Discord]] voice comms for fleet operations. The FC does not have time to type everything out in chat so we use voice comms for that. You do not need to have a microphone for some fleet roles, but you must be able to listen. Almost all of out fleet comms are in English. Once you are in a fleet, make sure you are in the correct Discord voice comms channel for the fleet.
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.


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:
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 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.
* In small gangs (up to 15 pilots give or take) voice chat is often relatively open, and we enter "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 relatively silent so that the FC, scouts etc can pass vital information. If you're unsure, ask about this in fleet text chat channel. Even in fleets with restricted comms, it is usually fine to talk textually in fleet chat, and we do try to relax comms where we can


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


=== Operational security ===
=== Operational security ===
{{main|Operational Security Policy}}
{{main|Operational Security Policy}}