-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow player to choose a specific seed through the UI #358
Comments
How about showing the seed in grey somewhere and hinting at the R key to regenerate it? 🙂 |
Showing the seed in grey somewhere sounds fine for #359 . But I don't see how having an |
How about this: when starting a game with no |
As an alternative, we could always provide a default and then specify if it is possible* to override the seed. Then when you press E we would bring up a form to edit the scenario parameters (#558) but for now, that would only be the seed. Brick ships with functions to create forms ( *) The |
Created a related issue about specifying from the command line: #1006 |
Closes #358 and closes #866. Allows specification of a seed value and/or the path of a script to run. Specifying a script to run in advance allows eligibility for code size scoring. Some effort was invested into integrating the Brick `FileBrowser` widget and discovering its idiosyncrasies. This paves the way for more applications of `FileBrowser` within Swarm. ## Usage From the scenario selection menu, press the `o` key to pop up a dialog for launch options. ![Screenshot from 2023-06-06 01-38-25](https://github.com/swarm-game/swarm/assets/261693/e306f2ce-db30-4906-9b02-db8e44bc5e99) Any manually-selected initial-script or seed are persisted to disk and will pre-populate the launch configuration dialog upon the next play. If a certain scenario is subsequently launched the normal way (i.e. by pressing `Enter` instead of `o`), then this clears the saved script path/seed, and the next pop-up of the launch configuration dialog will not see its fields pre-populated. ## Warning: Save format changed This PR changes the `ScenarioStatus` datatype, and therefore game status/progress saved previously to this PR will not be recognized. See #974 (comment) for discussion about this situation.
Currently, a specific seed can be chosen on the command line, e.g.
But if you choose e.g. classic mode via the "New Game" menu, you get a random seed with no way to override it. There should be some (optional) mechanism by which the user can specify a seed if they wish (e.g. for "set seed"-style speedruns, to play the same world as their friend, etc.).
The text was updated successfully, but these errors were encountered: