#Crash On Scoring = "Attempt to index upvalue 'effects'"

5 messages · Page 1 of 1 (latest)

rugged moon
#

I just started playing with Cryptid, and after going on a crazy run with the wormhole deck the game crashed when I tried to play a hand.

Stack traceback is attached to report.

small spade
#

idk if this crash specifically is fixed but your mods are out of date

rugged moon
# small spade delete old mods and replace them with these https://github.com/MathIsFun0/Crypti...

did that but only ended up resulting in a new error.

main.lua:1845: functions/misc_functions.lua:1585: attempt to perform arithmetic on local 'owned' (a nil value)

Additional Context:
Balatro Version: 1.0.1n-FULL
Modded Version: 1.0.0~ALPHA-1304a-STEAMODDED
LÖVE Version: 11.5.0
Lovely Version: 0.6.0
Steamodded Mods:
    1: Talisman by MathIsFun_, Mathguy24, jenwalter666, cg-223 [ID: Talisman, Version: 2.0.2, Uses Lovely]
        Break Infinity: omeganum
    2: Cryptid by MathIsFun_, Cryptid and Balatro Discords [ID: Cryptid, Priority: 1e+299, Version: 0.5.3c, Uses Lovely]
    3: Balustro by Dorian Bates, someone23832, Mr. Oddman [ID: Balustro, Version: 0.10, Uses Lovely]
Lovely Mods:

Stack Traceback
===============
(3) global C function 'error'
(4) Lua field 'update' at file 'main.lua:1845'
Local variables:
 dt = number: 0.0189003
 success = boolean: false
 msg = string: "functions/misc_functions.lua:1585: attempt to perform arithmetic on local 'owned' (a nil value)"
(5) Lua function '?' at file 'main.lua:931' (best guess)
(6) global C function 'xpcall'
(7) LÖVE function at file 'boot.lua:377' (best guess)
Local variables:
 func = Lua function '?' (defined at line 902 of chunk main.lua)
 inerror = boolean: true
 deferErrhand = Lua function '(LÖVE Function)' (defined at line 348 of chunk [love "boot.lua"])
 earlyinit = Lua function '(LÖVE Function)' (defined at line 355 of chunk [love "boot.lua"])```
echo trench
#

I'm having a similar problem (the bug report about chocolate die and ghosts). I installed those mods and I'm still getting the error, but now it's happening on line 1651. If I start a new run, is that likely to help? I'd like to finish this one if possible, but if something about the previous state is irretrievably broken I'll start over.