Muzzled.

[HiredGun]

There were a couple of players that reported being "muzzled" on OC32 Instagib today. What I heard was that they were kicked from the server, and when they reconnected they were STFU'd. But it doesn't end there -- they would automatically be STFU'd, without a vote being called, at the start of the next round. We had to keep calling UNSTFUs on them to allow them to speak or call votes. It almosts seems like whatever parameter/variable was set on their UID by the server to STFU them, wasn't being properly reset on the server by the callvote to UNSTFU. My two cents.

Anybody ever see this before?

[KyleRTCW]

One time i was STFU'ed and it STFUed me every new round not funny

[gotenks]

it's a banibug hes allready working on it

[=FF=im2good4u]

once i was STFU up when i reconnected to the server it was gone and i never had any trouble whit after that

[-[x]-Texan]

The only times I've ever been STFU'd is when I voted it myself, or I told someone to call the vote..O.o

[duke'ku]

The bug with the sticking STFU after a vote was called is fixed. You will be muzzled until someone calls a vote to unstfu that passes.

[gotenks]

i placed a rcon quiet on qcryan... and it happens there too... not just with voting stfu's

[duke'ku]

he hasn't released the fixed version yet.

[gotenks]

but what i was saying was that it wasn't with just the "voting stfu" sticking any stfu or quiet command can stick

[duke'ku]

that's the problem. the vote does the exact same command. when someone does /callvote stfu 13, if it passes, the server does the command stfu 13. when someone does /callvote map mp_beach, the server does set nextmap mp_beach;vstr nextmap.