#ignis
viscid onyx
Ty for making the thread, i couldn't figure how to
short timber
no worries
short timber
Ty for making the thread, i couldn't figure how to
see what happens when you change return { x_mult... to just return { xmult...
like it should work with the underscore, but I always use it without and it works perfectly
viscid onyx
same crash as before
short timber
alright, so it's not that
short timber
same crash as before
may I ask why there's an x_mult variable under config.extra when you never use it?
viscid onyx
Aside from an issue that I'll fix later, that code works fine, at least well enough to do what i want it to and not crash
short timber
it shouldn't change anything, but it's excess code that you could remove
oh right, the issue is in the joker
what's your file called?
viscid onyx
jokers.lua
short timber
ok so
none of the errors are coming back to your file specifically
which is weird
yeah, I have no idea
ask in a couple hours when someone else wakes up
that's my best advice
sorry 😓
viscid onyx
is oki, im wondering why it only crashes after they self-destruct
viscid onyx
I plan to be up for at least 2 more hours, take ur time
short timber
ok, I can't find a file that the crash log is complaining about, but I'm thinking maybe the instance of the card is being destroyed prior to the game checking for chip increases or something
viscid onyx
The video shows exactly what happens up to the crash, the chips and everything are already done being calculated, or at least they should be
short timber
oh, right
short timber
do you think it's because you changed the blind chip amount at all?
like infinity + a value usually throws an error
ah wait nvm
that's just a conditional, not a variable adding to the amount
viscid onyx
do you think it's because you changed the blind chip amount at all?
That high of a blind hasn't crashed for me before but I did think that maybe I should try a new run
(I'm just lazy so I didn't :P)
Bc if u watch the video, it only crashes the second the number is calculated
short timber
right
viscid onyx
I'm going to try that and, if need be, fixing the issue where they retrigger for some reason, but if neither of those work then I'm out of ideas
short timber
yeah, me too 💀
viscid onyx
(I hope the new run fixes it as I wouldn't know how to fix the re-triggering)
short timber
it's probably because you run two for loops instead of just one
short timber
replace destroying with destroy
*and see what happens
I think this may actually be the answer, since this tip on the wiki mentions you need destroy_card in an if statement rather than destroying_card
viscid onyx
Didn't change anything, I'll check if there's smth I forgot to change from destroying to destroy
short timber
alr
viscid onyx
Didn't change anything, I'll check if there's smth I forgot to change from `dest...
There was only that one thing to change
viscid onyx
is oki, the main issue was fixed
short timber
is oki, the main issue was fixed
oh lmao 😅 I didn't even notice