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

User:Jeffrey raholan/Fleet Communication Guide: Difference between revisions

From EVE University Wiki
No edit summary
No edit summary
Line 56: Line 56:
=== Check, Check, Check ===
=== Check, Check, Check ===


...
When the call "Check, Check, Check" is made on Mumble, everyone must stop talking. "Check, Check, Check" is used whenever important information or commands are to be relayed. Therefore, comms must be cleared immediatly.
 


=== Standings and Security Status ===
=== Standings and Security Status ===


-5 sec vs. -5 standing
There is often confusion between targets with a negative standing towards the University and targets with a negative security rating. Therefore it is important to clearly communicate the status of a target. Use "negative" and "positive" to refer to the security status and "minus" and "plus" to refer to the standing. Alternatively use words like "flashy", "minus five to the Uni", or "bad standing".


== Command Responsibilities ==
== Command Responsibilities ==


* FCs: keep the fleet informed
=== Keeping the Fleet Informed ===
* report friendly flashes
 
* what to do when fleet is split
The Fleet, Wing, and Squad Commanders should make sure to keep the fleet informed, when using Closed Comms. Talk to the fleet every few minutes if nothing apparent is happening. Also, tell the fleet in broad strokes what to expect and what is going on, as much as opsec allows. Nothing is more frustrating for fleet members than OGCing a gate for a quarter of an hour and not knowing what is going on.
 
Also, command should acknowledge the following to the fleet:
 
* friendly gate flashed, so the fleet knows not to worry
* unknown gate flashed, so the fleet know to keep on their toes
* flashies on grid and what to do about them
* other important things on grid, like obvious spies
 
This information is crucial so that the fleet know what to expect, and especially what to report and what not to report. Only by acknowledging these things, the fleet can know that those things are being observed by command and don't need to be brought to their attention.
 
=== How to Handle Split Fleets ===
 
When the fleet is split, command must make sure that everyone knows what to do and that it is clear to whom commands are given. Therefore, command must include clear squad designations when giving commands, and make sure that "fleet" only means the main fleet. "My squad" and unspecific commands (for example, just "Jump Jump Jump") should be avoided.
 
Also, it can help to qualify commands like "Jump, Jump, Jump" to include the destination. For example, "Squad 2, Jump Jump Jump into Aldrat".