
Greetings, everyone!
To be perfectly transparent from the outset: we are not planning a rework for civil wars. My primary goal here is to better understand your experiences with this existing content—what resonates with you and what aspects feel lackluster or frustrating.
When you initiate a campaign with the intent of switching to a breakaway nation—such as forming a fascist UK or a Communist Japan—what steps do you take in the lead-up to the conflict?
To help guide your feedback, here are a few questions to consider:
- How would you describe the experience of progressing down those specific focus trees?
- Do you prioritize rushing toward the civil war, or do you prefer to complete generic branches first?
- What is your strategy for managing the military of your starting nation?
- How do you handle the industrial development of the original nation before the split?
- Which specific mechanics or limitations annoy you during these playthroughs?
- What elements make the civil war experience feel truly worthwhile or satisfying?
- Do you find these scenarios narratively or emotionally compelling, even when you know they leave your nation objectively weaker than a standard, stable route? If so, what draws you to them?
I look forward to reading your insights, as they will be invaluable for shaping our future content.
— pdx_berthier
Understanding the Distinction: Dev Diaries vs. Dev Corners
Most of you are likely familiar with our two primary formats for developer updates:
Developer Diaries
- Usually published as we approach a release date.
- Provide deep dives into content that is largely finalized and in the polishing phase.
- Packed with imagery, screenshots, and visual demonstrations.
- Offer a forum for your questions and help us catch any significant oversights before launch.
- Allow us time to implement quick fixes or plan adjustments for upcoming patches, hotfixes, or War Effort updates.
Developer Corners (like this post)
- Centered entirely on gathering your specific feedback.
- Designed to be concise and focused.
- May be light on visuals or contain no images at all.
- Highlight concepts that might influence future content, though nothing is promised or set in stone.
- Published spontaneously; these aren’t mapped out far in advance. If a developer needs community input, we reserve a weekly Tuesday or Thursday slot to reach out.