style: Apply consistent field order to OpenContain Behavior module variants#67
Open
Stubbjax wants to merge 1 commit into
Open
Conversation
xezon
approved these changes
May 29, 2026
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.
This change applies consistent field orders to all
OpenContainBehaviormodule variants across all INI files. Fields are ordered based on the most common order patterns, their code declaration/parse orders, and some minor grouping of related orders where it made sense.Orders
Below are the orders applied to the respective modules.
GarrisonContain
HealContain
HelixContain
InternetHackContain
OverlordContain
ParachuteContain
RailedTransportContain
RiderChangeContain
TransportContain
> TunnelContain (unaffected)