Local Player is being set up multiple times

Hello!

I am having a weird issue on my server, where if a player disconnects and reconnects they get respawned (in a different body) and get the following message on the top left of the screen: Local Player is being set up multiple times.

I do have my own custom plugins on the server, however I don't see any reason this would happen in the code. Has anyone else experienced this? If so do you know what caused it?

--The FSM

 

@Wulf Do you know what might cause the player to get bugged? Would leaving the player object in a List<baseplayer> when the player disconnects cause it?

 

@Wulf I just checked my logs (thinking I wouldn't find anything) and I found the following errors:

Code:

ArgumentNullException: Argument cannot be null.
Parameter name: key
  at System.Collections.Generic.Dictionary`2[SpawnPopulation,System.Int32].ContainsKey (.SpawnPopulation key) [0x00000] in <filename unknown>:0
  at SpawnHandler.RemoveInstance (.Spawnable spawnable) [0x00000] in <filename unknown>:0
  at Spawnable.Remove () [0x00000] in <filename unknown>:0
  at Spawnable.OnDisable () [0x00000] in <filename unknown>:0
UnityEngine.Object:Destroy(Object, Single)
GameManager:Destroy(GameObject, Single)
BaseNetworkable:EntityDestroy()
BaseNetworkable:Kill(DestroyMode)
BaseNetworkable:KillMessage()

Could this be something with Oxide? I'm on Oxide 2.0.2131 for Rust939.93
[DOUBLEPOST=1468027830][/DOUBLEPOST]I'm going to update, looks like I'm a tad bit behind....Could be my issue

 

@Wulf Interesting....That error above doesn't have anything to do with my plugin or any other plugin on the server it seems. Maybe I am mis-reading it though.

 

@Wulf Updating everything seems to have fixed the player issue. I am still having issues with ArgumentNullException popping up in the logs. Seems to be rust related however so not a whole lot I can do about it.