Scenario Builder: a nation's infrastructure is drafted once, for its first plan's theatres #46
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found while building the corpus (#7) on 2026-10-14.
What happens. A nation's order-of-battle entry is shared by every plan with that nation and year. The infrastructure section is one request, marked covered as
CIV:infrastructurefor the whole entry. The infrastructure task names the theatres of the plan that first asked for it.Russia's 2027 entry got its infrastructure while drafting the Sea of Japan plan. It holds Vladivostok and Khabarovsk airports, Vostochny and Zarubino ports, and a Vladivostok power plant. When the Norwegian Sea plan committed Russia's infrastructure, nothing was drafted: the chunk was already covered, so the Kola Peninsula got no ports, airports or power plants.
This is the same nation-wide-coverage problem PR #38 fixed for units:
oob_regionasks once per set of theatres, with aregion:coverage mark.Proposal. Draft infrastructure per region in the same way. Use a
region:CIV:infrastructure:<region_key>mark and a request naming the plan's own front and enemy-homeland theatres. Add the rows beside the earlier ones.Related, smaller. The
oob_regiontask's example row is a real Russian unit (689 GvIAP, Su-27SM3, Chkalovsk). The local model copied it into Finland's rows. It stayed unmapped, and review excluded it. The examples of every OOB task are real units, so a copy is possible in any of them. A check that drops a row identical to its task's example for another nation would catch it.