Filroden's FoundryVTT Modules

All modules respect your chosen light/dark theme and offer two colour options:

On this page

FAQ

A note on performance

Terrain, moisture, temperature, biomes and rivers are all calculated from one another, so the module has to keep them consistent after every edit. Since version 2.5.0 it works out what an edit actually changed and recalculates and redraws only that part of the map. The result is identical to regenerating the whole map, only much quicker.

These edits only recalculate the area they change:

  • Terrain brush strokes, and undoing or redoing them.
  • Adding, moving or deleting fault lines, custom rivers and river source pins (and their nodes), removing or moving an automatically placed river source, changing a fault's strength, and undoing or redoing any of these.

For example, on a 3210 x 2400 map with over 7,000 brush strokes and 46 custom rivers, finishing a brush stroke or moving a custom river node takes about a fifth of a second. Before 2.5.0 the same edits took six to seven seconds. An edit that changes a large area takes longer because more has to be redrawn. An edit that moves the map's highest point (raising terrain above the current peak, or lowering the peak itself) takes longer still, because land is shaded relative to the highest point and so the whole map has to be redrawn. Since 3.0.0 a whole-map redraw is shared between your computer's processor cores, which cut it from one to two seconds on large maps to about half a second.

Tectonic features (see Rivers and faults) take longer to work out than other edits: up to a few seconds for a large feature on a large map. The result is kept, so a feature is only worked out again when its own settings change or the terrain beneath it changes. Editing one feature therefore only recalculates that feature.

These actions still run the full procedural generation engine over the whole map, and replay every terrain brush stroke in order:

  • Loading a map.
  • Changing the seed, the generation engine, the map size, the sea level, or any of the terrain, climate and river sliders.
  • Adding, editing or deleting custom biomes.
  • Editing land masks in Guided mode.

The full engine can be computationally heavy, particularly at larger resolutions. Maps of 1000x1000 pixels process very quickly. Maps of 4000x4000 pixels look beautiful, but may take a few seconds to calculate even on powerful PCs. On a map with a long brush history, replaying the strokes is the largest part of that time, and it is about four times faster in 2.5.0 than before.

Version 3.0.0 made whole-map generation much faster again. The terrain, the climate and the drawing of the map are shared between all of your computer's processor cores, and the calculations themselves are quicker. Maps you have already made still generate exactly as before. For example, loading a 3210 x 2400 map with over 7,000 brush strokes went from about 11 seconds to about 7, and loading a 4000 x 2400 Advanced (tectonics) v2 map went from about 23 seconds to under 6. How much faster your maps load depends on how many cores your computer has.

The questions below go into more detail on specific performance and behaviour quirks. If you want the full technical story of how the changes in 2.5.0 work, it is written up in the performance write-up on the repository's Discussions page. The changes in 3.0.0, including the faster generation, have a write-up of their own.

Why do my maps look different in v2+ compared to in v1?

What you are seeing is a difference in how biomes are being procedurally generated as a result of orographic lift (rain shadows caused by mountain ranges). In v1, there was a bug which caused orographic lift to only consider the procedurally-generated elevation model. If you used any tool to edit the terrain (terrain brushes, custom rivers or tectonic faults), these would not be taken into account. In addition, the original strength of the orographic lift was using a fixed value which did not change with the map's resolution or its scale. Both these were fixed in v2. This means procedurally generated biomes will look a little different (more realistic), particularly on maps that have a lot of terrain edits.

Note that because orographic lift is scaled, biomes in regional maps should still look the same as the original map from which they were created.

Why do some procedural rivers look slightly different after updating to 2.5.0?

When a procedural river reaches a point where several neighbouring pixels are equally low, it has to pick one, and it uses a random number to do so. Before 2.5.0 every river drew its random numbers from one shared sequence, which meant that changing one river (for example by moving a river source pin or editing a fault) gave every river traced after it a different sequence, and rivers all over the map could take new routes. Each river now has its own sequence, which depends only on the map's seed and where that river starts.

The side effect is that on an existing map, a river that had a choice between equally low pixels may now make a different one. The differences are small (I could not see any meaningful difference on any of my maps). If a river you were happy with has moved, you can lock it in place by drawing it as a custom river (River on the bar of Rivers and faults).

The benefit is that editing one river, fault or river source pin no longer changes unrelated rivers elsewhere on the map. Only rivers connected to the edit (because they merge with it or drain into the same lake) can change, along with any river whose own path or catchment you have reshaped.

Why is there a pause after I finish an edit?

When you finish a stroke, move a node or undo an edit, the module waits for two seconds before it recalculates, so that a quick run of edits triggers one recalculation instead of one for each edit. The brush shows its effect as you paint, and the calculations that depend on it (moisture, biomes, rivers and shading) run once you pause. Moving one of the terrain or climate sliders has a shorter pause of under a second. The times quoted in the performance note above do not include this pause.

