PWCG Historian

[ziher]

I'm making little app that takes some context from PWCG campaign and sends it to LLM. Any interest for something like this?
(requires Openrouter account/API key)


Briefing (after accepting mission in PWCG)

Debriefing (after submitting report in PWCG, gets written to PWCG journal)

Settings

 

Edited March 23 by ziher

[AcesDarthBubu]

Looks interesting. Does one needs to have to pay tokens to use the feature?

[ziher]

In theory you could use free models but they are usually heavily restricted. Price per call in my case is roughly $0.005 for Grok 4.2 which is on more expensive side, plenty of cheaper LLMs could handle it for ~$0.001 per call or less.

[Varibraun]

On 3/23/2026 at 7:18 PM, ziher said:

I'm making little app that takes some context from PWCG campaign and sends it to LLM. Any interest for something like this?
(requires Openrouter account/API key)

I agree that this looks interesting.  Since it appears that Pat is on a longer hiatus and unlikely to bring in the new aircraft and theaters for PWCG, do you think it would also work with @Arrow_1974's Campaign Tracker for the in-game campaign which I think is also downloading/reading mission logs and tracking squadron members?

[ziher]

It's just an 'atmosphere' app, could work with anything that has logs exposed. ATM it's only suitable for PWCG German bomber campaign, once i test it out properly and adapt to all nations/roles i'll post source code and compiled app. 
App was written almost entirely by Claude AI (free), so anyone could use Claude to modify it for their needs.

Edited March 26 by ziher

[Arrow_1974]

Since my campaign/career tracker was mentioned by @Varibraun, I would like to clarify a few points regarding how the data is sourced and interpreted:

Campaign tracking relies on the campaignsstates.txt file. This data provides overall campaign statistics, but it does not contain squadron-level information, only player related information.

Career tracking, on the other hand, is based on the cp.db database. This source is significantly more detailed and does include squadron information, allowing for a much richer and more accurate reconstruction of a pilot’s service record including his current (and former) squadron(s).

Regarding mission reports (*.mlg files located in the Flightlogs folder):
These files are first converted into readable .txt format and then parsed. Relevant events are extracted and used to generate the debriefing logs.

However, it is important to emphasize that mission reports should not be treated as 100% authoritative data. While they can provide valuable insights—and in some cases more granular detail—they still contain ambiguities and inconsistencies. For that reason, I consider them supporting data, rather than a definitive source.

That said, I am absolutely willing to support @ziher if needed. The mod creates some helper files (.json, .yaml) based on the available data that are then used to ‘feed’ the frontend (browser). At the moment, however, I have not fully understood the exact scope and objective of the mod. Something like you feed the mission reports into an LLM and it creates a “real” debriefing stories?  A brief explanation would be greatly appreciated.

Edited March 26 by Arrow_1974

[ziher]

Yes, basically that (asked claude to summarize since i'm not that great with english).

Exactly right. PWCG Historian is a small standalone Electron app that reads PWCG's campaign files directly (Campaign.json, MissionData, CombatReport, CampaignLog) and uses an LLM via OpenRouter to generate two things:

1. Pre-mission briefing — a historically grounded intelligence briefing for the date and mission, including a period newspaper excerpt, actual Eastern Front strategic situation, and how your specific mission fits into it, signed off by a plausible Luftwaffe officer.
2. Post-mission debrief — a first-person pilot journal entry that reflects actual mission outcomes (casualties, aircraft lost, awards from CampaignLog) plus optional freetext notes from the player. The narrative is written back into CombatReport.json so PWCG displays it in its own journal.

It also maintains a rolling career memory summary that gets updated each new mission and silently injected as context, so the LLM can reference past wounds, lost comrades, and the pilot's psychological arc over time.

Currently Luftwaffe/Moscow front focused but faction and theater selection is planned.

[Varibraun]

1 hour ago, Arrow_1974 said:

Something like you feed the mission reports into an LLM and it creates a “real” debriefing stories?  A brief explanation would be greatly appreciated.

Yes, @ziher answered above.  It seems like it will almost create a diary of sorts for both the pilot and the squadron. I asked AI "Gemini" about it regarding working with your Campaign Tracker and here is the summary (full answer in the spoiler): 

The IL-2 Campaign Tracker (v2.0) can be used with this AI to generate detailed, narrative histories, including squadron and individual pilot missions. By analyzing the tracker's PDF summaries, service records, and campaign files, the AI can construct chronological accounts of combat results, promotions, and awards. 

Workflow Example

1. Input Data: Mission 12: Pilot: Lt. Schmidt. Plane: Bf 109 G-2. Result: 2x La-5 destroyed, 1x Oil Leak. Location: Stalingrad.
2. LLM Output: "September 14, 1942: The air over Stalingrad was thick with smoke today as Lt. Schmidt led the swarm. Despite a desperate lunge from two Soviet La-5s, Schmidt's aim remained cold and precise, sending both spiraling into the Volga. He limped home with a severed oil line, the ground crew working through the night to patch the 'Black 1' for tomorrow's dawn sortie."

Spoiler

 

[ziher]

After mission reports get stored in the journal like this.