Mumble is the voice communications used by the Imperium and is internally hosted. It replaced Teamspeak 2 because it has better voice quality and doesn't have the "phone home" licensing issues of Teamspeak 3.
Mumble is hosted internally and is generally considered safe to use when connected to either of our servers. Connecting to external servers has a very low risk of damaging OPSEC, unless for some reason you've got an alt in a hostile alliance and are keying up in their comms and our comms at the same time...spy.
If you are on an op channel or a standing fleet channel on the GSF Mumble server there are [Mumble Rules] that apply.
Connecting: The First Time
How to connect?
Just download it from the MUMBLE and install it like a normal program. After you start Mumble the first time, a built in Audio Wizard will pop up. This will guide you to prevent sounding like a windstorm. At the end close the Favorite window and proceed to the next step.
Settings: Before you connect the first time
Before you connect the first time to any kind of server, there are some quality of life improvements you can do to prevent some nasty notification- and sounds spamming's. Just follow this :
“Configure” > “Settings” > ...
“User interface” Under “Look and Feel” you an change to a dark theme Under “Channel Tree” change the “Expand” to “None” you will see later why this is important Hit “Apply”
“Messages” Uncheck everything you don't want to get a Notification, Console Popups or Sound Alerts. You won’t miss anything if you just uncheck all checkboxes but sadly you need to uncheck all of them individually*
- development snapshot can use the row “All messages”
“Overlay” (if you want to have a overlay) For Win10 it works “out of the box” so if you want to know who is talking on comms just activate it and drag the red dot where you want to show the name. By default the overlay show you everyone in your channel, to change this just right click the overlay window and change the filter like you want Hit “Apply”.
Overlay does not work with DX12 active on the EVE Client. You will need to select "Configure" > "Talking UI".
Adding the GSF server Just add the server over “Server” > “Connect” > “Add New”
Label : Label the server like you want
Address : mumble.goonfleet.com
Port : 64738
Username : Your username (See here “GSF Mumble” > “Username”) don't miss the corp-ticker
Hit “OK” and there will be a new favorite shown and you can see the user count on it
Now you try to connect to the server and get some new Popups. The first one will be a certification window. Just accept the certificate and you are asked for your password. The password is your ESA password and not the one for the forum. You can change it here, but keep in mind a change will affect some other services too.
Well done, you are now ready to join fleet comms and shoot poor souls with your fellow bees.
How to connect to multiple channel at the same time
There will be some situations you want to be in more than one channel at the same time and listen to instructions or to someone. The best example is the usage of the Mainfleet (Subcaps) and with your alt in a big ship (Caps). Both of them have different comms in general and you need to listen to them at the same time.
The stable version doesn’t have a built in feature for this, so check out this forum post how to setup multiple mumble clients: Setup
The development version has a build in feature called “Listen to channel”. You only need to right click the channel you want to listen to and use the context entry “Listen to channel” now you are able to hear this channel too. Keep in mind you can just hear and don't talk with this function.
So you are connected and are completely lost? Don’t worry here are some helpful explanations for you.
First of all minimize every channel by clicking the small triangle at the left of every category (now you see why we set “Expand” to “None” because they will stay minimized)
From top to down you will find the most important categories and channels you will use frequently as a normal bee.
Fireside (weekly usage for Fireside Chat) Ops > Op Channels > OP1 - OP11 and more - these are your Op channels you will join based on the fleet ping you got from your PING (Pidgin, …) Keep in mind there is a “No chatter” for every Op Channel so you can NETFLIX and don't get nasty voices of sperging fleetmates while in a fleet. You will hear only FC and important pilots you don't want to mute. If the FC is sperging, good luck... Corporation Channels (if your corporation use mumble for daily business you will find them here) Social Channels (channels for all social groups in GSF)
Command Channels These instructions were borrowed from Gents' mumble instructions because IDKWFT. First add some commands to deal with local and global communications. You'll want to set the Function to "Whisper/Shout" instead of "Push-to-Talk". Data should appear as an "Empty" textbox with a button that says "...", click that button. Depending on whether you are setting a "Local Key" or "Global Key" you want to do one of two of the following: For "Local Key", you want it to whisper to only your CURRENT channel, as in the following screenshot.
For "Global Key", you want it to whisper to your PARENT channel and ALL SUB CHANNELS.
Set the shortcut key as you like, and the Suppress function if you think you need it. So basically, how this works is, In the Fleet superchannel: Each Command Channel is linked to the appropriate Fleet Channel as well as its EW/Logi sub channels. Using LOCAL (whisper to current) ignores sub channels and linked channels, and whispers to only to the current channel. Useful for Commanders to talk with each other without the rest of the fleet listening in, and the same goes for EW/Logi/Translation. Using GLOBAL (whisper to parent + subs) in a Fleet# channel will whisper to ALL channels in the Fleet superchannel. Useful for cross-fleet and cross-fleet-command chatter when multiple fleets are running. Using GLOBAL (whisper to parent + subs) in a Command# channel will whisper to ALL Command# channels. Useful for cross-fleet-command chatter when multiple fleets are running. Remember, when you are using a whisper command, Prefix and Suffix what you say with "Global" or "Local" so that everyone knows you are doing a whisper.
How to create a desktop shortcut that connects you directly to a channel in mumble. To avoid fumbling around in channels because you are bad and Asher Elias ragepinged his Cormfleet to shoot the next Ansiblex, these few simple steps can help you to join comms way faster. If you are already logged in to mumble in some other channel this shortcut will simply move you to the right channel. If you do not have mumble running this shortcut will start mumble and connect you to the right server and channel all in one go without any additional action required from you.
1. Open mumble and connect to Goonfleet
2. Right click on the desired channel (the screenshots in this guide will be using Theta - Eve related)
3. Select COPY URL
4. Go to your desktop or wherever you want this shortcut to be
5. Right click and go NEW -> Shortcut
6. Paste the URL you copied in step 3
7. Click Next
8. Name your shortcut something other than gay4jay (Something useful like Theta - Eve related) Remember to click Finish after naming it!
And you are done! You now have a shiny new icon wherever you wanted this to be in the earlier steps. As with most other files on your computer you can move and rename them later at will.
Broken Mumble Hyperinks
Are mumble hyperlinks sent in pings no longer working for you? Hopefully this is the fix for you!
Follow this guide posted on the goonfleet forums here.