Hardcore Ghosts Don't Move Server-Side

[lost-werewolf]

• TShock version: 6.0.0
• TShock build number (if known):

Reproduction steps (if applicable)?

1. Die in hardcore.
2. As a ghost, move away from where you died.
3. Section data won't be loaded as you move away from where you died, indicating your position is not updating on the server side.

Log file:

2025-10-03_18-43-56.log

I am suspect of this line in the Bouncer, but there was no logging of rejection for my player updates, so take it with a grain of salt.
https://github.com/Pryaxis/TShock/blob/general-devel/TShockAPI/Bouncer.cs#L586

This issue is not present with the vanilla server software, which I tested before creating this issue.

[sgkoishi]

🤔 if you have DebugLog you should also see Bouncer / OnPlayerUpdate rejected from (corpses don't move) {playerName} right? seems a bit weird

[lost-werewolf]

Yeah this has me stumped. Not sure why the ghost just doesn't move, this doesn't happen if you set Player.ghost to true either by using a 3rd-party client or through a server plugin.

[lost-werewolf]

I did some more digging. Turns out, this seems to be the problem:

TShock/TShockAPI/TShock.cs

Line 1643 in a867772

if ((player.State < (int)ConnectionState.Complete || player.Dead) && (int)type > 12 && (int)type != 16 && (int)type != 42 && (int)type != 50 &&

Completely ignoring a lot of packets when the player is dead. This causes desyncs because players can still send a lot of packets while dead, such as killing their projectiles - such a desync can be seen VERY easily if another player on a server running TShock, dies while using something like a Drill or Chainsaw. The projectile stays active for other clients despite it being gone for them.

[lost-werewolf]

Oops, I'm blind. That was mentioned in the PR aiming to fix this, my bad!