And a remark that the keys listed are the default keys,
in case we allow the user to change them (via config file or UI) later.

We should probably use the same type for monsters, to have a number
with which to indicate a targeted monster. Monsters probably don't need
to carry their numbers in them, unlike heroes, because they don't get
moved to and from any "current monster" state field.

TODO: some actions should behave differently in look mode, e.g., movement

TODO: currently all but on hero must remain on level 1. Either hero switching
in look mode or via number keys will solve that.

Plus a few tweaks around.

I'll prepare a patch to differentiate numpad and top row number keys.

So it's now possible to move more than one hero to levels > 1.

TODO: perhaps make the options case sensitive; it costs too much debugging.

…omplete

Plus a bit of clean-up.

That's after I myself didn't remember what the components are used for.
Now it's documented in record field names.

This is short form of "player-controlled hero".
Other heroes and all heroes in general are just "heroes".

Exactly as proposed; minimal changes to get it working again.

I misuderstood how the action monad "abort" propagates through nested actions.

That's because we really want hero selection to be a purely UI distinction;
otherwise players will waste time micromanaging cycling among heroes before
the end of the turn.

Via a tmp hack, until the TODOs below playerCommand implemented.

…g score

Only heroes from the current level are taken into account, or leaving
one hero camping near the exit would be a too powerful tactics.

This is to to let the keys that request (more) information (help screen,
item list for dropping, etc.) toggle display of the obtained information off.
No two keys required ('?' and ' '), just tap '?' once, look, tap again.

The bug was wiping out savegame on every other save attempt. I've forgotten
to set case sensitivity in some of the places config is created. Affects only
my branch. With the new code it's much harder to make such a bug again.

TODO: it takes a turn and it shouldn't

Actually, they don't actively follow each other (no monster FOV, so they
can't see each other), but they always attack when adjacent, and not
only when bumping into each other by chance, as on levels with heroes.
To see this behaviour toggle look mode, change level and press '.'.

TODO: refactor the hero code

Now it does not reveal the location of the other end of stairs is look mode.

Plus some refactoring and hardening.

In the future we can plug in there some extra statistics,
character dump commands, etc.

Plus some cleanup and TODOs.

…o alive

In this way, we avoid the usual headaches with paths, OSes and permissions.
At startup it's always parsed, but a user config is used instead, if it exists.
TODO: throughout the code, lookup default values in the default config instead
of specifying them every time an option is queried. In this way, the various
game balance parameters are in sync and all in one place (the default config).
The user configs can be short and modify only some options, the rest is taken
from the default config. Diffs between user and default configs are easy.
The cost of all this is a bit of dynamic typing, and so runtime failures.
Can be limited by defining some types for sets of config parameters.

…g file

The default config file is now the only source of defaults and we get
an immediate runtime error if the sought option is not found in it
(nor in the main config file carried by the savegame, which may also contain
options from the user config file from the time the game was started).

Also rewritten the default config file to make diffing with dumps easier.

Previously, the current directory was chosen if no paths were given,
now it's only when the ~/.LambadaHack directory does not exist.

It's out of sync currently, because it erronously takes time,
so monsters can move away before the player reads the description.

TODO: targeting monsters gets broken as soon as monsters change numbers.

See sn issue on tracker with a similar title.

KISS above all.

Since cursor is a component of state, it should not be duplicated
as an explicit argument of Action functions that have access to state.

…, too

TODO: many minor points described in #34.

(I've just read how unfashionable foldl is and at a glance all the functions
are or should be strict, so changing it to foldr would not make sense.)

TODO: simplification and clean-up

No more duplication of the number inside the hero and in the index of the
intmap at which the hero is stored.

Plus lots of renames, layout fixes, various tiny tweaks.

…ast time)

Asymptotic complexity is the same: finding first monster to move is linear,
but previously inserting the monster back into the time-sorted list was linear.

TODO: when the fatigue stat is introduced, monster will be released quickly
TODO: I bet it crashes in cases like inventory management, etc.; review

(Was inaccurate, because there are discontinuities in numeration,
especially for monsters.)