Fix #10135: Cost of building multiple objects might not match test #10137
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.
Motivation / Problem
As reported in #10135 (thanks @James103 for the excellent diagnosis!), objects might not consent to being built based on the locations of other objects built within the same command — for example distance restrictions between wind turbines in OpenGFX+ Landscape.
This creates an assertion because the test command and the exec command don't match costs.
Description
Add the
CMD_NO_TEST
flag to CmdBuildObjectArea to tell OpenTTD we're okay with this potential difference in cost.Closes #10135.
Limitations
Checklist for review
Some things are not automated, and forgotten often. This list is a reminder for the reviewers.