G.GAME.challenge_tab contains challenge data out of G.CHALLENGES for the currently active challenge. In vanilla, this data gets saved properly, so it is expected to behave the same way in smods. Instead, due to the challenge data being an instance of SMODS.Challenge, and thus, Object, the data gets replaced with "MANUAL_REPLACE". This causes any code making use of G.GAME.challenge_tab to break; for instance, holding R while in a challenge run that was exited and continued no longer restarts the same challenge, instead starting a run on a completely unmodified Challenge Deck.
To exactly replicate vanilla behavior, the full data would have to be saved. I'm not sure if it's good enough to just recover the challenge data from the key saved in G.GAME.challenge, or how this should handle challenges that were removed after a reload.
G.GAME.challenge_tabcontains challenge data out ofG.CHALLENGESfor the currently active challenge. In vanilla, this data gets saved properly, so it is expected to behave the same way in smods. Instead, due to the challenge data being an instance ofSMODS.Challenge, and thus,Object, the data gets replaced with"MANUAL_REPLACE". This causes any code making use ofG.GAME.challenge_tabto break; for instance, holding R while in a challenge run that was exited and continued no longer restarts the same challenge, instead starting a run on a completely unmodified Challenge Deck.To exactly replicate vanilla behavior, the full data would have to be saved. I'm not sure if it's good enough to just recover the challenge data from the key saved in
G.GAME.challenge, or how this should handle challenges that were removed after a reload.