Currently if BuildMgr has something at the top of its build stack that can't be constructed for whatever reason (not enough resources of a certain type, not enough supply... whatever) it can stall other build orders that should be able to run.
For example, if we have 1000 minerals and no gas, and a firebat is at the top of the build stack, BuildManager stops building things entirely until we get enough gas to fulfill the request to build the firebat.
Requests on the build stack should have priority, but if there is a holdup with something, the BuildManager should still be able to look through its queue and find the next thing it is able to build and get started on it (like marines or supply depots in the example above).
Currently if BuildMgr has something at the top of its build stack that can't be constructed for whatever reason (not enough resources of a certain type, not enough supply... whatever) it can stall other build orders that should be able to run.
For example, if we have 1000 minerals and no gas, and a firebat is at the top of the build stack, BuildManager stops building things entirely until we get enough gas to fulfill the request to build the firebat.
Requests on the build stack should have priority, but if there is a holdup with something, the BuildManager should still be able to look through its queue and find the next thing it is able to build and get started on it (like marines or supply depots in the example above).