## Table of Contents

I wanted to generate interesting game maps that weren’t constrained to be realistic, and I wanted to try some techniques I hadn’t tried before. I usually make tile maps but instead used a different structure. What could I do with 1,000 polygons instead of 1,000,000 tiles? The distinct player-recognizable areas might be useful for gameplay: locations of towns, places to quest, territory to conquer or settle, landmarks, pathfinding waypoints, difficulty zones, etc. I generated maps with polygons, then rasterized them into tile maps that looked like this:

Most procedural map generators, including some of my own previous projects, use noise functions (midpoint displacement, fractal, diamond-square, perlin noise, etc.) to generate a height map. I did not do that here. Instead, I used a **graph structure** to model the things directed by gameplay constraints (elevation, roads, river flow, quest locations, monster types) and **noise functions** to model the variety not constrained by gameplay (coastline shape, river placement, tree placement).

There were three main things I wanted for this project: good coastlines, mountains, and rivers. For the coastline, I wanted to make island maps that are surrounded by ocean, so that I don’t have to deal with people walking to the edge of the map. For the mountains, I started with something simple: mountains are whatever’s farthest from the coastline, so that you can always walk uphill to reach the top. For the rivers, I started with something simple: draw rivers from the coast to the mountains, so that you can always follow rivers down to the beach.

First, **try the demo!** (Flash) Read on to learn how it works, or get the source code. Here’s the overview of the process:

Every project will have its own gameplay constraints. For this project, the gameplay constraints were partially taken from Realm of the Mad God, a multiplayer RPG in which players start on the beach playing alone and then later join together on the mountaintop to fight bosses. Elevation directly corresponds to difficulty, and must monotonically increase, so that was a key constraint in the design. Elevation in Minecraft on the other hand isn’t constrained the same way, so the noise function they use works for that game. In multiplayer Age of Empires, the location of resources is constrained by the need to be somewhat balanced among the players; in Minecraft the distribution of resources is not constrained. When writing your own map generator, think about what which aspects of your map are set by the design and which can vary from map to map. Each of the ideas on this page can be used separately or together in your own map generator project.

The first step is to generate some polygons. The simplest approach would be to use a hexagonal grid and perturb it a bit to make it look irregular. This works (and the techniques on this page will work if you use a perturbed grid), but I wanted something even less regular than that, so I picked random points and generated Voronoi polygons, which are used for lots of things, including maps. The Voronoi wiki is incomplete but has some useful background. I’m using nodename’s as3delaunay library, which has an implementation of Fortune’s Algorithm.

Here’s an example of random dots (red) and the polygons that result:

The polygon shapes and sizes are a bit irregular. Random numbers are more “clumpy” than what people expect. I want something closer to semi-random “blue noise”, or quasirandomness, not random points. I approximate that by using a variant of Lloyd relaxation, which is a fairly simple tweak to the random point locations to make them more evenly distributed. Lloyd relaxation replaces each point by the centroid of the polygon. In my code I merely average the corners (see `improveRandomPoints`

). Here’s the result after running approximate Lloyd relaxation twice:

Compare it to running once or fifty times. The more iterations, the more regular the polygons get. Running it twice gives me good results but every game will vary in its needs.

Polygon sizes are improved by moving polygon centers. The same approach works to improve edge lengths. Moving corners by averaging the nearby centers produces more uniform edge lengths, although it occasionally worsens the polygon sizes. In the code, see the `improveCorners`

function. However, moving corners will lose the Voronoi diagram properties. Those properties aren’t used in this map generator, but keep this in mind if you want to use those properties in a game. You can either get better edge lengths or you can preserve the Voronoi distance properties.

Using Voronoi adds some complexity so if you want to start with something simpler, try a square or hexagonal grid (you can see this in the demo). The rest of the techniques in this article will work with a grid. Optionally, randomly perturb the vertices of the grid to make it a little more natural looking.

