In Mumble, each fleet channel is linked to a Command Channel. What this means is when you use your push-to-talk key in the Command 7 channel, everyone in the Fleet 7 channel will hear what you are saying. Likewise, if you are in the Command 7 channel, you will hear anyone in the Fleet 7 channel who talks with their push-to-talk key.

To speak privately between FCs and scouts inside your command channel or to all command channels, you must create whisper keys.

• Go to the Configure menu at the top of Mumble and click on Settings.
• Go down to Shortcuts and click on it. Click the Add button. (You will see a new selection come up labeled Unassigned).
• Click on Unassigned and then go down the options until you find Whisper/Shout and select that. Once you do that you will see under Data a new selection labeled Empty.
• Click on Empty and then you will see a button with “…” in it, click on that and a new window will come up.

Local whisper will enable you to whisper to the current command channel you are in.

• Follow the steps in the first section to create a new Whisper/Shout key.
• Click on the Shout to Channel. In the item list you will see Root > Parent > Current.
  • Select Current.
• Once you have done that click OK.

Global whisper will enable you to whisper to the everyone in all of the command channels.

• Follow the steps in the first section to create a new Whisper/Shout key.
• Click on the Shout to Channel. In the item list you will see Root > Parent > Current.
  • Select Parent.
  • Check shout to subchannels.
• Once you have done that click OK.

For the bootcampers, what is command channel?< Command channel is a sub restricted channel that is linked to your fleets channel; AKA, it works the same as any sub channels in your fleet channel. Keep reading, this comparison is important.

If you want place where you can discuss opsec stuff with your fleet on a local whisper. Join any of the subs channels in your fleet (preferably one that is empty eh) and just keep watch of who comes in and who goes out. You can also enable entrance sounds and etc.. etc.. I used this for my anchors and it's damn effective. Most of your fleet will respect not shitting on the comms. You can also put anyone who gets in that channel on the spy list if needed vOv

It's a cheap and effective way to get who you need in a private room for communication while still be able to command your fleet. It also puts less work load on those that would normally drag you around…

That said, if the need is supersecret opsec stuff you can allways ask for a drag to commands channels where well they wont be able to suprise enter your channel.

This is just how 95% of fleets function, based on observation throughout the years. This is common to Teamspeak and Ventrillo setups.

• Can be done on any comms

This is where everyone in the fleet jumps into the one channel and the FC runs the fleet from the channel. Its really chaotic and inefficient but doesn't take much to get setup. Small fleets can work using this. OPSEC is seen to be not of concern here.

• Can be done on TS, Mumble
• Hard to setup on Ventrillo

If you have quite a few Logi or EWAR, it might be wise to put them into different sub channels. Allows for coordination and opens up opportunities for sub-FCs to take control of the sub channel. Priority speaker is normally given out to the sub FCs.

• Cannot be setup on Ventrillo
• Easy to setup on Mumble

This is the common multi-fleet communication setup and can use either dogpile or sorted setups. OPSEC is conserved to the command channels of the fleet channels

• Hard if not impossible on TS3
• Impossible on Ventrillo
• Easy to setup on Mumble

This is a new form of mumble setup and it involves a setup time if it isn't used too much. OPSEC is largely conserved. The setup involves using sub FCs taking control a part of the fleet like groups of tackle and moves them around as forward scouts and tackle things. Great for roams and looking for targets whilst the motherfleet is at a more centralised point. GMT +10 Squad and Sajuukthanatoskhar uses this.