You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 17, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 17, 2022. It is now read-only.
Trusted Players get auto-kicked from pre-game menu in Multiplayer #2329
keyword_syncresolution_fixedtype_bug | by j0shdrunk0nwar
Many players are getting auto-kicked from the pre-game menu of hosted games. The host gets a error message that the player was auto-kicked. This has been happening too often even with trusted players.
Issue migrated from trac:2329 at 2022-04-16 06:47:46 -0700
What's particularly troubling is that auto-kick message in the console says it's due to cheating, though the person being kicked doesn't know this, because the only message they see is "You have been kicked".
This is a partial log file from a game I hosted today
Player 5 score was updated: kills=0 score=0 : 0 (Sync) Tue Nov 16 14:52:18 2010
!!>Msg: 54 was detected from a non-host player 5 (Terminator[UA]), IP:193.23.140.187 : 5 (Sync) Tue Nov 16 14:52:18 2010
Player was kicked. : 5 (Sync) Tue Nov 16 14:52:18 2010
Player (5) has left, closing socket 041914B0 : 5 (Sync) Tue Nov 16 14:52:18 2010
** Player 5 [Terminator[UA]], has left the game. : 5 (Sync) Tue Nov 16 14:52:18 2010
Freeing slot for a new player. : 5 (Sync) Tue Nov 16 14:52:18 2010
I have also seen this, when me and a friend tried to play a local LAN game with beta3. Both computers were Win7 64bit. There kick message leaves a lot to be desired, as it gives no info about what could possibly be wrong.
(In Warzone2100/warzone2100@fd2843e) Fix bug introduced in 09ea0be7c30236809536db332be78b2967d3114d
Changelog: Fix kicking of non-hosts who didn't have default color values.
Only change colors if you are the host on the setup screen.
Fixes #2329
#CommitTicketReference repository="" revision="fd2843e6431e43cc72b635c422fd18bb19d42c47"
Fix bug introduced in 09ea0be7c30236809536db332be78b2967d3114d
Changelog: Fix kicking of non-hosts who didn't have default color values.
Only change colors if you are the host on the setup screen.
Fixes #2329
What, you guys play with something other than the defaults? How dare you! ;)
Unsure if this ticket will be spammed or not, but this is fixed in
[4]fdba622e676fb40ea41f0c4a67597ce3ce711cd
I wonder if b3 is remember color changes from previous games? I rarely feel the need to set my flag to a certain color, though I had noticed in skirmish games subsequent to bogus kicks my color was red in game. I think that would explain why deleting the entire data directory + reinstall allowed me join a few games.
Activity
wzdev-ci commentedon Nov 16, 2010
effigy commented
What's particularly troubling is that auto-kick message in the console says it's due to cheating, though the person being kicked doesn't know this, because the only message they see is "You have been kicked".
This is a partial log file from a game I hosted today
wzdev-ci commentedon Nov 17, 2010
effigy uploaded file
netplay-1016_142620.log(53.2 KiB)complete log from log sample I mentioned above
wzdev-ci commentedon Nov 19, 2010
Per changed status from
newtoassignedwzdev-ci commentedon Nov 19, 2010
Per changed component from
othertoEngine: Networkingwzdev-ci commentedon Nov 19, 2010
Per changed priority from
majortoblockerwzdev-ci commentedon Nov 19, 2010
Per changed owner from `` to
Buginatorwzdev-ci commentedon Nov 19, 2010
Per changed milestone from
unspecifiedto3.0wzdev-ci commentedon Nov 19, 2010
Per changed keywords from `` to
syncwzdev-ci commentedon Nov 19, 2010
Per commented
I have also seen this, when me and a friend tried to play a local LAN game with beta3. Both computers were Win7 64bit. There kick message leaves a lot to be desired, as it gives no info about what could possibly be wrong.
wzdev-ci commentedon Nov 19, 2010
effigy commented
My experience with this has been on WinXP sp3, when playing online.
wzdev-ci commentedon Nov 19, 2010
buginator <buginator@...> commented
(In Warzone2100/warzone2100@fd2843e) Fix bug introduced in 09ea0be7c30236809536db332be78b2967d3114d
Changelog: Fix kicking of non-hosts who didn't have default color values.
Only change colors if you are the host on the setup screen.
Fixes #2329
wzdev-ci commentedon Nov 19, 2010
Buginator changed status from
assignedtoclosedwzdev-ci commentedon Nov 19, 2010
Buginator changed resolution from `` to
fixedwzdev-ci commentedon Nov 19, 2010
Buginator commented
What, you guys play with something other than the defaults? How dare you! ;)
Unsure if this ticket will be spammed or not, but this is fixed in
[4]fdba622e676fb40ea41f0c4a67597ce3ce711cd
wzdev-ci commentedon Nov 19, 2010
buginator <buginator@...> commented
In Warzone2100/warzone2100@fd2843e:
wzdev-ci commentedon Nov 20, 2010
effigy commented
Replying to Warzone2100/old-trac-import#2329 (comment:4):
I wonder if b3 is remember color changes from previous games? I rarely feel the need to set my flag to a certain color, though I had noticed in skirmish games subsequent to bogus kicks my color was red in game. I think that would explain why deleting the entire data directory + reinstall allowed me join a few games.
wzdev-ci commentedon Dec 6, 2010
buginator commented
Fix bug introduced in 09ea0be7c30236809536db332be78b2967d3114d Changelog: Fix kicking of non-hosts who didn't have default color values.
Only change colors if you are the host on the setup screen.
Fixes #2329
(cherry picked from commit fd2843e6431e43cc72b635c422fd18bb19d42c47)
Conflicts:
Changeset: 00c92cbdd7ca1bf9fbd1fc803cc811aef88aa0bc
wzdev-ci commentedon Dec 16, 2010
buginator commented
Fix bug introduced in 09ea0be7c30236809536db332be78b2967d3114d Changelog: Fix kicking of non-hosts who didn't have default color values.
Only change colors if you are the host on the setup screen.
Fixes #2329
(cherry picked from commit fd2843e6431e43cc72b635c422fd18bb19d42c47)
Conflicts:
Changeset: 00c92cbdd7ca1bf9fbd1fc803cc811aef88aa0bc
wzdev-ci commentedon Jan 3, 2012
cybersphinx changed milestone from
3.0tounspecifiedwzdev-ci commentedon Jan 3, 2012
cybersphinx commented
Milestone 3.0 deleted