-
Notifications
You must be signed in to change notification settings - Fork 39
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
[BUG] Attacking Barracks #186
Comments
I'll check it |
FYI - this was happening before your pull request, so not your fault. It's part of pushlane mode |
pushlane:Desire() only checks if there are towers nearby. So barracks are just pushed ins some edge cases. |
Nvm, I'll fix it now. pushing looks somewhat fine for now. I'll work on global movement for now. This should improve push and defense further. |
Lane switching code is in decision.lua ... b/c I was lazy implementing it. |
btw... the pushlane:Desire() has other checks ... I still don't think it would work (for whatever reason) even if you added a rax check into Desire() |
yeah, mode is actually pushlane. I'm checking the think method right now. |
Ok. so bot:GetNearbyTowers() seems to return barracks as well. great. |
and what does bot:GetNearbyBarracks() return? I assume nothing? |
exactly. I'll file a bug on dev.dota2.com and split up the tower list by names for now. |
Had a fix. Deleted it. The end. |
aight, rewrote it. #187 |
Our bots no longer right click barracks, no idea why.
They are fine on towers, shrines, and Ancient ( I believe ).
The text was updated successfully, but these errors were encountered: