Polygons, corners, and edges are stored in flat, contiguous memory arrays (Structures of Arrays) rather than deeply nested object pointers. This change drastically reduces CPU cache misses during massive graph traversals.
world = mapgen.Map(seed=4242, size=(2048, 2048)) world.add_biome("temperate_forest", humidity=0.6, temp=0.5) world.generate() world.export("my_world.png", format="heightmap") mapgen v2.2
One of the most notable criticisms of procedural maps in gaming is the "erratic river syndrome," where water networks flow uphill, split unnaturally, or end abruptly in deserts. Mapgen v2.2 addresses this with an overhauled deterministic hydrology pipeline. Polygons, corners, and edges are stored in flat,
files and text coordinates. Mapgen v2.2 emerged as a "magic wand"—a tool designed to automate the generation of provinces, terrain, and supply zones. For a brief window, it was the gold standard for anyone wanting to build a "Total Conversion" mod, like a fantasy world or an alternate history timeline. The "Mapgen Curse" Mapgen v2
The story of Mapgen v2.2 is one of ambition, frustration, and the "old guard" of the Hearts of Iron IV (HoI4) modding community. The Rise of the Tool
Perhaps the most requested feature for years has been realistic hydrology. In previous versions, rivers were often drawn as simple wiggly lines ignoring topography.
One of the most lauded fixes in v2.2 is the corridor connection system. In earlier builds, hallways often dead-ended or crossed through rooms awkwardly. Version 2.2 implements a weighted A* pathfinder that respects "digging costs"—preferring to tunnel through dirt rather than stone, and avoiding pre-placed treasure rooms unless explicitly told to intersect. This yields dungeon layouts that feel intentional, not random.
