-
Notifications
You must be signed in to change notification settings - Fork 4
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
Mesecons/punch/digtron/pipeworks crash #445
Comments
Similar error occurred again:
|
I'll take a closer look at this tomorrow and test a bit if I can reproduce this on local server. That's digitron crashing again... |
Proper fix would probably go somewhere in pipeworks but it wont hurt to have check in digtron so I'll add simple check there for now. |
auto close because of "fix" in commit msg... let this wait for PR and revert remote to https://github.com/minetest-mods/digtron.git |
Judging from the backtrace this looks like a mesecons triggered pipeworks-deployer that again triggers a digtron-controller... 😲 https://gitlab.com/VanessaE/pipeworks/-/blob/master/wielder.lua#L424 I don't think that was the idea behind the deployers but it should not crash either... :/ @S-S-X there was a missing |
Yes, I tested that old machine again as it seemed to work but didn't realize first that I caused crash by walking in front of dig heads and those attempted punch which failed in core because invalid value (fake player data table) was given instead of real player object.
But... that's idea behind minetest to test how things work 😁
AFAIK submodules do not normally track anything but instead fetch commit as detached head. |
)" This reverts commit 6c64a34.
thanks @S-S-X 👍 |
The text was updated successfully, but these errors were encountered: