Fix mission failureOnReturnToSystem#361
Merged
gmoromisato merged 1 commit intokronosaur:masterfrom Feb 9, 2026
Merged
Conversation
ArisayaDragon
pushed a commit
to ArisayaDragon/TranscendenceDev
that referenced
this pull request
Feb 26, 2026
(cherry picked from commit c243e3f)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Several missions use
failureOnReturnToSystem = NNNwhich is intended to fail the mission if the player spends more than the specified number game ticks outside the system. However, the implementation was using the Windows system get ticks call which returns the number of milliseconds since the computer was last started.