I’m representing the map as two related graphs: nodes and edges. The first graph has nodes for each polygon and edges between adjacent polygons. It represents the Delaunay triangulation, which is useful for anything involving adjacency (such as pathfinding). The second graph has nodes for each polygon *corner* and edges between corners. It contains the shapes of the Voronoi polygons. It’s useful for anything involving the shapes (such as rendering borders).

The two graphs are related. Every triangle in the Delaunay triangulation corresponds to a polygon corner in the Voronoi diagram. Every polygon in the Voronoi diagram corresponds to a corner of a Delaunay triangle. Every edge in the Delaunay graph corresponds to an edge in the Voronoi graph. You can see this in the following diagram:

Polygon `A`

and `B`

are adjacent to each other, so there is a (red) edge between `A`

and `B`

in the adjacency graph. For them to be adjacent there must be a polygon edge between them. The (blue) polygon edge connects corners `1`

and `2`

in the Voronoi shape graph. *Every* edge in the adjacency graph corresponds to exactly one edge in the shape graph.

In the Delaunay triangulation, triangle `A`

-`B`

-`C`

connects the three polygons, and can be represented by corner `2`

. Thus, corners in the Delaunay triangulation are polygons in the Voronoi diagram, and vice versa. Here’s a larger example showing the relationship, with Voronoi polygon centers in red and corners in blue, and the Voronoi edges in white and the Delaunay triangulation in black:

This duality means that I can represent the two graphs together. There are several approaches for combining the data from the two graphs. In particular, edges can be shared. Each edge in a normal graph points to two nodes. Instead of representing two edges in the two graph separately, I made edges point to *four* nodes: two polygon centers and two corners. It turns out to be quite useful to connect the two graphs together.

With the combined representation, I can now use the Relationships Between Grid Parts sections of my article on grids. They’re not grids so I’m not assigning grid coordinates, but many of the algorithms that work on grids also work here, and the algorithms that work on graphs also work here (on either of the two graphs).

In the code, the `graph/`

directory has three classes: `Center`

, `Corner`

, and `Edge`

:

`Center.neighbors`

is a set of adjacent polygons`Center.borders`

is a set of bordering edges`Center.corners`

is a set of polygon corners`Edge.d0`

and`Edge.d1`

are the polygons connected by the Delaunay edge`Edge.v0`

and`Edge.v1`

are the corners connected by the Voronoi edge`Corner.touches`

is a set of polygons touching this corner`Corner.protrudes`

is a set of edges touching the corner`Corner.adjacent`

is a set of corners connected to this one

The second step is to draw the coastline. The borders of the map need to be water, but you can mark the other polygons as either water or land, using any approach you want. The coastline is then all the edges where land and water meet.

Here’s an example that divides the world into land and water:

In the code, `Map.as`

contains the core map generation code. The `IslandFunction`

returns `True`

if a position is land, and `False`

for water. There are four island functions included in the demo:

`Radial`

uses sine waves to produce a round island`Perlin`

uses Perlin noise to control the shape`Square`

fills the entire map with land`Blob`

draws my blob logo

You can use any shape, (even pizza box stains). In a future version of this project I hope to add a drawing tool to let you draw your own shapes.

The code assigns water/land to both polygon centers and corners:

- Assign water/land to the
*corners*by setting`Corner.water`

based on the`IslandFunction`

. - Assign water/land to the
*polygons*by setting`Center.water`

if some fraction of the corners have`water`

set.

A simple flood fill starting from the border of the map can determine which water areas are oceans (connected to the border) and lakes (surrounded by land):

In the code, the flood fill runs on the polygon centers, and then we can decide what happens to corners:

- Set
`Center.ocean`

for any polygon connected to the borders of the map through water polygons. If`Center.water`

is set but`.ocean`

is not, then it’s a lake. - Set
`Center.coast`

if the polygon is land but has an ocean border. Coastal areas will later get drawn as beaches. - Set
`Corner.ocean`

if the corner is surrounded by ocean polygons. - Set
`Corner.coast`

if the corner touches ocean and land polygons. - Reset
`Corner.water`

to be consistent with the surrounding area.

