View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012628 | Dwarf Fortress | Dwarf Mode -- Nobles | public | 2023-11-28 22:46 | 2024-10-04 22:30 |
| Reporter | apoco | Assigned To | Toady One | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | Steam | OS | Linux | OS Version | Ubuntu 22.04 |
| Product Version | 50.11 | ||||
| Fixed in Version | 50.14 | ||||
| Summary | 0012628: Demand met but not when built | ||||
| Description | My baroness demanded a bismuth bronze chest in her dining room, and we finally created one, by gum. Strangely, her demand showed up as "green" which presumably meant it was met, before it was ever built. After placing the chest in her dining room, the demand changed to yellow. | ||||
| Steps To Reproduce | 1. Have a noble 2. Let the noble make a demand for something being built in their holdings 3. Create the thing Expected: the demand is not yet met Actual: the demand shows as met 4. Build (place) the item in their holding Expected: the demand shows as met Actual: the demand shows as not met | ||||
| Tags | Probable Quick Fix | ||||
|
|
The tileset defines the NOBLES_DEMANDS_* tiles as follows: * NA = 20:0 - gray * TIME_GOOD = 24:0 - yellow * TIME_WARN_1 = 28:0 - orange * TIME_WARN_2 = 32:0 - red * TIME_WARN_3 = 20:3 - green Clearly, these are in the wrong order - GOOD should be pointing at the Green icon, and WARN_1/2/3 should be pointing at Yellow/Orange/Red. This explains why it went from Green (not satisfied, long duration) to Yellow (satisfied) when you placed the chest in her room. The NOBLES_MANDATES_* tiles appear to have the same problem: * NA = 24:3 - gray * TIME_GOOD = 28:3 - yellow * TIME_WARN_1 = 32:3 - orange * TIME_WARN_2 = 20:6 - red * TIME_WARN_3 = 24:6 - green If you switch to ASCII mode, you should see the correct colors. |
|
|
Nice sleuthing! So it's just a UI thing which should hopefully be an easy fix. |
|
|
Looking at version 50.14, this appears to have been fixed. |
|
|
thanks! |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-11-28 22:46 | apoco | New Issue | |
| 2023-11-29 09:16 | Quietust | Note Added: 0041922 | |
| 2023-11-29 09:17 | Quietust | Note Edited: 0041922 | |
| 2023-11-29 09:45 | Quietust | Note Edited: 0041922 | |
| 2023-11-29 14:47 | apoco | Note Added: 0041924 | |
| 2023-11-29 15:50 | lethosor | Assigned To | => lethosor |
| 2023-11-29 15:50 | lethosor | Status | new => confirmed |
| 2024-02-15 14:12 | Quietust | Tag Attached: Probable Quick Fix | |
| 2024-10-04 09:56 | Quietust | Note Added: 0042383 | |
| 2024-10-04 22:30 | lethosor | Assigned To | lethosor => Toady One |
| 2024-10-04 22:30 | lethosor | Status | confirmed => resolved |
| 2024-10-04 22:30 | lethosor | Resolution | open => fixed |
| 2024-10-04 22:30 | lethosor | Fixed in Version | => 50.14 |
| 2024-10-04 22:30 | lethosor | Note Added: 0042384 |
