Ghost players #78

Open
opened 2021-09-28 13:33:06 +02:00 by unfa · 3 comments

Maybe player scenes should ping home to make sure their network authority is still online, or to check if there are other player scenes and prune the stuck ones.

We've experienced this on the team meeting, and I have managed to reproduce it by running a few clients, stopping and starting the server, reconecting clients etc.

Werid things happen, we need to find a way to prevent that.

Maybe player scenes should ping home to make sure their network authority is still online, or to check if there are other player scenes and prune the stuck ones. We've experienced this on the team meeting, and I have managed to reproduce it by running a few clients, stopping and starting the server, reconecting clients etc. Werid things happen, we need to find a way to prevent that.
Poster
Owner

I guess the simplest way to fix this would be to periodically check for player scenes under /Main/Players/ and se if they belong to any active peer. If not - delete them.

I guess the simplest way to fix this would be to periodically check for player scenes under `/Main/Players/` and se if they belong to any active peer. If not - delete them.
Poster
Owner

I've managed to trigger this problem by connecting and suspending my computer while being connected.

When I resumed and saw that the server has disconnected, I have reconnected and saw my old body hanging where I left it.

I should investigate what's going on when a player disconnects.
Maybe these bodies are put into the respawn queue somehow?

I've managed to trigger this problem by connecting and suspending my computer while being connected. When I resumed and saw that the server has disconnected, I have reconnected and saw my old body hanging where I left it. I should investigate what's going on when a player disconnects. Maybe these bodies are put into the respawn queue somehow?
gilgamesh added the
bug
label 2021-12-14 16:06:08 +01:00
Poster
Owner

I think each player should generate and confirm with the server a random token thwt would let us distinguish the active and dead connections. Also we could do a garbage collection of dead player nodes when a new player joins and leaves to ensure game stare integrity.

Check the nodes, make sure eaxh node matches a peer ID with an active connection. Whatever is left without a match should be pruned.

I think each player should generate and confirm with the server a random token thwt would let us distinguish the active and dead connections. Also we could do a garbage collection of dead player nodes when a new player joins and leaves to ensure game stare integrity. Check the nodes, make sure eaxh node matches a peer ID with an active connection. Whatever is left without a match should be pruned.
unfa added this to the 0.1.2 milestone 2021-12-27 18:08:36 +01:00
This repo is archived. You cannot comment on issues.
No Milestone
No project
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: unfa/liblast#78
There is no content yet.