The game can crash when the Snurtle Shell Armour is in the backpack.
[00:11:18]: [armorsnurtleshell|onuse] owner=107224 - wilson [00:11:23]: [armorsnurtleshell|droptargets] owner=108541 - backpack(LIMBO) [00:11:23]: [string "scripts/prefabs/armor_snurtleshell.lua"]:27: attempt to index field 'sg' (a nil value) LUA ERROR stack traceback: scripts/prefabs/armor_snurtleshell.lua:27 in (field) fn (Lua) <22-36> inst = 108539 - armorsnurtleshell(LIMBO) (valid:true) owner = 108541 - backpack(LIMBO) (valid:true) scripts/scheduler.lua:194 in (method) OnTick (Lua) <168-225> self = running = table: 15C5AB60 waitingfortick = table: 15C5A9F8 tasks = table: 15C5A818 waking = table: 216FB0D8 attime = table: 15C5A9A8 hibernating = table: 15C5AD18 tick = 17678 k = PERIODIC 108539: 5.000000 v = true already_dead = false scripts/scheduler.lua:406 in (global) RunScheduler (Lua) <404-412> tick = 17678 scripts/update.lua:166 in () ? (Lua) <150-223> dt = 0.033333335071802 tick = 17678 i = 17678 [00:11:23]: [string "scripts/prefabs/armor_snurtleshell.lua"]:27: attempt to index field 'sg' (a nil value) LUA ERROR stack traceback: scripts/prefabs/armor_snurtleshell.lua:27 in (field) fn (Lua) <22-36> scripts/scheduler.lua:194 in (method) OnTick (Lua) <168-225> scripts/scheduler.lua:406 in (global) RunScheduler (Lua) <404-412> scripts/update.lua:166 in () ? (Lua) <150-223>
The [armorsnurtleshell|*] lines are my debug prints, so line numbers might be a little off.
Thanks to @DejaVuZXY for noticing it.
Steps to Reproduce
1. Equip Snurtle Shell Armour. 2. Right click on it to [i]Use[/i] it. 3. Right click on it to [i]Unequip[/i] it. 4. Pick up the backpack from the ground. 5. Move the armour from the inventory to the backpack. Steps 2-5 have to be done within 5 seconds.
1. Equip Snurtle Shell Armour. 2. Right click on it to [i]Use[/i] it. 3. Right click on it to [i]Unequip[/i] it. 4. Pick up the backpack from the ground. 5. Move the armour from the inventory to the backpack. Steps 2-5 have to be done within 5 seconds.
A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now