Yesdowoshek wrote:Another annoying callvote bugs are:
1. You can't vote (from menu) for kicking a player with empty spaces or combinations of "^^" in his name. It can be done in console, but it's not always practicable.
2. Player can change his name during voting and he won't be kicked even if the vote will pass.
Is it already fixed in 1.1?
Pardner wrote:Players are able to call custom messaged through the callvote system. I posted this here because I noticed this on a 1.0 server. It may be fixed in 1.1
/dev/random wrote:Iirc you can use 'clientkick #id', which avoids the renaming problem. But since /stats is disabled, I don't know how to obtain a client id clientside.
Tequila wrote:Yesdowoshek wrote:Another annoying callvote bugs are:
1. You can't vote (from menu) for kicking a player with empty spaces or combinations of "^^" in his name. It can be done in console, but it's not always practicable.
2. Player can change his name during voting and he won't be kicked even if the vote will pass.
Is it already fixed in 1.1?
/serverstatus
And don't worry, this has been addressed in 1.1. "kick" callvote is really now secured.
moRtem wrote:It's "fixed", but not really (afaik).
Most lamers simply rename as soon as the vote passes (or as soon as someone calls a vote to kick them).
A good solution would be, to have the menu initiating a /callvote clientkick PLAYER_ID
moRtem wrote:/serverstatus
NOT -- see the part i wrote above. (or /serverstatus got fixed in 1.1b3 already?)
Players:
num: score: ping: name:
0 3 0 "ManWithNoName"
1 3 0 "Unknown"
2 3 0 "Tuco"
3 1 0 "TheMexican"
4 0 50 "=SG=Pardner"
moRtem wrote:It's "fixed", but not really (afaik).
Most lamers simply rename as soon as the vote passes (or as soon as someone calls a vote to kick them).
moRtem wrote:A good solution would be, to have the menu initiating a /callvote clientkick PLAYER_ID
And next important thing would be to display the correct IDs /serverstatus (which are seen in /rcon status), since the displayed IDs in /serverstatus won't work with /callvote clientkick./serverstatus
NOT -- see the part i wrote above. (or /serverstatus got fixed in 1.1b3 already?)
map: dm_alamo_tiny
num score ping name lastmsg address qport rate
--- ----- ---- --------------- ------- --------------------- ----- -----
0 1 0 Tuco^7 11900 bot 0 16384
1 0 0 Tuco *^7 11900 bot 0 16384
2 0 0 Tuco **^7 2300 bot 0 16384
3 0 0 Tuco ***^7 11950 bot 0 16384
5 0 0 Me^7 0 127.0.0.1 15514 99999
6 1 0 Tuco *****^7 11950 bot 0 16384
Players:
num: score: ping: name:
0 1 0 "Tuco"
1 0 0 "Tuco *"
2 0 0 "Tuco **"
3 0 0 "Tuco ***"
4 0 0 "Me"
5 1 0 "Tuco *****"
"version" is:"1.1b4_SVN481M 20100109 linux-i386^7"
moRtem wrote:Hmm - Tequila.
I somehow got the feeling your "final" solution of fixing that problem is a bit dirty.
I don't want to say it's bad, but it feels pretty complicated and therefor might cause sideeffects which need to be addressed and fixed aswell.
E.g. nicks containing ^-signs ain't displayed correctly. (neither in callvote menu, nor in the initiated poll) -- it's still possible to kick them, but sometimes it's hard to find the correct player in menu, especially when more players are having those signs in their nickname.
In any other Q3-mod i played so far, a command like /serverstatus worked (in many other mods it is called /players). The most Mods didn't offer a "callvote"-section in menu too. And "callvote kick" would accept those IDs.
In my opinion the most elegant way to get a consistent callvote-kick-system would be to display the real IDs of the players in scoreboard. And link the callvote-kick in menu with the real IDs to initiate clientkick-votes.
Having a (working) command like /serverstatus would be a good solution too.
/quit
/kick #id
/callvote please kick if you can mr/ms bad_player with client_numberN