shadowen / lightning-ai Goto Github PK

Improve the Debug Engine so that you can see which modules are active, and turn them on/off with chat commands.

Expansions are not recognized as additional bases; the ai will ignore them completely.

Investigate why units that are on paths sometimes will get stuck even while being issued orders.

Units won't follow the path until they hit a point on the path. They should be following a small distance behind the path pointer.

Move node costs and parent pointers to local variables to enable code to be parallelized and iterative deepening.

Currently, all the workers are sent to build a single building. The bot needs a way to keep track of which worker it already sent, and not send any more. Try incorporating "builder" as a member of buildingPlan.

Use the BuildManager along with BuildingPlan to reserve minerals that should be used to build a specific structure.

Drawing functionality should be seperately accessible from the actual call to draw() to avoid unintentional infinite recursion.

https://github.com/vjurenka/BWMirror

If two building plans are created before the first one is laid down, the building plans can overlap, causing an invalid building plan.

A pathfinding engine would help scouts not get stuck, improve micro performance, and also help the buildmanager move units out of the way.

Pull workers to defend a 4-6 pool attack.

Wraiths do not currently recognize that bunkers can shoot them.

Bot has no idea when mineral patches are mined out.

When a visible building lands, the resultant landed building is not registered properly. An update needs to be fired when a building is detected to have landed (check in onFrame).

Whenever a refinery is destroyed, a new geyser unit is created. This will likely break the Base system.

BW crashes when the game starts.

Add memory for buildings we have seen.

It seems 4-5 workers are being assigned to mine gas and 4 of them are actually mining gas.

Make the pathfinder re-run if an enemy building is revealed to be in the way.

The AI has trouble scouting to find the enemy and attacking it with units properly.

Replace botstate with a task pipeline?

Common functions in BotState like checking the build queue and training queue, supply/economy should be implemented in BotState, not individual subclasses.

Implement a profiler to find which functions need the most optimizing.

The bot thinks that buildings are completed immediately as soon as they are started building. onCreate only triggers when the building is created (begun), not completed.

It appears that a single worker can be assigned to build while building another building.

Make sure to count mineral miners and gas miners separately when saturating a base with AutoEconomy. May also want to move the building of workers out of JavaBot (into BaseManager?).

Make units continue to circle in the enemy base after reaching it.

Building placement algorithm may place buildings in locations that are unbuildable.