The most realistic approach would have been to define elevation first, and then define the coastline to be where the elevation reaches sea level. Instead, I’m starting with the goal, which is a good coastline, and working backwards from there. I set elevation to be the **distance from the coast**. I originally tried elevations at polygon centers but setting elevations at corners worked out better. Corner-to-corner edges can serve as ridges and valleys. After calculating the elevation of corners (`Corner.elevation`

), the polygon elevation (`Center.elevation`

) is the average of the elevation at the corners. See the functions `Map.assignCornerElevations`

and `Map.assignPolygonElevations`

.

Water polygons don’t count towards the distance. This is both because I expect lakes to be flat instead of sloped, and because this tends to build valleys around lakes, which helps guide rivers towards lakes.

One problem with the simple definition is that some islands have too many mountains and others have too few. To fix this, I redistribute the elevations to match a desired distribution, which has more low elevation land (coastline) than high elevation land (mountains). First, I sort the corners by elevation, and then I reset the elevation `x`

of each to match the inverse of the desired cumulative distribution: `y(x) = 1 - (1-x)^2`

. In the `Map.redistributeElevations`

function, `y`

is the position in the sorted list, and `x`

is the desired elevation. Using the quadratic formula, I can solve for `x`

. This preserves ordering so that elevations always increase from the coast to the mountains.

For any location, going downhill will eventually lead to the ocean. This diagram shows the steepest downhill direction from every corner, stored in `Corner.downslope`

:

By following the downhill arrows from any location, we eventually reach the ocean. This will be useful for rivers but may also be useful for calculating watersheds and other features.

I had two main goals for elevation:

**Biome**types: high elevations get snow, rock, tundra; medium elevations get shrubs, deserts, forests, and grassland; low elevations get rain forests, grassland, and beaches.**Rivers**flow from high elevations down to the coast. Having elevations that always increase away from the coast means that there’s no local minima that complicate river generation.

In addition, games may define their own use of elevation data. For example, Realm of the Mad God uses elevation to distribute monsters.

This elevation calculation works for simple islands, which is what I needed for Realm of the Mad God. For continent generation, you’ll want to change this step to generate one or more mountain ranges that aren’t necessarily in the center, as well as isolated volcanos.

Rivers and lakes are the two fresh water features I wanted. The most realistic approach would be to define moisture with wind, clouds, humidity, and rainfall, and then define the rivers and lakes based on where it rains. Instead, I’m starting with the goal, which is good rivers, and working backwards from there.

The island shape determines which areas are water and which are land. Lakes are water polygons that aren’t oceans.

Rivers use the downhill directions shown earlier. I choose random corner locations in the mountains, and then follow the `Corner.downslope`

path down to the ocean. The rivers flow from corner to corner:

I tried both polygon centers and corners, but found that the corner graph made for much nicer looking rivers. Also, by keeping lakes flat, elevation tends to be lower near lakes, so rivers naturally flow into and out of lakes. Multiple rivers can share the lower portion of their path. Every time a river flows through an edge, I increase the water volume stored in `Edge.river`

by 1. At rendering time, the river width is the square root of the volume. This approach is simple and works well.

Since I’m working backwards, I don’t need moisture to form rivers. However, moisture would be useful for defining **biomes** (deserts, swamps, forests, etc.). Since rivers and lakes should form in areas with high moisture, I defined moisture to decrease as **distance from fresh water** increases. `Corner.moisture`

is set to `a^k`

for some `a`

< 1 (e.g. 0.95), and `k`

being the distance. There are unfortunately some tuning parameters in `Map.assignCornerMoisture`

that I tweaked until the maps looked reasonable:

As with elevation, I redistribute moisture to match a desired distribution. In this case, I want roughly equal numbers of dry and wet regions. The desired cumulative distribution is `y(x) = x`

, so the redistribution code is very simple. I sort by moisture and then assign the moisture of each corner to that corner’s position in the sorted list. See `Map.redistributeMoisture`

for the code.

In this map generator, moisture is only used for biomes. However, games may find other uses for the moisture data. For example, Realm of the Mad God uses moisture and elevation to distribute vegetation and monsters.

