@FatsharkJulia @FatsharkStrawHat Hi there, Please forward this to the dev. This new condition added from the new update in the screenshot seems to be responsible for the bug. Remove “not was_special_active” check, fixed the bug on local for me. not sure if there is more to this, hope it helps you guys get this fix a bit faster.