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.
Editing v0.34:World rejection
Jump to navigation
Jump to search
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
You are editing a page for an older version of Dwarf Fortress ("Main" is the current version, not "v0.34"). Please make sure you intend to do this. If you are here by mistake, see the current page instead.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
{{av}} | {{av}} | ||
| − | + | Dwarf Fortress uses a "belt and braces" method of world generation in that whilst the map properties are configurable by [[world token]]s there are also tokens which will cause the rejection and 'reroll' or re-randomisation of the world. By way of example, if you were to leave the world at its default setting, but set a rejection parameter which required there to be a large number of "minimum desert tiles", then a large number of worlds might be rejected until one (by random chance) was finally generated that met that requirement. Because of the high number of possible rejections, this is an inefficient way of generating a world with many deserts; instead, it's recommended to work with broader parameters, such as [[#Weighted Ranges|Weighted Ranges]], to generate the world you want. It is possible to set the parameters in such a way that will result in endless rejections because they specify a world which is incredibly unlikely or impossible to be 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 than one type of rejection occurring, and as such it takes thousands of rejections until any one type hits the threshold for the warning message. | 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 than one type of rejection occurring, and as such it takes thousands of rejections until any one type hits the threshold for the warning message. | ||
| Line 19: | Line 19: | ||
[REGION_COUNTS:GRASSLAND:0:0:0] | [REGION_COUNTS:GRASSLAND:0:0:0] | ||
[REGION_COUNTS:HILLS:0:0:0] | [REGION_COUNTS:HILLS:0:0:0] | ||
| − | <small>'''Note: the above values are arbitrary although these | + | <small>'''Note: the above values are arbitrary although these setting effectively disable the region counts.'''</small> |
[SUBREGION_MAX:2750] | [SUBREGION_MAX:2750] | ||
| Line 29: | Line 29: | ||
[VOLCANISM_RANGES:0:0:0] | [VOLCANISM_RANGES:0:0:0] | ||
| − | <small>'''Note: the above values are arbitrary although these | + | <small>'''Note: the above values are arbitrary although these setting effectively disable the range counts.'''</small> |
== Placement tokens == | == Placement tokens == | ||