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

Crash with minetest-5.8.0 when digging chest with inventory #99

Open
dennisjenkins75 opened this issue Mar 24, 2024 · 1 comment
Open
Labels

Comments

@dennisjenkins75
Copy link

I did not witness this myself, just the player's report and the crash report in my server logs.

Player claims that the crash trigger is a digtron attempting to dig a node with an inventory (I assume a chest in a dungeon?). They items are obtained, but the chest remains. So this is also an item duplication glitch (at the expense of a server crash).

I have not attempted a manual repro, as I don't have a digtron and don't use them (my players do though).

1hit@EdgyNet:~$ ./opt/minetest/bin/minetestserver --version
Minetest 5.8.0 (Linux)
Using LuaJIT 2.1.0-beta3
BUILD_TYPE=Release
RUN_IN_PLACE=0
USE_CURL=1
STATIC_SHAREDIR="/home/1hit/opt/minetest/share/minetest"

ServerError: AsyncErr: Lua: Runtime error from mod 'digtron' in callback node_on_receive_fields(): .../1hit/worlds/world/worldmods/awards/src/api_triggers.lua:148: attempt to call method 'sub' (a nil value)
stack traceback:
        .../1hit/worlds/world/worldmods/awards/src/api_triggers.lua:148: in function 'notify_digtron_dig'
        /home/1hit/worlds/world/worldmods/digtron/awards.lua:32: in function 'award_item_dug'
        ...it/worlds/world/worldmods/digtron/util_execute_cycle.lua:334: in function 'execute_dig_cycle'
        ...orlds/world/worldmods/digtron/nodes/node_controllers.lua:166: in function 'auto_cycle'
        ...orlds/world/worldmods/digtron/nodes/node_controllers.lua:283: in function <...orlds/world/worldmods/digtron/nodes/node_controllers.lua:257>
@BuckarooBanzay
Copy link
Member

worldmods/awards/src/api_triggers.lua:148

this looks like an award issue to me 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants