Request: Expanded Export Data
Posted: Wed Jan 14, 2026 8:10 pm
Commander's Report Export - Feature Requests
Hey all,
I've been working on a tool to dig into Commander's Report CSV exports - battle stats, unit tracking, air ops performance, that kind of thing. The exports are great, but I've hit some gaps where the data just isn't there or is ambiguous. Putting together a list in case the devs are looking at this stuff.
Roughly ordered by how useful it would be.
═══ THE BIG ONES ═══
1. Air Mission Altitude
Probably my #1 request. The altitude setting for air missions isn't exported anywhere I can find. The in-game combat log viewer shows it (so the data's in the save file), but it doesn't make it into the CSVs.
Altitude affects everything in air combat - engine performance, speed, whether your escorts can actually reach the bombers they're supposed to protect. Right now I can see "these fighters got shot down" but I can't tell if they were at 3000m while the bombers were cruising at 8000m. Hard to learn from mistakes without that info.
The game's master database files have an altTarget column, so the field exists. Would be great to have it in Air-Air Groups.csv or Air-AOG.csv.
2. What Equipment is Actually in a Unit
Unit-Main.csv gives us totals: 45 AFV, 12 guns, 8000 men. But which tanks? Which guns? Is that panzer division running Pz IVs or Pz IIIs? Can't tell.
Without this, it's hard to figure out actual combat capability, track which units need specific replacements, or spot units stuck with obsolete gear.
Could be a column like "PzKw IVG:12,PzKw IIIJ:8" or a separate Unit-Equipment.csv file.
3. Which Units Fought in Each Battle
The combat log shows equipment names like "Rifle Squad 43" or "7.5cm PaK 40" - not organizational units like "3rd Panzer Division" or "261st Rifle Division".
Right now I guess which units were involved based on hex position, but units move after combat so it's unreliable. Either:
- A parentUnit field in combat events, or
- A Battle-Participants.csv listing which units were in each battle
Same problem for air - I can parse "II./KG 1 breaks off" messages but not all groups break off, so I'm missing some participants. Which air groups actually flew in each battle would be useful.
4. Detected Enemy Units
This one's probably a bigger ask: export enemy unit positions. For games with FOW off, this would be all enemy units. For FOW games, only what's visible through recon/contact - respecting fog of war, not revealing hidden units.
I get why this might be tricky for PBEM or head-to-head play. But for single-player vs AI, being able to put enemy positions on a map overlay would be great for planning. Maybe export what the player can already see in-game, which varies based on FOW settings?
═══ WOULD REALLY HELP ═══
5. Weather Conditions on Battles
Weather isn't attached to battle or combat log data. When looking at a battle there's no way to know if it was clear skies, mud, or a blizzard.
- Mud wrecks armor and movement
- Blizzards hammer air ops
- Ground attack effectiveness drops hard in bad weather
Having weather zone or condition on battle records would explain a lot of "why did that go so badly?" moments. A weather column on Battle-Ground.csv and Battle-Air.csv would do it.
6. Terrain and Fort Level at Battle Hex
Same idea as weather - terrain and fortifications have huge effects on combat but aren't in the battle exports. Was that attack across a river? Into a city? Through a forest? Did the defender have level 3 forts?
The hex coordinates are there, but not the terrain type or fortification level. Knowing "this was a forest hex with level 2 forts" would help make sense of results that look wrong on paper. Fort level especially - the difference between no forts and level 4 is massive. Terrain and fort_level columns on the battle CSVs would help.
7. Which Weapon Fired
Combat log shows "Panzer IV fires at T-34" but not which weapon. The 75mm main gun or the coax MG? For anything with multiple weapons it's hard to figure out what's actually working at different ranges.
8. HQ Subordinate List
Units export their higher HQ, but HQs don't export who's under them. Building an OOB means querying every unit and grouping by hhq_name. A subordinates column on HQ records would be cleaner.
═══ NICE TO HAVE ═══
9. AFV Repair Stats by Vehicle Type
EventLog gives total repaired/scrapped counts but not by type. "Scrapped 15 Pz IIIs, 3 Pz IVs" would help spot which models have reliability problems.
10. Air Directive Details
Intensity slider value and detailed target priorities aren't fully exported. We get APri (2 or 4) but not the actual intensity setting or target breakdown.
11. Fatigue Source
We get fatigue percentage but not what caused it. Fatigue comes from movement, combat, disruption recovery, airdrops, and isolation - knowing the breakdown would help figure out why a unit is +exhausted and whether the cause is avoidable (e.g., routing through captured hexes vs. heavy fighting).
12. Supply Chain Info
Just unit supply percentages right now. Depot utilization, transport availability, route congestion - basically why a unit is low on supply, not just that it is.
13. Other Stuff
Lower priority but would be cool:
- Construction progress (is that airfield 50% done or 90%?)
- City control history (when did we take Smolensk?)
- Replacement routing (where are reinforcements coming from?)
- Pilot experience levels
That's the list. Commander's Report is already useful - these would just take it further for people who like digging into the numbers.
Hey all,
I've been working on a tool to dig into Commander's Report CSV exports - battle stats, unit tracking, air ops performance, that kind of thing. The exports are great, but I've hit some gaps where the data just isn't there or is ambiguous. Putting together a list in case the devs are looking at this stuff.
Roughly ordered by how useful it would be.
═══ THE BIG ONES ═══
1. Air Mission Altitude
Probably my #1 request. The altitude setting for air missions isn't exported anywhere I can find. The in-game combat log viewer shows it (so the data's in the save file), but it doesn't make it into the CSVs.
Altitude affects everything in air combat - engine performance, speed, whether your escorts can actually reach the bombers they're supposed to protect. Right now I can see "these fighters got shot down" but I can't tell if they were at 3000m while the bombers were cruising at 8000m. Hard to learn from mistakes without that info.
The game's master database files have an altTarget column, so the field exists. Would be great to have it in Air-Air Groups.csv or Air-AOG.csv.
2. What Equipment is Actually in a Unit
Unit-Main.csv gives us totals: 45 AFV, 12 guns, 8000 men. But which tanks? Which guns? Is that panzer division running Pz IVs or Pz IIIs? Can't tell.
Without this, it's hard to figure out actual combat capability, track which units need specific replacements, or spot units stuck with obsolete gear.
Could be a column like "PzKw IVG:12,PzKw IIIJ:8" or a separate Unit-Equipment.csv file.
3. Which Units Fought in Each Battle
The combat log shows equipment names like "Rifle Squad 43" or "7.5cm PaK 40" - not organizational units like "3rd Panzer Division" or "261st Rifle Division".
Right now I guess which units were involved based on hex position, but units move after combat so it's unreliable. Either:
- A parentUnit field in combat events, or
- A Battle-Participants.csv listing which units were in each battle
Same problem for air - I can parse "II./KG 1 breaks off" messages but not all groups break off, so I'm missing some participants. Which air groups actually flew in each battle would be useful.
4. Detected Enemy Units
This one's probably a bigger ask: export enemy unit positions. For games with FOW off, this would be all enemy units. For FOW games, only what's visible through recon/contact - respecting fog of war, not revealing hidden units.
I get why this might be tricky for PBEM or head-to-head play. But for single-player vs AI, being able to put enemy positions on a map overlay would be great for planning. Maybe export what the player can already see in-game, which varies based on FOW settings?
═══ WOULD REALLY HELP ═══
5. Weather Conditions on Battles
Weather isn't attached to battle or combat log data. When looking at a battle there's no way to know if it was clear skies, mud, or a blizzard.
- Mud wrecks armor and movement
- Blizzards hammer air ops
- Ground attack effectiveness drops hard in bad weather
Having weather zone or condition on battle records would explain a lot of "why did that go so badly?" moments. A weather column on Battle-Ground.csv and Battle-Air.csv would do it.
6. Terrain and Fort Level at Battle Hex
Same idea as weather - terrain and fortifications have huge effects on combat but aren't in the battle exports. Was that attack across a river? Into a city? Through a forest? Did the defender have level 3 forts?
The hex coordinates are there, but not the terrain type or fortification level. Knowing "this was a forest hex with level 2 forts" would help make sense of results that look wrong on paper. Fort level especially - the difference between no forts and level 4 is massive. Terrain and fort_level columns on the battle CSVs would help.
7. Which Weapon Fired
Combat log shows "Panzer IV fires at T-34" but not which weapon. The 75mm main gun or the coax MG? For anything with multiple weapons it's hard to figure out what's actually working at different ranges.
8. HQ Subordinate List
Units export their higher HQ, but HQs don't export who's under them. Building an OOB means querying every unit and grouping by hhq_name. A subordinates column on HQ records would be cleaner.
═══ NICE TO HAVE ═══
9. AFV Repair Stats by Vehicle Type
EventLog gives total repaired/scrapped counts but not by type. "Scrapped 15 Pz IIIs, 3 Pz IVs" would help spot which models have reliability problems.
10. Air Directive Details
Intensity slider value and detailed target priorities aren't fully exported. We get APri (2 or 4) but not the actual intensity setting or target breakdown.
11. Fatigue Source
We get fatigue percentage but not what caused it. Fatigue comes from movement, combat, disruption recovery, airdrops, and isolation - knowing the breakdown would help figure out why a unit is +exhausted and whether the cause is avoidable (e.g., routing through captured hexes vs. heavy fighting).
12. Supply Chain Info
Just unit supply percentages right now. Depot utilization, transport availability, route congestion - basically why a unit is low on supply, not just that it is.
13. Other Stuff
Lower priority but would be cool:
- Construction progress (is that airfield 50% done or 90%?)
- City control history (when did we take Smolensk?)
- Replacement routing (where are reinforcements coming from?)
- Pilot experience levels
That's the list. Commander's Report is already useful - these would just take it further for people who like digging into the numbers.