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

Using 3d_armor mod with "Enable Damage" inactive makes the world mostly refuse to load #9022

Closed
style-nine opened this issue Oct 6, 2019 · 9 comments · Fixed by #9025
Closed
Labels
Blocker The issue needs to be addressed before the next release. Bug Issues that were confirmed to be a bug
Milestone

Comments

@style-nine
Copy link

Minetest version
I did a bisect and found the first commit where this bug appeared:

81c7f0a ("Send ActiveObjects once right after Init2", 2019-08-25)

OS / Hardware

Operating system: Ubuntu 18.04
CPU: AMD x86 64

GPU model:
OpenGL version:

Summary

If you switch to Damage not enabled, the world will mostly refuse to load.

Steps to reproduce

Create a new world with MTG and then enable "3d_armor" mod. Uncheck the "Enable Damage" option. "Play Game" and notice how it mostly doesn't load.

@style-nine style-nine added the Unconfirmed bug Bug report that has not been confirmed to exist/be reproducible label Oct 6, 2019
@style-nine
Copy link
Author

@sfan5 sfan5 added Blocker The issue needs to be addressed before the next release. Bug Issues that were confirmed to be a bug and removed Unconfirmed bug Bug report that has not been confirmed to exist/be reproducible labels Oct 6, 2019
@sfan5 sfan5 added this to the 5.1.0 milestone Oct 6, 2019
@sfan5
Copy link
Member

sfan5 commented Oct 6, 2019

This happens because 3d_armor removes the immortal armor group, making the client think the player is dead, so it won't send any movement packets.

While this is technically not an engine bug, I'm not sure whether we want the fragile construct around active objects (has caused 2 issues so far) for the sole purpose of disabling autoforward if the player is dead (#8387 which is an extremely minor annoyance).

@style-nine
Copy link
Author

So, why does the client think that the player is dead if Enable Damage is unchecked?

@ClobberXD
Copy link
Contributor

I'll remove that annoying bit of code for 5.1.0, and we'll look at a better implementation once 5.1.0 has been released.

@ClobberXD
Copy link
Contributor

Btw, I can't reproduce this at commit 4682c7b, which comes after 81c7f0a. I've disabled damage, and enabled 3D Armor modpack.

@style-nine
Copy link
Author

You sure about that? On my screen, 4682c7b is Sep 8 and 81c7f0a is Sep 14.

see: https://github.com/minetest/minetest/commits/master?after=825579b43d6454cc33607ab8eff4e896b003b801+34

@ClobberXD
Copy link
Contributor

ClobberXD commented Oct 7, 2019

Oops, my bad, sorry. I'll test with 81c7f0a.

EDIT: I can reproduce with 81c7f0a.

@ClobberXD
Copy link
Contributor

#9025 reverts the optimisation that the causes this issue. @style-nine, it'd be nice if you could test the PR and confirm that it works.

@lhofhansl
Copy link
Contributor

Hah... I noticed that the other day and was about to track that down, but couldn't find time to that.
Thanks for figuring this one out @ClobberXD .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocker The issue needs to be addressed before the next release. Bug Issues that were confirmed to be a bug
Projects
None yet
4 participants