Add a short "Guide"/"How to play" section describing UI, basic game mechanics, agent types, effects, and abilities.

Use images and GIFs.

Check WarbitsManual.pdf as an example of a good guide.

Related to #420 ("Clarify how movement limits work")

А то у меня только картинки в обзорной секции-то. Надо написать хоть пару слов про туман войны, влияние местности, реакционный огонь, систему морали и т.п.

Right now I have some pictures only in "Overview" section. I need to add some words about fog of war, terrain, reaction fire, morale, etc.

For now this is purely for local games, not networked.

• Map selection
• Number of players
• Team setup

There could be new starting positions for realms. Ancient could start in middle of the galaxy and rest of the realms from outside of the galaxy.

Could be useful to have a benchmark to measure how many events can be fired per second.

We could think of running one bench with only DummyEvent and another bench with StartRound and EndRound in sequence.

Keep in mind all events end up in the in-memory timeline and we shouldn't allocate too much for a benchmark.

The main map should react to zoom and increase/decrease the part of the world map that it displays (with the transformation anchor as the current mouse pointer/the center of the map) within some reasonable values. The zoom should either react on the scrool wheel of the mouse or a setting in the preferences (maybe in percent of the natural size).

Per dialyzer:

nuk_user_session.erl:30: Invalid type specification for function nuk_user_session:new/0. The success typing is () -> #{'user':=#{}, 'username':='anonymous'}

Indeed, the opaque session() type defines username => string(), and we are setting an atom.

Right now the player can bring his whole faction to a combat mission. Instead we should allow him to add eight characters to a squad which will then be used when loading the combat mission.

Allowing blueprints to export themselves as a single function decreases the friction of development.

Use case:

Blueprint = function(...) {
}

Internally:

if (typeof Blueprint === 'function')
  Blueprint = { name: Blueprint.name,  in: Blueprint }

As mentioned in #35, it would be nice to have a circleci build alongside Travis. It doesn't have to handle code coverage, just compile and test the project.