MantisBT

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000478SoldatGameplaypublic2013-12-14 20:102014-10-06 03:55
ReporterSzaman 
Assigned ToExHunter 
PriorityimmediateSeveritymajorReproducibilityN/A
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version1.6.6 
Target VersionFixed in Version 
Summary0000478: Vote-kick causing the permanent ban
DescriptionAccording to this post: http://forums.soldat.pl/index.php?topic=43172.msg516845#msg516845 [^]
There is possibility of permbanning player by vote-kick if you type some random (?) characters as the reason.
Additional InformationRead the topic: http://forums.soldat.pl/index.php?topic=43172.msg516845#msg516845 [^]
TagsNo tags attached.
Attached Files

- Relationships
has duplicate 0000554resolvedExHunter Player votekicks turn into permanent server bans 

-  Notes
(0002089)
SpiltCoffee (reporter)
2013-12-15 15:27
edited on: 2013-12-15 15:27

Appears to be caused by vote kicks launched by the server against players it believes to be cheating.

The code currently does not handle server initiated vote kicks in a manner consistent with how it handles player initiated vote kicks.
This results in the first player to press F12 on a server initiated vote kick to appear as the (incorrect) entity to have launched it.
This also results in the weird characters appearing in the reason for the vote kick, as the player's client would not have provided a reason back to the server, and so (I think) the server prints garbage data, not knowing what else to do.

Possible solution would be to ensure server initiated vote kicks setup all related variables correctly.

(0002091)
Szaman (reporter)
2013-12-16 00:30

But this player (Magnum from the mentioned above forum thread) has just joined the game. And he is not "hacker". Maybe there was some network problems (lags, packet flood, etc.) that made server think that he is hacking. But... I still don't understand that mechanism - if it was the server who initiated the kick, then why there was a nick of currently playing player as the "source" of the kick? I mean this fragment:
13-12-13 11:03:24 .:Ma9NuM:. joining game (84.205.190.134:64900) HWID:2D635128F0C
13-12-13 11:03:28 kOSMICZNY KUTAS started votekick against .:Ma9NuM:. - Reason:R^C <FC>^X
13-12-13 11:03:29 .:Ma9NuM:. has been kicked and permanently banned (Vote Kicked by Server)

I've also found that this reason is the same as "R ΓΌ" (but the viewer has displayed it differently).
(0002092)
SpiltCoffee (reporter)
2013-12-16 01:47

"if it was the server who initiated the kick, then why there was a nick of currently playing player as the "source" of the kick?"

That is the inconsistency I was referring to. The server does not correctly initialise everything to do with vote kicking when it decides to launch a vote kick at a player. The random characters in the reason provided is not actually the bug itself.
(0002289)
ExHunter (developer)
2014-09-06 23:49

Please check if it will be fixed in the upcoming 1.6.8 beta.

And if other bugs related to voting occurs.

- Issue History
Date Modified Username Field Change
2013-12-14 20:10 Szaman New Issue
2013-12-15 01:26 Bistoufly Priority high => immediate
2013-12-15 01:26 Bistoufly Status new => acknowledged
2013-12-15 15:27 SpiltCoffee Note Added: 0002089
2013-12-15 15:27 SpiltCoffee Note Edited: 0002089 View Revisions
2013-12-16 00:30 Szaman Note Added: 0002091
2013-12-16 01:47 SpiltCoffee Note Added: 0002092
2013-12-19 13:11 SpiltCoffee Assigned To => SpiltCoffee
2013-12-19 13:11 SpiltCoffee Status acknowledged => assigned
2014-04-02 17:38 homerofgods Status assigned => confirmed
2014-04-04 00:21 Shoozza Assigned To SpiltCoffee =>
2014-08-18 14:29 ExHunter Relationship added has duplicate 0000554
2014-09-06 23:49 ExHunter Note Added: 0002289
2014-09-06 23:49 ExHunter Assigned To => ExHunter
2014-09-06 23:49 ExHunter Status confirmed => feedback
2014-10-06 03:55 ExHunter Status feedback => resolved
2014-10-06 03:55 ExHunter Resolution open => fixed


Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker