Fix scenario chain graph normalization#381
Open
Ultimationzzz wants to merge 1 commit into
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
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.
Fixes scenario
.ymtcorruption after deleting scenario chains or scenario points.ScenarioRegion.RebuildChains()was previously empty, so saved scenario files could retain stale chain edge references, edge indexes, or node edge flags after edits. This change normalizes the scenario chaining graph before save by compacting node/edge indexes, rebuilding chainEdgeIdsfrom surviving edges, removing invalid references, and refreshingHasIncomingEdges/HasOutgoingEdges.Tested by deleting scenario chains from FiveM scenario region files and verifying the saved files load without crashing.