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.

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

Create basic Build Order lists #4

Closed
krogenth opened this issue Jan 11, 2022 · 0 comments · Fixed by #28
Closed

Create basic Build Order lists #4

krogenth opened this issue Jan 11, 2022 · 0 comments · Fixed by #28
Assignees
Labels
enhancement New feature or request

Comments

@krogenth
Copy link
Owner

krogenth commented Jan 11, 2022

We'll want to keep a rough idea of opening plays we can/should make depending on knowledge we have at the time. For now, we will only consider the map size.

As such, we'll want 3 different types of opening Build Orders based on map size:

  • small
  • medium
  • large

All Build Orders should use an std::initializer_list to define the list of std::pair's of BWAPI::Unit and int(supply used) to define when a build order should occur.

Broodwar counts the majority of units as 2 supply instead of 1, except zerglings, they are counted as 1 supply.
A good resource for various Zerg build orders can be found here: https://liquipedia.net/starcraft/Category:Zerg_Build_Orders

@krogenth krogenth added the enhancement New feature or request label Jan 11, 2022
@krogenth krogenth added this to To Do in AdditionalPylons via automation Jan 11, 2022
@krogenth krogenth moved this from To Do to In Progress in AdditionalPylons Feb 8, 2022
AdditionalPylons automation moved this from In Progress to Done Feb 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

2 participants