This adds 'log <severity> <comma-domain-list>' to change the log level
for one or more log domains without restarting the server, 'log precise
on/off' for changing the timestamp precision setting, and 'timings
on/off' for changing the request servicing timing reports setting.
It already didn't work anyway, but now it seems to be actively causing problems by randomly failing due to lack of disk space. Though how it can only sometimes run out of disk space despite trying to cache the same thing every time, and when the runner instance is supposed to always have the same amount of disk space available, is anyone's guess.
By default, the MAI removes movement points from units even when they cannot find a hex to move to. When this option is set to 'no' (default is 'yes'), this step is skipped, so that other candidate actions can take over.
This implements feature request #5580
In general, the units specified in the MAI setup should be on the AI side. However, that might change during a scenario, for example when there is an event that switches units to other sides.
In movetype::write, the children might not be created if that child has an
empty config; there might be no child at all for movetypes such as "none". The
movetype "none" is a real movetype defined in units.cfg for units that
shouldn't be able to move.
The original_cfg local variable was only used once anyway, removing it and the
comment made the code clearer.
This wasn't caught in the 1.15 testing, but with 1.14 it resulted in a
"mandatory WML child missing" warning.
This is preparation for backporting 0ba433203e, with the idea that both sets
of names will be supported in both branches.
No deprecation messages are added. While config::get_attribute_value() has a
config::get_old_attribute_value(), there isn't currently a similar utility for
config::child(); maybe I should add one now, but it feels too large a change
for a backport.
- get_terrain and set_terrain replaced with direct indexing operations
- get_map_size mostly replaced with either the iterator or an on_board call.
Only a few cases really needed to know the size of the map for some other purpose.
- shroud and fog operations, village owner, time areas, and location filters
- get_terrain_info replaced with terrain_types table
- Map generation functions create_map and create_filter
