A comment from the code:

# TODO-remove - this is a temporary flow, used by the trainer worker, duplicated from observe() - need to create
#               an external trainer flow reusing the existing flow and methods [e.g. observe(), step(), act()]

It appears that this code is related to, if not the cause of, quite a bit of complexity and duplicate code in the training control flow

Add a game_speed configuration setting to bwapi.ini, and make BWAPI use this setting to set the Game Speed drop-down in the game lobby, e.g. game_speed = FASTEST. Otherwise, the game speed will be set to whatever game speed was picked from the drop-down in a previous game on the machine that is hosting the game, which may lead to confusing results if you're not aware of this. If a ``

As pointed out in TorchCraft/TorchCraft#299 : if you follow the setup instructions in
https://github.com/TorchCraft/TorchCraft/blob/develop/docs/starcraft_in_windows.md for using BWEnv.exe, you are instructed to click "Start" but the indication that everything is working correctly is the game freezing, which is surprising.

It may be helpful to have pages dedicated to the more commonly used classes (for example: game_state, unit, units etc) where the tables of applicable properties, methods etc can be found. I often find myself searching for properties / attributes or using trial and error to see if something will work, e.g. .position is a property of .unit and not .units.

Sometimes it is useful to slow down the game and look at the decisions the bot is making however the game is always really fast.
Probably we should make a configurable gamespeed parameter in BotConfig.txt similar to the original game (i.e. fast, very fast).

Currently I don't know how that should be done in a proper way. The following approach works for me:

    while (coordinator.Updat

It's almost ready, but few things needed to be done:

• remove SHIELDBATTERY_PATH mention
• add an example of couple of different developer workflows
• rework project structure a bit
• edit redis description a bit (eg. windows installer starts the service automatically)
• node > 7.6.0
• contributing guide
• generating map thumbnails in local dev
• ~~remove setting up initi

May warrant some discussion.

The tutorial instructions should be improved cause now it is not really clear how to build it.

At least the following should be added:

• Launch under Linux (set proper env variables).
• Minimal set of steps required for compilation of the tutorial.

Current:

[6:40:53 PM] -- Ribose joined the channel using Warcraft III The Frozen Throne.

Proposed:

[6:40:53 PM] -- Ribose joined the channel; 391ms, Warcraft III The Frozen Throne