-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Comments
This happens because 3d_armor removes the 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). |
So, why does the client think that the player is dead if Enable Damage is unchecked? |
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. |
#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. |
Hah... I noticed that the other day and was about to track that down, but couldn't find time to that. |
Minetest version
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.
The text was updated successfully, but these errors were encountered: