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.

v0.34:World rejection

From Dwarf Fortress Wiki
Revision as of 10:35, 1 July 2012 by SAFry (talk | contribs)
Jump to navigation Jump to search

Dwarf Fortress uses a 'belt and braces' method of world generation in that whilst the map properties are configurable by world tokens there are also tokens which will cause the rejection and 'reroll' or re-randomisation of the world. By way of example, if I were to leave the world at it's default setting but set a rejection parameter which required there to be a large number of deserts; then a large number of worlds might be rejected until one (by random chance) was finally generated that high a higher then usual number of deserts. This is an inefficient way of generating a world with lots of deserts though as one might as well just change other tokens to produce such a world. Also it is possible to set the rejection parameters in such a way that it will effectively cause endless rejections, being incredibly unlikely or impossible that the required world is generated.

If a certain number of rejections of the same type happen during world gen then you will get a notification telling you what is causing the rejections. This can happen after a few hundred rejections or it may take thousands. This is possibly due to the fact that you may have more then one type of rejection occurring and as such it takes thousands of rejections until any one type hits the threshold for the warning message.

The following are the primary rejection parameters, their sole purpose is to cause rejections, they do not affect the generation of the world in any way:

  [REGION_COUNTS:SWAMP:0:0:0]
  [REGION_COUNTS:DESERT:0:0:0]
  [REGION_COUNTS:FOREST:0:0:0]
  [REGION_COUNTS:MOUNTAINS:0:0:0]
  [REGION_COUNTS:OCEAN:0:0:0]
  [REGION_COUNTS:GLACIER:0:0:0]
  [REGION_COUNTS:TUNDRA:0:0:0]
  [REGION_COUNTS:GRASSLAND:0:0:0]
  [REGION_COUNTS:HILLS:0:0:0]

Note: the above values are arbitrary although these setting effectively disable the region counts.

  [SUBREGION_MAX:2750]
  [ELEVATION_RANGES:0:0:0]
  [RAIN_RANGES:0:0:0]
  [DRAINAGE_RANGES:0:0:0]
  [SAVAGERY_RANGES:0:0:0]
  [VOLCANISM_RANGES:0:0:0]

Note: the above values are arbitrary although these setting effectively disable the range counts.

The following are tokens are not rejection parameters but instead force to placement certain of features. This can cause rejections if the world generated does not support the placement of the features in sufficient quantities or at all. For example a volcano requires the square to have a volcanism of 100, if the maximum volcanism for the world is less then 100 then no volcanoes can be placed. See Advanced World Generation for more details.

  [VOLCANO_MIN:3]
  [PEAK_NUMBER_MIN:12]
  [PARTIAL_OCEAN_EDGE_MIN:1]
  [COMPLETE_OCEAN_EDGE_MIN:0]
  [RIVER_MINS:300:300]
  [MOUNTAIN_CAVE_MIN:25]
  [NON_MOUNTAIN_CAVE_MIN:50]
  [TOTAL_CIV_NUMBER:40]
  [PLAYABLE_CIVILIZATION_REQUIRED:1]

It is unknown if the following tokens can cause rejection:

  [REGIONAL_INTERACTION_NUMBER:28]
  [DISTURBANCE_INTERACTION_NUMBER:28]
  [GOOD_SQ_COUNTS:0:0:0]
  [EVIL_SQ_COUNTS:0:0:0]