v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

40d:World token

From Dwarf Fortress Wiki
Jump to navigation Jump to search
This article is about an older version of DF.

World tokens are used to store world parameter settings used in creating custom worlds. Parameter settings are stored in world_gen.txt, found in the \data\init\ folder after you've hit F6 in the world generation menu. You can change all of these in-game in the world generation menu by editing advanced parameters, or by editing the file directly. Parameters are also explained at Advanced world generation.


Token Arguments Description
TITLE string The name of the template you've created, not the name of the world itself.
DIM X:Y values The dimensions of the world, in X and Y rows and columns.
END_YEAR number The year it will end at during world generation, assuming all of your megabeasts aren't dead.


When it hits the first number value, it begins checking to see if that percent of your megabeasts have been killed, which leads the game to halt. Often this leads to very early world generation halting. It can be stopped entirely by setting the percent value to -1. To make your megabeasts not get killed to easily, try modding the raw creature files to make them stronger, i.e. larger size.
REVEAL_ALL_HISTORY 1 or 0 Whether or not to hide history in legend mode until you've discovered it in adventure mode.
CULL_HISTORICAL_FIGURES 1 or 0 Whether or not the game ignores unimportant figures in history generation.


The min and max for all values except temperature are percentages (0 to 100) while temperature is -1000 to 1000. The X and Y variance are the amount the values change along the X and Y axis of a given map; 0:0 for example on a value gives a random value across the entire map.

By subtly tweaking the min and max values, vastly different maps can be made. The largest chance of having unusable maps comes from too high of a savagery value, which means civilizations cannot form. Increasing variance will result in a more "patchwork" world, with many small biomes. For this to work, the SUBREGION_MAX token must be edited as well.


mesh size
mesh weighted range 0-20, 20-40, 40-60, 60-80, 80-100

The Mesh Size affects the smoothing brush in the world painter. It also seems to have an affect on the variability of the regions during world gen if you do not use the world painter.

The weighted ranges seem to affect the relative amounts of that parameter when world gen begins. For example, if you set the 0-20 range of rainfall to 5 and the 20-40 of rainfall range to 1, you will get approximately 5 times as many areas with 0-20 rainfall as areas with 20-40 rainfall. These amounts do not have to add up to any particular number; in the above example, you can get the same effect with 500 and 100.

Lastly, the weighted ranges affect what parameters the world begins with; they do not make rejection checks, although they can be responsible for many rejections if you neglect to turn off some of the minimum parameters.


small region value
medium region value
large region value

These values change the amount of good or evil tiles on the map, depending on the size of the region it is being considered for. Overly large values seem to be fine; doubling or tripling the evil value of all three seems to not give any errors. Note: If either of these values are set to 0, they will BOTH generate no good or evil regions. Setting good or evil to 1:1:1 fixes this.
PEAK_NUMBER_MIN value 0 to 200 This determines if a region is rejected for not having enough mountain peaks. It can be a very frequent cause of infinite rejections if your map does not have enough cliffs/elevation/mountains.
OCEAN_EDGE_MIN value 0 to 4 This determines the minimum amount of oceans on your map. It can be a cause of rejections if you have very high minimum elevation, as there's not enough salinity to form an ocean.
VOLCANO_MIN value 0 to 200 This determines if a map is rejected for not having enough volcanos on it. It seems to have a relatively high threshold in terms of map rejections, as long as your volcanism is set appropriately high.

initial map tile count
initial biome region count
final biome region count

This token rejects a map if it does not meet the specific biome requirements. All values (except biome) can be set to 0 for much less map rejections.
EROSION_CYCLE_COUNT value Tells the world-generator how long the world has to erode its tall peaks down to mountainsides. The higher this number, the less jagged the world will be. If you use the maximum number, your mountains will dissolve before your eyes into plains.

pre-erosion value 0 to 800
post-erosion value

These values determine how many rivers are spawned during the river generation phase of world building. It's easiest to set both values the same.
PERIODICALLY_ERODE_EXTREMES 1 or 0 This token, when set to 1, will smooth out extremely high cliffs during world generation, making them more slope-like and able to be walked up in adventurer or dwarf fortress mode.
OROGRAPHIC_PRECIPITATION 1 or 0 Toggle that allows terrain height to affect rainfall. For example, moist air coming from the ocean blows over the land. As the terrain gets higher, it forces the moist air up, causing it to rain on the seaward side of a mountain. Eventually, all the rain has fallen if the mountain is tall enough. So, when the breeze goes over the top, there's no moisture left to fall on the other side, creating a rain-shadow. This should create a tendency for more extreme rainfall in regions, creating more forests, deserts, marshlands, and grasslands.
SUBREGION_MAX value 1 to 60000 The maximum amount of subregions a world can have. Larger values mean the regions will be smaller, while smaller values means they will be larger. Logically, setting this to very low values will result in numerous rejections since not all civilizations can live on them.
CAVE_MAX_SIZE value 1 to 500 This determines the maximum size of all caves generated in the world. Most new-style caves are around 25, while older, much larger and emptier caves can be made by setting it to 300.
MOUNTAIN_CAVE_MIN 0 to 800 This determines the minimum amount of mountainous caves to generate on the map. Having this set very high seems to generate a lot of ettins/giants/other cave creatures along with it as well.
NON_MOUNTAIN_CAVE_MIN 0 to 800 This determines the minimum amount of non-mountain caves to generate. Many kobolds or megabeasts will claim these.
ALL_CAVES_VISIBLE 1 or 0 This determines whether caves are hidden until you find them in adventurer mode. If this is set 1, you can also see them on the embark screen when creating a fortress.
TOTAL_CIV_NUMBER 0 to 100 This determines how many civilizations the world generator places on initial loading. Note that a high value here can cause lots of map rejections, particularly on smaller maps as there simply isn't enough room or regions to put them all in.
TOTAL_CIV_POPULATION -1 to 20000 This token determines the population cap of a civilization after it's been created. It should usually be kept the same value as the appropriate sized standard map.
PLAYABLE_CIVILIZATION_REQUIRED 1 or 0 When set to 0, the world will not be rejected if there is no place for a civilization that the player can play as.

mid value
low value
high value

Sets the minimum possible number of squares of certain ranges of each of the region qualities, such as elevation, rain, drainage, volcanism, savagery, and temperature. These need to be changed to reflect your regional meshes and weights. These are responsible for a HUGE number of map rejections. These values can all be set to 0 for much less map rejections, particularly in the case of more wacky, non-standard maps.