By Joseph Luster

Veering off of our current timeline, developer Overseer Games’ Kaiserpunk takes aim at an alternate history that noticeably split from our reality after the end of World War I. This notion paves the way for a strategic city-builder that reimagines the world from 1918 to 1945 during a time known as the Interbellum Era.

Following the events of WWI, city-states rose from the ashes, pitting themselves against one another in an attempt to rule supreme. Kaiserpunk envisions war on a global scale as you attempt to rule your city through thoughtful management, industrial growth, and a focus on military expansion across land, air, and sea.

Every aspect of city building is at your disposal, giving you a chance to dig into the nitty gritty of everything from housing to public services, employment rates that impact the overall economy and the general well-being of public morale that will ensure your metropolis stays at the top. As you encounter other similarly ambitious city-states, it will be up to you whether or not you go for diplomacy and trade, or use them as a means to an end in your quest for total dominance.

All in all, Kaiserpunk offers 100 different regions to add to your list of potential conquests. Each aspect of civil and military management within is robust, including an impressive number of interconnected production chains that can scale to meet your burgeoning empire’s demands. All of the decisions made throughout have sizable heft to them, and will ultimately impact the way the rest of the world sees you and how successful you end up being on a global stage.

Kaiserpunk will be fully in your hands by the time this issue is on stands, but as of this writing we’re still a couple weeks away from final delivery. With inspiration taken from classics like Hearts of Iron and Civilization, the team at Overseer has a lot to live up to, but early looks into the grand strategy that awaits remain promising.

Publisher: Overseer Games, Elda Entertainment
Genre: Strategy
System: PC
Available: Now

Back to the issue this appears in