View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007736 | Dwarf Fortress | Init Options | public | 2014-07-30 06:53 | 2014-08-15 05:41 |
| Reporter | Quietust | Assigned To | Toady One | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | 0.40.05 | ||||
| Fixed in Version | 0.40.09 | ||||
| Summary | 0007736: Omitting STRICT_POPULATION_CAP from d_init.txt defaults it to 0 | ||||
| Description | Most init/d_init settings with numeric values have valid ranges, such that setting a value too high or too low will restrict it to that range (e.g. POPULATION_CAP has a minimum of 7 and a maximum of 1000). Such options, if not set at all, will be given a value of 0, which may not make any sense. The most notable instance of this is STRICT_POPULATION_CAP, which defaults to 0 when not specified (which has turned out to be the case with several incorrectly-prepared "starter packs", as noted in 0007684). Ideally, most init/d_init settings should be pre-initialized to sane values in memory. | ||||
| Additional Information | Additionally, d_init.txt should probably include the same warning present at the top of init.txt. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-07-30 06:53 | Quietust | New Issue | |
| 2014-07-30 16:07 |
|
Relationship added | has duplicate 0007746 |
| 2014-07-30 16:07 |
|
Relationship added | related to 0007684 |
| 2014-07-30 18:52 | lethosor | Assigned To | => lethosor |
| 2014-07-30 18:52 | lethosor | Status | new => acknowledged |
| 2014-08-03 09:29 | lethosor | Relationship replaced | parent of 0007684 |
| 2014-08-13 08:40 |
|
Summary | Omitting init setting can result in invalid default setting values => Omitting STRICT_POPULATION_CAP causes it to default to 0 |
| 2014-08-13 08:41 |
|
Relationship added | related to 0007988 |
| 2014-08-13 08:41 |
|
Summary | Omitting STRICT_POPULATION_CAP causes it to default to 0 => Omitting STRICT_POPULATION_CAP from d_init.txt defaults it to 0 |
| 2014-08-13 08:41 |
|
Status | acknowledged => confirmed |
| 2014-08-13 08:42 |
|
Relationship added | related to 0002922 |
| 2014-08-13 08:48 |
|
Relationship replaced | has duplicate 0007988 |
| 2014-08-13 10:25 | Toady One | Status | confirmed => resolved |
| 2014-08-13 10:25 | Toady One | Fixed in Version | => Next Version |
| 2014-08-13 10:25 | Toady One | Resolution | open => fixed |
| 2014-08-13 10:25 | Toady One | Assigned To | lethosor => Toady One |
