1 reply to this topic

[<da> Shadow]

TF2C Profile: Shadow
Region: NA

Browser: Mozilla Firefox
Critical plugins: --
OS: Windows
Connection type: * WiFi

Bug type: Mumble
Lobby ID: 484990
Date & Time: august 3rd 7:45 ish est

http://prntscr.com/80j7hn
There's a screeny of my ban
http://prntscr.com/80j7v5
there's a screeny of me sitting in the mumble still, I haven't left it.

Thanks, I'm matt and i'm here to tell you that your mumbility system broke resulting in a third time of my self being banned something along the lines happened the second time when it refused to let me connect to the tf2c mumble at all and both of these being bugs not only with your system and with mumble have left me rather frusterated, I was in the mumble from start to finish as a matter of fact that was the worst lobby i've played in ages no one was really comming they just said the med died a few times (our medic) and they never called their sniper, they couldn't break a gun and demanded I frag the engineer etc.

So for the sake of the future please fix the issue with it not registering people in the mumble so they don't get banned its very annoying to sit here and watch the system act so irrationally and flawed.

Thanks.

[ninjaMooCow]

As far as I know, the mumbility system works correctly.  Usually these things get tracked down to a user behavior, so I will spell out the "cheat sheet."

 

Tips to avoid auto mumble bans:
1. Make sure your mumble client version is up to date.
2. get in before the start.  Get out after the end.
3. Don't leave mumble and come back (e.g. restart).
4. stay in mumble until after the end.  The end is when TF2C says it is the end.
5. Use the same computer for mumble as tf2.   The IP addresses must match.
6. Do not mute or deafen.  at all.