Update ConstructionAutomation.kt #12472
Closed
Conversation
This file contains 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
|
Incorrect, this is calculated in getStatDifferenceFromBuilding - we compare this city vs this city with the building, which includes the extra stats from tiles |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The AI currently does not evaluate tile yields from buildings. For granaries, stables, etc. this is not much of a problem as they're also valued in other ways, but the AI not building lighthouses is pretty bad.
Merging this PR simply as-is will allow the AI to build lighthouses again, but it would be better to extract the type and amount of stats from the unique, and multiply this by the number of respective tiles the AI is currently working in the city. How does one do so?