Steve Cotton ad1c42ca8f Make [store_reachable_locations]range=vision calculate vision
Previously it calculated max movement, and then added the adjacent hexes. This
version should correctly handle:
* units with vp different to max mp
* units with vision costs different to movement costs
* jamming by enemy units

Draft changelog entry for this:
* `[store_reachable_locations]range=vision` now calculates vision, instead of using movement costs and max movement points (issue #4179)
2021-04-16 02:05:42 +02:00
..

This directory contains both the scenarios used by C++ unit tests and those which are
WML unit tests.

For the C++ unit tests, it is recommended to reuse the same scenario file as much as possible
and just inject WML into it.
Injection can be done by adding a config object containing event code and then registering that
manually for game_events.

WML unit tests are self-contained scenario files to test a specific area of WML. They can be
implemented with the GENERIC_UNIT_TEST macro.