User:Jeffrey raholan/Fleet Communication Guide

Note: This is not offical EVE University policy. This document is only a suggestion by Jeffrey Raholan, lowly Uni student.

Fleet Channels

Each fleet has their own channel on Mumble. There are premade channels named Alpha to 'Juliet in the Ivy League Navy section. Do not go into a fleet operation channel unless you are in the fleet. If you go into fleet op channels without authorization, you will be unregistered and kicked from Mumble.

Inside each fleet channel there will be a command channel. Do not join the command channel in Mumble unless you are in a command position, or otherwise given authorization. This is a private Mumble channel which is only for people in command positions. Joining without authorization will result in being kicked from Mumble.

Communication Policies

Fleet communications are typically ran using one of the following three policies:

Closed Comms

This is the default. If no other order is given, assume Closed Comms. Closed Comms means that commanders and scouts will talk in the command channel and relay orders to the fleet channel whenever necessary. Fleet members are not allowed to speak in Mumble, except in the situations outlined below.

Open Comms

This works like Closed Comms, except that command will usually speak in the fleet channel, for education and entertainment of the fleet members. This does not mean that fleet members are allowed to speak, except in the situation outlined below. Command

Unrestricted Comms

When the Unrestricted Comms policy is in effect, everybody is allowed to speak on Mumble. Nevertheless fleet members must not talk in tight situations or when instructed not to. Also, chat should be kept brief and mostly on-topic to the fleet operations.

Fleet Commanders may change the communication policy during a fleet, for example to have Unrestricted Comms while in high-sec, but switch to Closed Comms once in low-sec or while engaged.

How to Report

Communication Format

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). 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.

The exact place is important to know for many status updates. For example, "There are flashies incoming" is not very helpful, since it is not clear from where they are coming. The place can be left out, if it is not important for the situation at hand or refers to the main fleet's position.

Finally, what to report should be as concise as possible, but as expansive as necessary to describe the situation or command.

Examples

• "Command, Scouty McScout, the Eygfe gate in Aldrat is clear."
• "Fleet, align to Aldrat." (Speaker and place left out, since they are irrelevant.)
• "Command, Fleety McFleet, Eygfe gate in Aldrat, cloaky on grid just cloaked."
• "Command, Fleety McFleet, cloaky on grid just cloaked." (Place left out, meaning it was on grid with the main fleet.)
• "Squad 3, jump, jump, jump." (Speaker and place left out, since they are irrelevant.)
• "Fleet, quick status update, ..." (Place left out, since they are irrelevant, speaker is usually the Fleet Commander.)
• "Point on the Drake." (Recipient, speak, and place left out, since they are irrelevant.')
• "Command, Fleety McFleet, yellow-boxed by the Rifter." (Place left out, since it should usually be obvious.)
• "Gate flash." (Recipient and speaker are irrelevant. Place is the gate the fleet is currently orbiting.)

What to Report

Except in Unrestricted Comms fleets, non-command fleet members should not speak on Mumble, except for the following situations:

• When prompted by command.
• To report points and webs. Include which ship is pointed or webbed.
• Report when you get targeted while not in a fight.
• Normally you should not report flashies or suspicious targets on grid, gate flashes, and other similar things. Use the fleet chat for that, if you think command has missed it.

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

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

Keeping the Fleet Informed

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".