Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Don't build between minerals and command center #43

Open
alkurbatov opened this issue May 15, 2020 · 2 comments
Open

Don't build between minerals and command center #43

alkurbatov opened this issue May 15, 2020 · 2 comments
Assignees
@ImpulseCloud
Labels
bug

Comments

@alkurbatov
Copy link
Owner

No description provided.

@alkurbatov alkurbatov added the bug label May 15, 2020
@alkurbatov alkurbatov changed the title Don't build between minerals and command center. Don't build between minerals and command center May 15, 2020
ImpulseCloud added a commit to ImpulseCloud/suvorov-Impulse that referenced this issue Feb 27, 2021
@ImpulseCloud
Fix issue alkurbatov#43 "Don't build between minerals and command cen…
ea06c40 
…ter"
@ImpulseCloud
Copy link
Contributor

This is a simple solution for now. As this is a starter bot, I'd like new coders to understand the buffer exclusion zone, rather than use a more complicated algorithm. Eventually, it would be best to use a cached build_grid (0.5x0.5 cells) and mark those cells as reserved/off-limits which intersect a line segment between the base and each mineral/geyser.

ImpulseCloud added a commit to ImpulseCloud/suvorov-Impulse that referenced this issue Feb 27, 2021
@ImpulseCloud
Revert "Fix issue alkurbatov#43 "Don't build between minerals and com…
b8d59c8 
…mand center""

This reverts commit ea06c40.
@ImpulseCloud ImpulseCloud mentioned this issue Feb 27, 2021
Merged
@ImpulseCloud
Copy link
Contributor

alkurbatov: "we can use the placement grid abstraction from the api and mark the related tiles as occupied."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ImpulseCloud ImpulseCloud

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alkurbatov @ImpulseCloud