DEVELOPMENT PLAN #111 — Scars of Street Fighting: Battle Damage and Recovery in Town
- Thursday, November 19 2026
- Contributed by: Takeshi Miyaoka
- Views: 18
This is a plan article introducing something I would like to develop. Nothing described here is implemented yet; the ideas are still under consideration and may change before they are built.
Tonight's plan connects damage to the ground battles that are now fought on the city map. Today, when squads trade fire across the town's hexes, only troops and organization are lost; workshops, homes and roads come through untouched. I would like fighting to break the facilities in the hexes where it happens, cost residents' lives, block roads with rubble, and leave repairs to be made in workshops afterward. The aim is to give the layout of a town real weight for its defense. It is registered as improvement item WLD-024 (battle damage on the city map and recovery afterward).
A town battle today (an actual screen from the Debug build, the Ground defense view of Province Information). Around the castle of a regional capital, attacking squads under red flags and defenders under blue flags exchange fire, and the share of troops lost (−15% and so on) floats above them. The orange lines are the entry paths to the castle, and the bottom row lists each route's combat width and breakthrough count. The homes and facilities around them come through the fight untouched.
Where things stand: battles move across the town's hexesAs of today, the city map (improvement item WLD-019) exists for every land province you own and opens from the province information screen. When a ground battle happens in a province with a city map, it is fought on those hexes.
- Attackers have one entry route (attack route) per path leading to a gate; they enter from the edge of the map and head for the castle. Defenders take positions starting near the castle.
- Every hour, each squad moves one hex and fires on the adjacent enemy squad with the fewest troops. A squad fired on from two or more directions loses defense (15% per extra direction, down to half), and attackers who reach an undefended castle move toward a breakthrough.
- This evening's update (UI-088) draws squads as figures by arm and state, shows muzzle flashes, arrows, mortar shells and the sparks of close combat, and floats the share of troops lost. A squad that is wiped out leaves fallen soldiers or a broken vehicle on its hex, and the Logistics view turns roads through hexes in combat into red dotted lines with a stopped wagon.
Meanwhile, the game already has broken facilities repaired in workshops (used by riots, disasters such as earthquakes, and sabotage against air defenses, with repair costs charged to the budget) and a ledger that subtracts people lost to war and disaster from the population. Ground battles, however, feed neither of them.
What is missing: battles leave nothing behindThe fallen soldiers and wrecks after a battle are only drawn on the screen. Workshop output, the people in the homes and how easily roads can be crossed are all the same as before the fight. So it makes no difference whether you line workshops and homes along the attackers' path or tuck them deep inside the walls. Automatic placement already follows a rule that prefers spots away from the routes into the castle, but the player has no way to see why that matters.
The plan: count war damage and turn it into losses- Recording war damage: in each hour's exchange of fire, the troops a squad loses would be counted as "war damage" on the hex where it stood. Mortar shells, which wreck their surroundings more, would count double.
- Facilities: once, when the battle ends, every 40 points of war damage puts one facility on that hex out of order. As with riots and disasters today, no more than 95% of a facility type can be out of order, and repairs use the existing system (5 workshop-days per facility, plus its cost).
- Housing: every 10 points of war damage records one resident lost in the population ledger, with the cause "street fighting". A housing hex stands for 100 people, so one hex loses at most 20.
- Roads, gates and bridges: at 80 points or more they become rubble, which raises the effort of crossing that hex in the logistics and living calculations from 1 to 4 (the same as forest). Clearing takes 2 workshop-days and comes before facility repairs.
- While a province is occupied, neither repairs nor clearing progress; they resume once it is retaken.
Damage would be applied only once, at the end of the battle, under a fixed ID built from the battle and the hex, so saving and reloading never counts it twice. Nothing about the city map or damage would be recalculated in the daily midnight economy processing. The numbers (40, 10, 80, double, 20 people) are a first proposal, to be set while watching how much damage a test battle produces.
Concept mock (plan under consideration). The town after attackers pushed from the east gate to the castle, seen in the Ground defense view. Gray hatching marks the road and gate turned to rubble; the workshop with the red crack (3 state-owned) took 96 war damage and has 2 out of order; the numbers on homes are residents lost. The panel on the right sums up the damage to the town and the order of recovery. Names and numbers are illustrative, and this is not a game screen (the building art is the game's city map images).
The plan: show where fighting is likely before it startsIf damage matters, you should be able to see it coming before you build. Today's Ground defense view already draws the entry paths to the castle and the gates, and lists the number of entry routes with each route's combat width and breakthrough count (image 1). I would like to add a "likely battlefield" mark to facilities and homes on or next to those paths, and show a forecast when you consider moving one. The paths would come straight from the entry-route calculation that battles already use.
Concept mock (plan under consideration). The same town before the battle: the red bands are the two entry paths to the castle (lines the current view also draws), and orange outlines are the planned "likely battlefield" marks. The bottom of the panel shows the forecast for moving the workshop to the clearing west, inside the walls. Names and numbers are illustrative.
In the mock town, the workshop just inside the east gate is only 1 from the gate, which makes shipping easy, but it sits right next to an entry path. Moving it to the western clearing inside the walls takes it out of the fighting, but the cost to the nearest gate rises to 5 (the market stays at 4). I would like layout to become a choice between easy shipping and readiness for battle. It also combines with the choice from plan #109: more gates are convenient but give attackers more ways in.
Implementation steps and links to other systems- Record war damage per hex inside the battle state, unchanged across save and reload.
- Turn it into broken facilities, ledger entries and rubble once, at the end of the battle, without double counting.
- Run clearing and repairs on the existing repair system for workshop allocation and costs, and recalculate logistics and living effects only when clearing finishes.
- Display the "likely battlefield" marks and relocation forecasts before a battle, and the damage marks and the "Damage to this city" panel after it. The marks are drawn by the program; no new images are made.
- AI nations: recheck the current automatic placement rule (prefer spots away from the routes) against the amount of damage.
Work on this would start once battles on the city map (WLD-019) are settled. Bombing from the air, food in a long-besieged town and people who lose their homes are left out for now, so that they can later be connected to the same damage system.
Tell us what you thinkDoes clearing rubble and repairing broken workshops after a battle in town sound like fun to play, or like extra chores? I would also like to hear what you think of seeing likely battlefields in advance, and of choosing between easy shipping and a well-protected layout.
About the imagesImage 1 is an actual game screen, captured by starting the Debug build without showing its window and setting up a test formation for a town battle in a game started from the initial master (no player save was used). Images 2 and 3 are mock-ups to explain the plan, not game screens. The building and soldier art is the game's city map images; the rubble, damage and battlefield marks were drawn for the mock-up.
Related articles: DEVELOPMENT SNAPSHOT #110 — From Plan #109 to the Game: The Capital City Map, DEVELOPMENT PLAN #109 — A Town Inside the Regional Capital: Hex Streets and Gates, DEVELOPMENT PLAN #97 — Breaking the Air-Defense Net from Within: Sabotage and Ammunition Stores
Check the files currently available and the development status on the downloads page
