Add option to lock file to current levelset (#588) #888
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds an option to lock an existing save file to its current levelset (preventing the user from switching levelset).
This option can be toggled from the
FileSelectSlotOUI, or using thelockcommand (like theassistorvariantscommands).The lock status is saved in the
CoreModuleSaveData.I'm wondering if adding a button can causes issues in TASes, if they don't expect it.
Closes #588.