Together, elevation and moisture provide a good amount of variety to define biome types. I use elevation as a proxy for temperature. If this were a continent generator, latitude might be a contributor to temperature. Also, wind, evaporation, and rain shadows might be useful for transporting moisture as humidity. However, for this generator I kept it simple. Biomes first depend on whether it’s water or land:

`OCEAN`

is any water polygon connected to the map border`LAKE`

is any water polygon not connected to the map border, or`ICE`

lake if the lake is at high elevation (low temperature), or`MARSH`

if it’s at low elevation`BEACH`

is any land polygon next to an ocean

For all land polygons, I started with the Whittaker diagram and adapted it to my needs:

Elevation Zone | Moisture Zone | |||||
---|---|---|---|---|---|---|

6 (wet) | 5 | 4 | 3 | 2 | 1 (dry) | |

4 (high) | `SNOW` | `TUNDRA` | `BARE` | `SCORCHED` | ||

3 | `TAIGA` | `SHRUBLAND` | `TEMPERATE DESERT` | |||

2 | `TEMPERATE RAIN FOREST` | `TEMPERATE DECIDUOUS FOREST` | `GRASSLAND` | `TEMPERATE DESERT` | ||

1 (low) | `TROPICAL RAIN FOREST` | `TROPICAL SEASONAL FOREST` | `GRASSLAND` | `SUBTROPICAL DESERT` |

Here’s the result:

These biomes look good in the map generation demo, but each game will have its own needs. Realm of the Mad God for example ignores these biomes and uses its own (based on elevation and moisture).

For some games, the polygonal maps are sufficient. However, in other games I want to hide the polygon structure. The main way I do that is to replace the polygon borders with a noisy line. Why would I want a polygon structure if I’m just going to hide it? I think game mechanics and pathfinding benefit from the underlying structure.

Recall from earlier that there are *two* graphs: one for Voronoi corners (`1`

, `2`

in the diagram below) and edges (blue lines), and one for polycon centers (`A`

, `B`

) and Delaunay edges (red lines) between them:

I wanted to make both types of line noisy without making them cross lines from other polygons. I also wanted to make them as noisy as feasible. I realized that points `A`

, `1`

, `B`

, and `2`

form a quadrilateral, and I could constrain the wanderings of the line segment to that quadrilateral:

I further divided the quadrilateral into four quadrilaterals. Two were usable for the red (Delaunay) edge and two for the blue (Voronoi) edge. As long as the lines stayed within their allocated space and met in the center, they’d never cross each other. That takes care of constraining them. Note that the quadrilateral may not be convex; to divide it properly, I divide it at the midpoint of the Voronoi edge instead of at the intersection of the Voronoi and Delaunay edges.

The entire map can be divided up into these quadrilateral regions, with no space left over:

That ensures that the noisy lines aren’t constrained any more than necessary. (I wonder if these quadrilaterals would be useful for game mechanics.)

I can use any noisy line algorithm that fits within these constraints. I decided to subdivide the quadrilaterals recursively and stitch line segments together within the small quadrilaterals into a complete edge. The algorithm is in `NoisyEdges.as`

, in `buildNoisyLineSegments`

. The result is that the polygon edges are no longer straight:

There are three places to tune the noisiness:

- The recursive function ends when the segments are shorter than some length. I have examples at segment size 7, segment size 4, and segment size 1. In the map demo I use segment size 1 for rivers and coastlines, 3 where biomes meet, and 10 elsewhere.
- There’s a tradeoff between how much of the space goes to the red quadrilaterals (Delaunay edges) and blue quadrilaterals (Voronoi edges). I set
`NoisyEdges.NOISY_LINE_TRADEOFF`

to 0.5. - There’s a range of random numbers in
`NoisyEdges.subdivide`

. In the current demo it’s from 0.2-0.8, but it can be up to 0.0–1.0. Also, the random numbers don’t have to be linearly chosen. More visual noise results if you avoid the space around 0.5.

Noisy edges turn out to have a large impact on the map appearance, especially for rivers and coastlines.

