Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Death Loop bug #2469

Closed
deezl opened this issue Mar 9, 2015 · 4 comments
Closed

Death Loop bug #2469

deezl opened this issue Mar 9, 2015 · 4 comments
Labels
Bug Issues that were confirmed to be a bug @ Server / Client / Env.

Comments

@deezl
Copy link

deezl commented Mar 9, 2015

On VanessaE's Creative server, somehow players were "killed" in a certain location, so they appeared "dead" (as in player model in laying down position). On subsequent logins of the player, they were greeted with the death screen upon emerging into the world, and after selecting "respawn" they remained "dead" and could still move around, but not interact with anything. The same issue remained even after the server was rolled back to stable-0.4 branch. The only way to fix it turned out to be to enabling damage for the server so that the players could actually finish dying and respawn with full hp. Another player reported in chat having experienced the same bug in singleplayer, also on near latest git. The bug occured while VE's server was running at: 9e67579.
Some relevant messages from debug associated with this event:

23:44:56: ERROR[ServerThread]: ServerEnv: Trying to store id=7560 statically but block (-43,1,-28) already contains 2653 objects. Forcing delete.
23:44:58: ERROR[ServerThread]: ServerEnv: Trying to store id=7561 statically but block (-43,1,-28) already contains 2653 objects. Forcing delete.
23:44:58: ERROR[ServerThread]: ServerEnv: Trying to store id=7562 statically but block >(-43,1,-28) already contains 2653 objects. Forcing delete.

And....:

23:58:14: ERROR[ServerThread]: ServerEnv: Trying to store id=12639 statically but block (-19,1,-27) already contains 500 objects. Forcing delete.
23:58:16: ERROR[ServerThread]: ServerEnv: Trying to store id=12641 statically but block >(-43,1,-28) already contains 2677 objects. Forcing delete.

@deezl
Copy link
Author

deezl commented Mar 9, 2015

Also, the above "Forcing delete" mentions have been flooding debug on the server lately, and running clearobjects does not help. Not sure if this is related to the death loop issue, but the ERROR messages were occuring at the time of the bug.

@ShadowNinja
Copy link
Member

Error messages are irrelevant. The server simply shouldn't allow death if damage is disabled.

@ShadowNinja ShadowNinja added Bug Issues that were confirmed to be a bug @ Server / Client / Env. Medium priority labels Mar 10, 2015
@nerzhul
Copy link
Member

nerzhul commented Mar 15, 2015

Partially fixed by b2801d8 which properly sent the HP or deathscreen on those servers when client connects.

@nerzhul
Copy link
Member

nerzhul commented Mar 16, 2015

Fixed: aaf26b3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues that were confirmed to be a bug @ Server / Client / Env.
Projects
None yet
Development

No branches or pull requests

3 participants