Move custom navmesh data to a separate file, to be grouped by levels in functions#8
Merged
Merged
Conversation
Owner
Author
|
Not merging this yet, I am not happy about the names... Need to sleep on it. |
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.
This change had to be done.
Bloating entity.gc was not nice. And it led to merge conflicts if the modbase changed a navmesh while a modbase-using mod also had navmeshes. So these changes will resolve all problems.
Now you can have your navmeshes in separate functions, in the custom-navmesh-data.gc file. Should be much more readable, and much harder to get conflicts.