If you are placing or dragging many nodes and do not want the terrain to update after each one, press Pause regeneration on the bar of the Rivers and faults tool or, on a Guided map, the New map tool. While it is paused, changes are collected and applied when you press Apply changes or turn the pause off again (see Rivers and faults). Pausing lasts only for the current tool and edit session, and turns itself back on when you change tool or finish editing.

Can I import my own map?

You can bring in any image as a reference (see Reference image), and it will be shown as a canvas overlay. You can then use the Flat terrain engine to generate a flat landscape slightly higher than sea level. From here, you can use the terrain edit tools to sculpt your topography to match your reference image. Biomes will still be calculated automatically, but these can also be edited using the Biome brush (see Biomes).

Will you add the ability to load a Digital Elevation Model (DEM) or a greyscale elevation map to generate the terrain?

No. This is still being considered. The main issue is that for the module to faithfully recreate the map when it is loaded would mean saving the DEM or image with the map. This adds a lot of file size to each map save (which are Foundry Journal pages).

Can the sea be something other than water, such as mist, fog or a sea of lava?

Not directly: every map assumes there is water up to its sea level. You can still make the sea look and behave like something else, or have very little sea at all, with the tools that already exist.

  • Cover the water with a custom biome. In Biomes, open Edit biomes and add custom biomes (for example "Mists" or "Lava sea") with the colours you want. Set their Placement to Overwater only (or to Land and Overwater if they should span both), so they sit on top of the water and hide the seabed beneath it, as Pack ice does (see Biome placement). Then either paint them where you want them with the biome brush, or open the Biome rule editor and give them rules whose Elevation range is the Underwater zone, so they cover the sea and lakes by itself (or use a range of elevations above and below sea level). An Underwater only biome works the other way: it lies on the seabed and is seen through the water, which suits something glowing beneath a clear or murky sea.
  • Have less sea, or none. How you do this depends on the map's engine (see Terrain). On a Legacy generation or Flat map, lower the Sea level. On an Advanced (tectonics) map, lower Grouping to leave more land and merge the landmasses together. On a Guided map, draw one land mask that covers the whole map (see New map), and use ocean masks only where you want a sea.
  • Change how the water looks. The Water section of Terrain sets the water's Water tint (from blue-green through blue to blue-violet), Water saturation (turn it down for a grey, colourless sea) and Water clarity (turn it down to hide the seabed). These change only how the water is drawn, so they combine with either of the ideas above.

Can I build realms above or below the surface, such as sky kingdoms or an underworld?

Not yet. Subterranean and aerial worlds, each with its own realms, cultures, borders and routes and with links to the surface where they meet, are on my roadmap for a later version. They need a system of map layers, a way to generate terrain that is above or below the surface, and connections between the layers so they can interact, which is a lot of work. It is definitely possible, but not for a while.

Why is it taking longer and longer for the terrain to regenerate when I make a new edit?

Before version 2.5.0 this was expected. Once an edit was complete, all terrain brush strokes were replayed in chronological order, so the more strokes you made, the longer every edit took, and hand-drawing an entire map at a high resolution could easily generate thousands of strokes.

From 2.5.0 the module keeps a copy of the terrain with every brush stroke already applied, and updates it as strokes are finished, undone and redone. Ordinary edits no longer replay the history, so the number of strokes on a map no longer slows them down.

The strokes are still replayed in full when the whole map is regenerated (see the note on performance above), so a map with a very long history is slower to load, and slower when you change the seed, the sea level or a slider. Undo can also fall back to a full replay: the module keeps the data it needs to undo strokes within a memory limit (64 MB at most, less on very large maps), and if you have made so many strokes that the data for the oldest ones was dropped, undoing one of those replays the history instead.

Does the module use more memory than it used to?

Yes. Keeping edits quick means keeping extra copies of the terrain. On a 3210 x 2400 map that is about 38 MB for the copy of the terrain with every brush stroke applied, up to 64 MB for undo data, and a 31 MB working copy used to find what an edit changed, which is released after 30 seconds without an edit. Smaller maps use less. If the browser cannot supply the memory, the module falls back to the slower method instead of failing.

Do you have any tips for how to improve performance?

Edits are now quick at any resolution, but anything that regenerates the whole map (see the note on performance above) still takes longer the larger the map is. So it is still worth creating your initial terrain map at a lower resolution, such as 1600 x 1200, with any engine except the older Advanced (tectonics) v1 and Guided v1 maps (which need updating before a regional map can be created from them). This reduces the computational power required to calculate the terrain and biomes while you experiment with the seed, the sliders and the overall shape. Once you have your topography, custom rivers, and tectonic faults (which physically deform the terrain) in place, you can generate a high-resolution regional map from it (see New map). Instead of cropping a small area, expand the crop box to cover the entire map and increase the target resolution. The module will automatically upscale the map, calculating more granular detail while perfectly preserving your custom features. Once you are working at this higher resolution, loading the map and changing the seed or a slider will take proportionally longer, but brush strokes and edits to rivers and faults stay quick.

