I put it in a new file to leave the door open for list_, grant_, and revoke_ unlockable commands.
Things that trigger a profile save:
changing settings
changing loadout
granting any unlockable (including eclipse levels and whatnot)
collecting a pickup for the first time (item commands obviously bypass this but tonic afflictions in the inventory are counted as a pickup)
marking any menu icon as viewed (the yellow highlight for survivors/items/achievements/etc)
changing profiles
shutdown
So based on what a user has already unlocked, giving yourself unlimited coins and continuing with a full run may still only trigger the save on shutdown much later. This info could go as a note in the readme so people have a clearer expectation of what may save their profile and when, but a terse "enable early and leave on" suffices in my opinion.
This is the most sane way I've thought of implementing it, effectively with a file lock. Freezing StatSheets, unlockable granting, etc for only the duration of the command being enabled would be messy and prone to bugs.
Closes #99
I put it in a new file to leave the door open for
list_,grant_, andrevoke_unlockable commands.Things that trigger a profile save:
So based on what a user has already unlocked, giving yourself unlimited coins and continuing with a full run may still only trigger the save on shutdown much later. This info could go as a note in the readme so people have a clearer expectation of what may save their profile and when, but a terse "enable early and leave on" suffices in my opinion.
This is the most sane way I've thought of implementing it, effectively with a file lock. Freezing StatSheets, unlockable granting, etc for only the duration of the command being enabled would be messy and prone to bugs.