Author Topic: [fixed] r4372: Player who has quit should not be kickable  (Read 519 times)

filux

  • MegaGlest Team
  • Draco Rider
  • ********
  • Posts: 310
  • was OpenSuse x64, is Debian testing x64
    • View Profile
Tomreyn and I tested rejoin function.
I hosted a 1vs1 game and tomrey few times disconnected himself and rejoin,
then I kicked him and he properly couldn't join to game anymore.

After completed tests I spotted that I still have him in the "kicking menu", as if he was still in the game.
Menu, warning message and confirmation all pointed that he was still in game.
Then I kicked "him" few times and he was still present.



Edit (tomreyn, 2013-06-05):

 As Filux pointed pointed out correctly, I posted a duplicate report on this issue. The following posts stem from there.
« Last Edit: 5 June 2013, 06:53:25 by tomreyn »

tomreyn

  • Local Moderator
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
r4372: Player who has quit should not be kickable
« Reply #1 on: 3 June 2013, 22:48:52 »
I was hosting a game (with rejoin enabled) and Titi joined, later disconnected voluntarily. I received a message that he had disconnected. I then opened the in-game menu and looked at which players I could disconnect. Correctly, none should have been listed because Titi was the sole client and had left. However, Titi was still listed there and could be chosen for disconnection, and the command would seemingly succeed, i.e. there was no error message.


atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

filux

  • MegaGlest Team
  • Draco Rider
  • ********
  • Posts: 310
  • was OpenSuse x64, is Debian testing x64
    • View Profile

softcoder

  • MegaGlest Team
  • Battle Machine
  • ********
  • Posts: 2,239
    • View Profile
Re: r4372: Player who has quit should not be kickable
« Reply #3 on: 4 June 2013, 08:02:02 »
Should be fixed in 4380

tomreyn

  • Local Moderator
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
Re: r4372: Player who has quit should not be kickable
« Reply #4 on: 5 June 2013, 07:09:46 »
And [fixed] it is.
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·