I’m generally a fan of noise in game art, and wanted to add a little bit of noise to these maps as well. In a real game map the noise might reflect vegetation or small variations in terrain. In the demo (`mapgen2.as`

) I just filled the screen with a random noise texture by adding a noise bitmap on top. I also smoothed the borders between adjacent polygons by blending the colors in stages:

Here’s a rendering with 16,000 polygons, noisy edges, a noise texture overlay, and simple lighting:

A different way of blending the biomes at polygon boundaries is to build gradients using the elevation and moisture at each *corner*, and then assigning biomes per pixel:

If the game doesn’t need an entire polygon to be the same biome, this approach can be useful for making more interesting boundaries.

Another way to make the map look less polygon-like is to distort the elevation and moisture maps:

- Add Perlin or random noise to the elevation and moisture at each pixel.
- Sample nearby points using Perlin or random noise to change the coordinate.

Here’s an example of what this can do:

Adding noise to the elevation and moisture will produce “dithering” in the zones near transitions. Sampling nearby points using noise will distort the shapes of the boundaries.

I’ve placed the Actionscript source under the MIT license; it’s available on github. If you can read Java or Javascript, I think you’ll have no trouble reading the Actionscript. I don’t expect that the code will be immediately useful to anyone, but it might be a useful starting point if you’d like to use these techniques for making your own game maps.

`Map.as`

is the core map generation system`graph/*.as`

is the representation of graphs (polygons, edges, corners)`mapgen2.as`

is the demo, with rendering and GUI`Roads.as`

is a module adding roads along contour lines`Lava.as`

is a module adding lava fissures to high elevation edges`NoisyEdges.as`

is used by the demo to build noisy edges

The diagrams on this page are built with 300 polygons, the demo uses 2000 by default, and allows up to 8000. Some of the code for producing diagrams isn’t checked in because it was quick and dirty code only for the diagrams on this page, and not generally useful.

If you find the code or ideas useful, I’d love to hear about it!

- Jeff Terrace has contributed patches and also wrote a utility to convert the XML into COLLADA, as well as a COLLADA viewer in WebGL.
- Alex Schröder has been working on a Perl version that generates SVG output.
- Christopher Garrett has written a Voronoi/Delaunay port for iOS.
- Adam Martin maintains a Voronoi/Delaunay port for Unity, forked from Julian Ceipek’s port.
- Christophe Guebert has written a Java+Processing version.
- Baran Kahyaoglu has written a C#/ .NET version (source), and abhimir has a Unity version of Chris Herborth’s version of Baran’s code.
- Richard Janicek has a Haxe version that compiles to Javascript+Canvas, with a demo, and also a Javascript version, with a demo.
- Егор Харват has a Haxe/NME version.
- Connor Clark has a Java version.
- PolyWorld is based on Connor Clark’s Java code, and is now part of the Terasology game (watch this video).
- Miguel Cepero of Voxel Farm was inspired to make a political landscape map using Voronoi regions.
- Christophe Le Besnerais has a Javascript version that has a more advanced water flow model; luckylooke has a version of it for Phaser.io.
- Kylepixel has a Javascript project that also uses Voronoi regions for map generation.
- Conquest uses these techniques to make some of their game maps.
- Nuclear Horse Studios has a C#/Unity version (MIT license).
- Besiege uses these techniques for their procedural map generator.
- Stafford Williams also has a C#/Unity version (MIT license).
- Gareth Higgins has a C# map generator.
- Martín Candela Calabuig has a C++ version.
- Tobias is working on a C++ version
- Spencer Judge has C++ code for a map generator using these techniques.
- BitAlchemists has a Dart version
- Andy Gainey experimented with Voronoi diagrams on a sphere and decided to instead build a map with subdivided isocahedrons, with tectonic plates, air currents, temperature, moisture, and biomes. Several people asked me how to extend my map generator to handle continents; take a look at this project.
- Corey Lee has a political map generator using Voronoi regions.
- Island is a Scala project that uses techniques similar to the ones on this page.
- PtolemyJS is a Javascript game engine that includes a Voronoi region map generator.
- Jesse Morgan has used ideas from this map generator to build a city generator (project page and source code)
- Kaelan Cooter has a hexagon world map generator with elevation, moisture, biomes, rainfall, aquifers, and territories.
- Phill Spiess also uses Voronoi and noisy edges for his project but no details are posted.
- Sword & Scroll uses a Voronoi map generator to create political zones (baronies)

