bugfix: Preserve scaffold health when AI building completes #1768
+12
−0
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
bobtista
force-pushed
the
bobtista/fix-ai-building-scaffold-health
branch
from
41f2e5c to
2029868
Compare
Skyaero42
requested changes
Nov 1, 2025
bobtista
force-pushed
the
bobtista/fix-ai-building-scaffold-health
branch
from
2029868 to
ab9b554
Compare
bobtista
force-pushed
the
bobtista/fix-ai-building-scaffold-health
branch
from
ab9b554 to
56e1f5b
Compare
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.
Addresses issue #1343
When AI buildings finished construction, they were incorrectly restored to their
BuildListInfoinitial health value (default 100%, can be set in WorldBuilder)The
BuildListInfo::m_healthfield is still used for its intended purpose: setting initial health on pre-placed buildings. It just no longer incorrectly applies to buildings under construction.Note: This change causes mismatches with retail, so it's behind flags.
Tested: The fix works (with RETAIL_COMPATIBILE_CRC and RETAIL_COMPATIBLE_BUG flags set)