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

← Older edit

VisualWikitext

@@ Line 1: / Line 1: @@
-<div style="border: solid 0.5em orange; padding: 0.5em">Note: This is not offical EVE University policy. This document is only a suggestion by [[User:Jeffrey raholan|Jeffrey Raholan]], lowly Uni student.</div>
+<div style="border: solid 0.5em orange; padding: 0.5em; margin-bottom: 2em">Note: This is not offical EVE University policy. This document is only a suggestion by [[User:Jeffrey raholan|Jeffrey Raholan]], lowly Uni student.</div>
 == Fleet Channels ==
@@ Line 21: / Line 21: @@
 === Communication Format ===
-Communication should be clear and concise. In the Uni, the following format should be used when speaking on Mumble:
+Communication should be clear and concise. Prefer conciseness over politeness. In the Uni, the following format should be used when speaking on Mumble:
 :''Recipient, Speaker, Place, What to report''
-The recipient is usually something like ''fleet'', ''command'', or ''squad 3''. When the recipient is ''fleet'', this only refers to members of the main fleet, not any scouts, squads, or members that are not with the main fleet at the moment (like bait squads). The recipient can be left out, when answering a question or giving a quick status update, like "point on XYZ" or "gate flash". If the speaker is stated, the recipient must always be stated as well.
+The recipient is usually something like ''fleet'', ''command'', or ''squad 3''. When the recipient is ''fleet'', this only refers to members of the main fleet, not any scouts, squads, or members that are not with the main fleet at the moment (like bait squads). ''Command'' refers to the people in the command channel, i.e. the Fleet, Wing, and Squad Commanders as well as the scouts. The recipient can be left out, when answering a question or giving a quick status update, like "point on XYZ" or "gate flash". If the speaker is stated, the recipient must always be stated as well.
 It is important to identify who is speaking. The Mumble overlay is unreliable as a tool to identify the speaker. If you use the words "my" or "I", you probably have done something wrong. The speaker can be left out, if it is clear, who the speaker is, or it is irrelevant for the situation at hand. For example, if commands are given, it is seldom necessary for the recipients to know who exactly is giving the command. Also, the voices of frequent speakers, such as the Fleet Commander, or the scouts in the command chat, should be familiar to the listeners.
@@ Line 56: / Line 56: @@
 === 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 ===
--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 ==
-* 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".