The map generator wasn’t designed for direct use but Welsh Piper (encounter tables, Minocra), Kingdoms in Trevail, Cresta, and others (1, 2, 3) are using the map generator to create maps for their projects. You can use the “export PNG” button to export a 2048x2048 PNG that you can then adapt with Photoshop to color, style, and annotate for your own needs.

### Modules

I tried to structure the map representation so that modules could annotate them without creating a code dependency. The GUI module `mapgen2.as`

depends on `Map.as`

(core) and `Roads.as`

(non-core), but `Maps.as`

does *not* depend on `Roads.as`

. Every polygon, edge, and corner in the graph has an index, which can be used as a key into an external table. In `Roads.as`

, there’s a `road`

array that’s indexed by the edge index.

Where core map code can reference `edge.river`

as a core field, the module can’t do that. Instead, the module references its local variable `road[edge.index]`

. This works for polygon centers and corners as well. It keeps the core clean.

I have three modules: Roads, Lava, and NoisyEdges.

### Roads

Realm of the Mad God doesn’t use most of the features of this map generator, but I built a road generator for them. I observed that in the game, people naturally explore rivers. This unfortunately leads them up to the mountains, where they die. I wanted to build some roads that are at right angles to the rivers.

I calculated contour lines along the corners. Where the contour level changes, there’s a road. It’s a fairly simple algorithm that works most of the time, but sometimes creates tiny loops:

Whereas rivers meander along Voronoi edges (blue lines in the diagram above), roads go on Delaunay edges (red lines). Roads don’t get the noisy edge treatment. Instead, they are drawn with splines from edge midpoint to midpoint:

Most polygons have two neighbors with roads. For them, there’s a regular spline connecting the two edge midpoints. For polygons that have more than two road neighbors, I instead draw an intersection, with splines from all the edge midpoints to the polygon center. In the diagram above, the lower left polygon has an intersection and the upper right polygon has a regular spline.

### Lava

Lava and rivers follow the same paths. Lava fissures occur in high dry areas, and are assigned to some subset of the edges. In a game, lava and water will of course be different, but here they only differ in color and placement. Lava gets the noisy edge treatment:

### Abstract Rendering

A *map* should show the relevant portions of the world, not all the details. With this projects I’m generating maps with some level of detail, but it’s not detailed down to the vegetation or towns, and it’s not completely abstract either. It may be possible to render a more abstract map in the style of maps of Middle Earth (such as this one). I made some notes about what I want from game maps.

### Watersheds

By following the downslope arrows (described in the section on elevation), there’s a path from every polygon corner, along edges, to the coast. I use this to mark every corner with the location where the water would flow out to the ocean. All corners with the same outflow location can be considered to be part of the same watershed.

The watershed code is incomplete. There’s a watershed view in the demo, but I’m not happy with it. I’ve tried polygon centers and corners as watershed boundaries and neither is quite right. I have put watershed calculations on hold until the day I need them.

The place I thought watersheds would be useful is for naming larger regions. There are roughly 1000 land polygons on the map in the demo. In a game map it might be nice to have a smaller number of named regions that group together polygons. For example, the XYZ Mountains can be above the XYZ Valley, which might have the XYZ River flowing through it. Players would be able to learn that these features are related. I didn’t get very far with this project but I might come back to it someday.

### Impassable borders

In this map generator all the borders between polygons are the same. There’s a smooth transition from one to the other. It might be interesting to make some edges discontinuous, so that we can make cliffs, chasms, plateaus, and other sudden elevation changes. See this article for ideas on how to make the Voronoi regions interesting for gameplay.

### Terrain analysis

