Allow GMs to set gameSpeed > 1.0 #2680
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a GuiSelector to select a time scale for the game, ranging from 1x (the default) to 16x.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add a selector for set timescales to 1x, 2x, 4x, or 8x to the GM screen (selector next to Pause) and Lua API (functions
getGameSpeed()andsetGameSpeed()).Changing the timescale should affect all server and client behaviors.
Toggling pause from the GM screen resumes at the previously selected timescale. Toggling pause elsewhere on the server, or with Lua function
unpauseGame(), should always resume at 1x speed.I've tried testing higher timescales by letting scenarios with and without victory/defeat conditions run for several real-time hours on a server and client. Additional testing would be useful.
I limited timescales to 8x since 16x and beyond cause too many client-side issues, particularly with internal repair crew movement and scanning.
Screencast_20260102_223521.webm