Fixed AI bug when an UndeploysInto building undeploys #1868
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
The AI bug never produced the expected unit when is undeployed.
|
Nightly build for this pull request:
This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build. |
Contributor
|
I think you should add another flag to control it, rather than modifying the vanilla behavior. |
Contributor
|
Since the problem was solved by adding a new flag in #1938, this PR is being closed. |
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.
The AI bug never created the expected unit when is undeployed.
Tested in Map action 60 & forcing the AI to undeploy (for example when the affected deployed has a minimum range in the weapon and the enemy is inside that range).
Bugfix of the reported issue:
#1851
Since this is only fixing a very small coding mistake no documentation of any kind should be required.