A few other habits help:

  • Make your terrain and slider decisions before your fine-detail brush work, because every slider change regenerates the whole map and replays your strokes.
  • Use the pause toggle (see above) when you are placing or dragging many nodes.
  • Remember that the time an edit takes grows with the area it changes, so a large sweeping stroke costs more than a small one.

How can I see how long things are taking?

After every full render, brush stroke, undo, redo, and climate or features refresh, the module writes a summary to the browser console (press F12 to open the developer tools and look for the summary, which follows lines starting with World Map Builder |). It lists each phase of the work with its time and its share of the total. If you report a performance problem, including that summary and your map's resolution is very helpful.

Why did my custom river create a massive, unnatural canyon?

Water never flows uphill. On a version 3 map (every new map, see Engine versions), a custom river follows the land within a corridor around the line you draw, and by default it bends around high ground your line crosses where the corridor allows, and otherwise runs over it. It only cuts a gorge through a ridge or a mountain range when you tick Cut through high ground in its inspector (see Rivers and faults), as a river older than the mountains would. If the gorge is not what you wanted, clear the tick.

On an older map (version 2 or earlier), a custom river runs exactly along the line you draw, and the ground along it is lowered into a valley so the river always runs downhill from its higher end to its lower end. If your line crosses a high mountain range, the valley has to be cut deep enough through that range for the river to pass, which makes a gorge. To avoid extreme canyons, try to route your rivers through natural valleys, or use the Lower or Level brushes (on the Terrain bar) to flatten the path before drawing the river. Updating the map to version 3 (see Updating older maps) also gives its rivers the corridor.

Why doesn't my custom river run exactly along my line?

On a version 3 map, a custom river follows the lie of the land within a corridor around your line, so it winds like any other river. To keep it closer to your line, lower its Corridor width in the inspector (down to 3 river widths either side); to let it follow the land more freely, raise it (up to 15). See Rivers and faults.

Why do my rivers suddenly change their path when I edit the terrain?

Procedural rivers (those flowing from the automatically placed river sources) follow the lie of the land downhill until they reach the sea or join another river, pooling into lakes where they run into hollows. If you use the terrain brushes to raise a hill, carve a valley, or smooth a slope anywhere near a river's path, you alter the underlying topography. The hydrology engine recalculates the most natural route based on your new landscape, which will sometimes divert the water down a new valley.

From version 3.0.0, the river sources are also placed afresh from the land every time the rivers are worked out (see Rivers and faults). A river only rises where the land is high enough and moist enough, so raising or lowering the ground can also start a new river or remove one. River sources you have added, removed or moved yourself stay as you left them.

From version 2.5.0, this only happens to rivers whose path or catchment you have actually reshaped. Editing one river, fault or river source pin no longer changes the routes of unrelated rivers elsewhere on the map.

Tip: If you need a river to stay in an exact, permanent location regardless of how you sculpt the nearby terrain, draw it as a custom river instead (River on the bar of Rivers and faults). A custom river always keeps to the line you draw (on a version 3 map, within its corridor: set a narrow Corridor width to keep it close) and shapes a valley for itself, whereas procedural rivers simply adapt to the landscape as it currently exists. (Beyond the end of your line, a custom river follows the land like any other river until it reaches the sea or another river.)

Why does my world map have no villages?

A run of Generate places the places a world map can show: capitals, cities, large towns, towns, castles and ports, a few hundred kilometres apart for the largest. Villages and market towns are far too many and too close together for a world map, so they come from Fill in, on a regional map cut close enough in for them to be seen (see Fill in). Tick Fill in villages and market towns when you cut the regional map in New map, or use Fill in in the Generate tool once it is open.

Why is part of my regional map empty after a fill-in?

First check the Detail level in the map controls: market towns and large villages show from Local, and the other villages only at Everything (see Detail level).

If they are still missing, the land is probably too far from the inherited roads and towns. Market towns and villages stand only within about 15 km of a road, river trade route or town (further round a big town: about 30 km round one of 4,000 people or more, and 45 km round one of 15,000 or more). Beyond, people live in hamlets and farms, which are not shown. A land the generator joined to the rest only by sea lanes has no roads of its own, so only the country round its towns is filled in. Drawing a road across it with Routes and pins and filling in again settles the land along it.

Why are some names missing from the map?

Several things decide whether a name is drawn:

  • The detail level: each pin style has a Name detail level, so a kind of place can appear before its name, and the names of duchies and counties appear with their layers (see Detail level).
  • No room: with Avoid overlaps on, a name that would cover another name or a pin is left out. The Labels list marks it No room, and its With no room filter finds them all. Drag the name to a place of your own in the Labels tool, or try a smaller Symbol size.
  • The Labels menu in the map controls: a label style that is unticked hides every name in that style.
  • The label's own visibility: a hidden label (its eye in the Labels list, or Show names off when the map was generated) is not drawn, though its pin, route or region is.
  • A border: while the map has a border, names keep clear of it, so a name at the map's edge may find no room (see Cartography).

Last updated 5 November 2026. This page is copied from the wiki on GitHub, where it is maintained.

Full screen preview