-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Phantom Builder Bots Fail sometimes #1610
Comments
I'll assume this is an intended behavior, all poor AI by the units seems to be intended behavour, shame, game would be funner if AI acted with little bit of intelligence. |
This specific problem isn't intentional behavior, but in general, many parts of the AI are being thrown out in 6.0. The command center doesn't feel like a very good mechanic for unit control, and making units do everything you want them to do automatically (e.g. patrolling or attacking) isn't working out very well. |
@Anuken Are you saying that this issue will be fixed in 6.0 and units will auto-rebuild properly? |
He's saying that the AI that causes the issue won't be a part of 6.0 |
Platform: Windows
Build: Steam 104.3
Issue: The phantom builder bots will fail to rebuild a structure if a unit is in the position of the structure, furthermore it will never re-attempt to build it, resulting in gradually multiple structures missing. A solution would be to task builder bots to keep re-attempting to build if they fail the first time.
Steps to reproduce: When a unit goes to build a building, if there is a unit already in that position, the build order will cancel. I think this affects phantom bots too. For example, imagine wall defenses, they get destroyed and as they do two things happen, enemy units run into the position where the wall was, and the builder bots run to try to rebuild the wall. The builder bots will fail because there is a unit already in that position. When this occurs the builder bot will never re-attempt to build that wall.
This happened to me in the image below. It has happened frequently before but only recently have I figured out (I think) what is triggering the bug.
The text was updated successfully, but these errors were encountered: