Conditional nest predecessor check for subway and trail map unhardcoding #67648
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.
Summary
None
Purpose of change
Being able to test for underlying predecessors will allow me to select appropriate nests/foliage for trails in #67470 depending on whether they're in swamp/forest/forest_thick and also help with the way I want to do sub stations with a partial subway unhardcoding I'm doing
Describe the solution
Adds a check in the same vain as the others but that only checks the map itself rather than it's neighbors
Adds documentation
Describe alternatives you've considered
Testing
Checked it worked using some simple nests like this one on road_straight
"place_nested": [ { "chunks": [ "24x24_fence1" ], "x": 0, "y": 0, "predecessors": [ "field" ] } ]
Also tested match type ( and that nests still spawn elsewhere >-< )
Additional context