Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001344Dwarf FortressWorld Generation -- Parameterspublic2010-04-19 16:052014-08-22 08:14
Reporterilmoran 
Assigned ToFootkerchief 
PrioritylowSeveritymajorReproducibilityhave not tried
StatusconfirmedResolutionopen 
PlatformOSWindows Vista 64 BitOS VersionBusiness SP 1
Product Version0.31.03 
Target VersionFixed in Version 
Summary0001344: Setting a maximum lower than a minimum causes DF to hang/freeze on world gen
DescriptionIf a "maximum" parameter (i.e. Maximum Savagery) is set lower than the minimum for the same value (i.e. Minimum Savagery), program hangs when attempting to generate a world. Was unable to abort out of world gen.
Steps To ReproduceChoose to create a new world with parameters.
Set Minimum Savagery to 10
Set Maximum Savagery to 9
Generate world
<System will hang, nothing shows on screen, not even a rapidly increasing rejected world count>
Attempt to abort world gen.
Additional InformationI would suggest that either attempting to set the minimum above the maximum, or the maximum below the minimum, should warn the user before letting them out of the parameter screen, or automatically set them to the same value. Should not be able to get to the point of attempting world generation with invalid min/max values like this.
Tagsworldgen
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-04-19 16:05ilmoranNew Issue
2010-04-19 17:32KennelTag Attached: worldgen
2014-08-22 02:23CosinusNote Added: 0029473
2014-08-22 08:14FootkerchiefAssigned To => Footkerchief
2014-08-22 08:14FootkerchiefStatusnew => confirmed

Notes
(0029473)
Cosinus   
2014-08-22 02:23   
Going through worldgen bugs, I found this and tested in 40.09.
The problem is still present as described in the description.
Worldgen stops in the "preparing elevation" step and can not be aborted (you have to kill DF to stop it).
I also tried this with other parameters like volcanism and drainage; the result is the same.
Although no one with a sane mind would enter a lower maximum then minimum, this bug seems like a quick fix. Just check the parameters before worldgen and display an error.