feat(GUI): enable race seed button for dev with spoiler log lock #2311
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.
This adds the race seed button to the web UI for dev forks.
So far, this was disabled, as dev forks have no encryption.
However, in response, maybe competitive events disabled spoiler log generation on dev in their presets to streamline the process. This is no longer needed with this, as a dev seed can now be created as race seed.
As against release, the seed will still not be encrypted, but the spoiler log will be locked away and won't be available without admin interference.
In addition, a custom seed entered will be scraped and replaced with a random string, and the actual randomizer seed will not be visible by any means on the seed page or the settings log unless the spoiler log is unlocked.