Pathfinding should be fairly fast on a polygonal map, and may be useful for terrain analysis. For example, if two locations are spatially close but pathwise far, that may mean there’s a bay or mountain in the way, and that’d be a good place for a tunnel or bridge. A pathfinder could also help find places where we need bridges to nearby islands. Polygons that show up on paths often might be strategically more valuable than polygons that rarely are used for paths.

### Named areas

As mentioned in the watersheds section, I’d like to name map features. Combined with terrain analysis, names could be assigned to rivers, mountains, lakes, groups of polygons, coastlines, oceans, forests, peninsulas, valleys, etc. Names in an area could be related. For example, the XYZ River could flow from Mount XYZ through the XYZ Valley. I haven’t worked on this in part because I think it helps if it’s for a specific game instead of a generic map generator. Not only should names connect to the game’s theme, there could be items and quests and plot elements that are related. For example, the Sword of XYZ might be found only in the XYZ Valley.

### Variable density

Fortune’s algorithm should work within a polygon to subdivide it into smaller polygons. A map where most of the world is coarse, but some areas are more finely divided, could be interesting. Alternatively, we could place the original points with variable density so that some areas get more polygons than others. For example, we could use Poisson Disk Sampling instead of Lloyd’s Algorithm.

### Better noisy edges

I implemented a very simple noisy edge system, with jagged lines. The corners are very visible when you zoom in on the map. A better system might involve curved splines, or a fractal expansion that looks more detailed as you zoom in.

This page started out as three blog posts on the topic: part 1 is about polygons, map representation, islands, oceans and lakes and beach and land; part 2 is about elevations, rivers, moisture, and biomes; and part 3 is about rendering, demo, and source code. Having it all on one page made more sense in the long term.

For those of you interested in how I got to this point, a brief history:

- In December 2009, Rob and Alex of Wild Shadow Studios had asked me if I had a quick way to generate maps. I had already been thinking about using Perlin noise for maps, so I tried it, with good results. I got something going within a day, and then spent the next month tweaking and trying variations. Most of the variations failed, and taught me that there were limitations with this approach. One month was a good time to stop, so I stopped working on maps and moved on to other small projects — art, animation, monster groups, NPC AI, among others.
- In June 2010, I was inspired to work on maps again. I spent the month sketching out ideas on paper and trying some prototypes. I tried hexagon grids, hexagonal river basins, quadrilateral river generation, volcanos, hills, erosion, weather systems, and a few other things.
**Everything failed.**However, I learned a lot by trying these things out. Delaunay triangulations for example didn’t work out, but they led me to Voronoi diagrams. The quadrilateral river generation didn’t work out, but the quadrilaterals were useful later when I worked on noisy edges. The erosion system didn’t work out, but some of the same ideas were useful when I worked on rivers. - While attending the Procedural Content Generation workshop, I sketched out some more ideas on paper for map generation. During the July 4 long weekend, I implemented these, and they worked really well. I worked out Voronoi polygons, map representation, island generation, noisy edges, elevation, biomes, rivers, and elevation redistribution that weekend. I experienced flow. It was great! Most of the core system was in place in just three days.
- Every weekend in July and August, I made improvements, many of them substantial. I also made many changes that didn’t work out, and I deleted them. As the core map features became good, I shifted my focus to the map rendering and the UI. As the map rendering and UI improved, I was able to
*see*more flaws in the maps, and I found lots more bugs I needed to fix. I also made major refactorings to simplify the code that had grown organically. - By the end of August I found that I was only working on minor things, and decided the project was ready to wrap up. I spent the Labor Day long weekend writing up the results on this page (and the blog posts). Much of my time went into making good diagrams. The diagrams actually exposed more bugs, and I ended up making bug fixes, greatly simplifying one feature (elevation redistribution), and implementing a new feature (moisture redistribution). I also renamed and commented code to make it easier to explain.

Why am I keeping track of this? It’s because I’m trying to improve the process by which I approach these small (1-3 month) projects. There are some things I want to remember:

