Open pridit opened 2 years ago
This happens both dead and alive, I can't find a way to reproduce but people consistently seem to manage doing something that causes these units to stick around. In the most recent case someone is actively occupying the slot, but there is another unit sitting at spawn which is not controlled. This means the script to scan them won't find this unit, as the playable unit is assigned to an active player.
This may possibly be fixed as a result of a refactor to use onPlayerDisconnected
- if these rogue units can be captured by that, then this will be fixable.
Still happens, though the unit was dead and the body could not be hidden. Seems to have been significantly curtailed but can't really know, and at the least this is a new symptom.
Cause of this is respawning while the handlers are loading, so still probably possible to trigger by being killed but it's unlikely enough, with disabling the option from the menu, for me to not care.
This has been observed on a unit not in the spawn position, so there's a different issue happening that must be possible to fix.
Reproducible by gesturing then disconnecting, which causes the unit to linger and repeat their animation.
Fixed the above case on local dedi but didn't work on local mp. Will await to see this case actually resolved on server or not.
Gone back and forth through various functions, hiding, deleting, but they always seem to linger. I can't even figure out how to reproduce it as usually when players disconnect they automatically get cleared which happens for the majority, but just a few instances a day the unit remains in the world. Might not ever be able to get to the bottom of it until I can reproduce it.
Could be something to do with group, doesn't seem to reproduce when the player loses connection as I have tried doing that without this ever happening the unit always clears gracefully. Given they always seem to originate at spawn maybe it's related to disconnecting/going back to the lobby when loading in or something.