Skip to content
This repository was archived by the owner on Apr 17, 2022. It is now read-only.
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

Closed

Description

@wzdev-ci

keyword_sync resolution_fixed type_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

Activity

  1. wzdev-ci commented on Nov 16, 2010

    @wzdev-ci
    ContributorAuthor

    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

    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
    
    
  2. wzdev-ci commented on Nov 17, 2010

    @wzdev-ci
    ContributorAuthor

    effigy uploaded file netplay-1016_142620.log (53.2 KiB)

    complete log from log sample I mentioned above

  3. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    Per changed status from new to assigned

  4. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    Per changed component from other to Engine: Networking

  5. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    Per changed priority from major to blocker

  6. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    Per changed owner from `` to Buginator

  7. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    Per changed milestone from unspecified to 3.0

  8. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    Per changed keywords from `` to sync

  9. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    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.

  10. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    effigy commented


    My experience with this has been on WinXP sp3, when playing online.

  11. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    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

  12. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    Buginator changed status from assigned to closed

  13. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    Buginator changed resolution from `` to fixed

  14. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    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

  15. wzdev-ci commented on Nov 19, 2010

    @wzdev-ci
    ContributorAuthor

    buginator <buginator@...> commented


    In Warzone2100/warzone2100@fd2843e:

    #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
    
  16. wzdev-ci commented on Nov 20, 2010

    @wzdev-ci
    ContributorAuthor

    effigy commented


    Replying to Warzone2100/old-trac-import#2329 (comment:4):

    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.

  17. wzdev-ci commented on Dec 6, 2010

    @wzdev-ci
    ContributorAuthor

    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:

    lib/netplay/netplay.c 
    

    Changeset: 00c92cbdd7ca1bf9fbd1fc803cc811aef88aa0bc

  18. wzdev-ci commented on Dec 16, 2010

    @wzdev-ci
    ContributorAuthor

    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:

    lib/netplay/netplay.c 
    

    Changeset: 00c92cbdd7ca1bf9fbd1fc803cc811aef88aa0bc

  19. wzdev-ci commented on Jan 3, 2012

    @wzdev-ci
    ContributorAuthor

    cybersphinx changed milestone from 3.0 to unspecified

  20. wzdev-ci commented on Jan 3, 2012

    @wzdev-ci
    ContributorAuthor

    cybersphinx commented


    Milestone 3.0 deleted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions