event.getPlayer().kickPlayer("") --> Duplicates in server?

Discussion in 'Plugin Development' started by Dino Filippini, Jun 17, 2012.

Thread Status:
Not open for further replies.
  1. Offline

    Dino Filippini

    As per the title...

    Code:
    event.getPlayer().kickPlayer("Some message");
    Will kick the player off the server, without actually kicking them from the console, leaving a ghost profile and user in the game world. Any insight as to why this occurs?

    [​IMG]
     
  2. Offline

    r0306

    Dino Filippini
    Try adding this to the code:
    Code:
    event.getPlayer().remove();
    
    BTW, are all those names on there the same character? They have different names...
     
  3. Offline

    Dino Filippini

    I'll try that code out now and edit in the response in a bit, thanks! To answer the other question, those are all entities from my account Fusionpro. I had a different player login to confirm and the same thing happened under their name. It's really bizarre.

    Edit -> No change with the .remove addition. Still have a player duplication bug. :confused:
     
  4. Offline

    md_5

    Try the latest dev build, should be a fixed issue.
     
  5. Offline

    Dino Filippini

    Used build 2237 and I'm still having the console not kick people. The server terminates the connection for the player, but thinks that they're still connected and have an in-game entity.

    Clarification: The same issue persists exactly.

    Edit -> The kicking of the player is occurring within an onRespawnEvent, perhaps the respawn event is causing problems in memory when kicking a player that is queued to respawn?
     
  6. Offline

    md_5

    We really need to make this clear.
    Never ever kick the player in:
    Player Join
    Player Login
    Player Respawn
    Instead schedule a sync delayed task 1 tick after.
     
  7. Offline

    Dino Filippini

    Player Death might be another one to add to that list... It creates a duplication bug where the items of the player are dropped but retained on login.
     
Thread Status:
Not open for further replies.

Share This Page