So as an example, a Mumble link on a lobby (77685) I just joined as Blue Medic
Following the conventions here: http://mumble.source....net/Mumble_URL this would do the following:
- This is a Mumble URL.
%5BTASF%5DOverkill - This is the username to use. The encoding is fine and mumble will understand it as [TASF]Overkill.
mumble.tf2center.com - Connect to this server.
%2377685 - This is in the place where Mumble expects a channel. %23 is #, so this will get expanded to "#77685".
version=1.2.0 - Tells my client the server version. Just in case.
I am running Linux so if this happens automatically when the game starts or something, I apologize... I am going off of the "Join Mumble" link in the lobby:
1. Update my name in the Mumble link as I switch class slots. If I join the Medic slot, make my name "MED: [TASF]Overkill" in the URL.
2. Update the channel in the Mumble link as I switch teams. If I join the Blue team, instead of just "#77685" as the channel, specify "#77685/BLUE".
3. Include ServerName and ServerURL variables so that users can drag-drop to their Mumble client and easily add as a favorite.
So, ideally, if I join a lobby as a BLU medic, my "Join Mumble" button should take me to:
MED%3A%20%5BTASF%[email protected]/%2377685/BLUE?version=1.2.0&ServerName=TF2Center%20Mumble%20Server&ServerURL=http%3A%2F%2Ftf2center.com
Or urldecoded:
MED: [TASF][email protected]/#77685/BLUE?version=1.2.0&ServerName=TF2Center Mumble Server&ServerURL=http://tf2center.com
For bonus points you could automatically control the Mumble server with ICE based on what users do in the lobby. But the URL scheme is a lot easier.