- It’s useful to have a
**key idea**that drives everything else. The simple maps I did in January were based on Perlin Noise. These maps are based on Voronoi diagrams. I need to pick something and go with it, but only after… - It sometimes takes a
**lot of experimentation**before I run across the right idea. I spent a month on ideas before coming up with Voronoi as the key structure. I need to sketch out lots and lots of ideas. - I have a
**lot of failures**. The key is to fail quickly, not to avoid failing. I need to not get discouraged. - I got the core system up in three days.
**A quick prototype**can tell me a lot about whether an idea’s going to work out. In the early stages I need to focus on a prototype and not worry about making it a high quality system. - In the very early phase it’s more important to
**learn from the system**than to produce good code. I need to ask myself what I’m trying to learn with a prototype. **Failures are sometimes useful later**. I need to keep them accessible. I’ve been deleting the code as soon as it fails, but maybe I should make lots more git branches and store them there.- The
**ability to see things**can help a great deal in understanding what’s going on. I missed several bugs because I never bothered to build a visualization for that part of the data. I need to display as much as I can. - There are sometimes
**tiny things that seem wrong**that actually mean I have a bug somewhere. I often shrug these things off. Even if it’s not a good time to investigate and fix some bug, I need to track them somewhere so that I can later investigate. **Writing the blog posts**helped tremendously. It forced me to understand every part of the system, to look at all the data, and to make sure all the code could be understood. It made me question every phase of map generation and improve the ones that were hard to explain. I need to write blog posts much earlier in the process. Explaining is a good way to learn.

I’ll keep these in mind as I work on future projects.

Thanks to the Dungeon League blog for a great series on procedural map generation, the Procedural Content Generation wiki for ideas for map generation, the incomplete Voronoi wiki for some useful resources about Voronoi diagrams.

My thanks to `nodename`

for as3delaunay. It’s an Actionscript 3 library for generating Voronoi and Delaunay graphs. Also my thanks to `polygonal`

for the PM_PRNG random number library, which allows me to use and reset the seed value so that I can reproduce a series of pseudorandom numbers. I used the OptiPNG library to optimize the PNG images on this page.

Delaunay triangulation and Voronoi polygons are taught in many graphics classes. For example, see Stanford CS 368(PDF). I also looked at relative neighborhood graphs and Gabriel graphs but didn’t use either.

Delaunay triangulation can be used for maps, in the form of triangular irregular networks. Voronoi diagrams are also used for maps.

Fortune’s Algorithm is one of several algorithms that can turn a set of points into Voronoi polygons. It’s implemented in `as3delaunay`

. Lloyd Relaxation is used to improve the distribution of random points. It decreases the irregularity of the Voronoi polygons.

The Voronoi wiki has some incomplete pages on graph representation and edge representation, as well two pages that helped me with river generation: rivers and watersheds and crust and skeleton.

The Relief Shading Website has some images of shaded relief maps, as well as design guidelines for shading and coloring. I am sad to say I did not have time to apply these techniques. I also studied Bing and Google maps to see how they draw various features; see this article and my blog post and this article.

The Whittaker diagram is one way to predict common biomes given climate. Wikipedia has a page listing biome classification schemes and various biomes.

Wikipedia also has a nice list of landforms that one might want to generate in a game map generator. I did not explore these for this project.

Ken Perlin is the master of noise, with Perlin Noise. He’s also made the lesser known Simplex Noise(PDF). For this project I used Perlin Noise for the overall island shape. Joe Slayton has a page on how to turn perlin noise into islands. I was looking for “blue noise”, which led me to Dunbar and Humphreys’s paper on noise generation and recursive Wang tiles before I found Lloyd’s algorithm for better random point distribution. I also looked at Craig Reynold’s textures but didn’t have time to do anything with them.

Also interesting were these papers about generating worlds, Gozzy’s wilderness map generator, donjon’s world generator, a paper on procedural road generation, a paper on procedural city generation. Straight skeletons seemed like they might be useful for defining mountain ranges, but once I discovered how well “distance from coast” worked, I didn’t need anything else. The 3d map generation in Dwarf Fortress is pretty neat.