Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0011279Dwarf FortressDwarf Mode -- Locationspublic2020-02-01 09:452020-02-05 12:51
ReporterTalvieno 
Assigned ToLoci 
PrioritynormalSeverityminorReproducibilityalways
StatusconfirmedResolutionopen 
PlatformPCOSWindowsOS Version10
Product Version0.47.01 
Target VersionFixed in Version 
Summary0011279: Values for locations vary between designating zones and using furniture to set locations
DescriptionUsing furniture to set a location doesn't seem to take smoothed floors or engravings into account, while using zones to set a location does. This makes zone-designated locations be worth four or five times as much.
Steps To ReproduceCreate two identical rooms, and create two locations from them - one with a statue, and one with a zone. The one with the zone will be worth more.
Additional InformationIn my recent temple, assigning a location via a statue garden only got the value up to roughly ☼1200, while assigning a location via a zone brought the total value up to roughly ☼6500.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0039771)
FantasticDorf (reporter)
2020-02-01 10:22

If the valuation of rooms are off due to furniture, issues 0010700 & 0010790 can count for omitted quality from ignored objects and displays (and to this case, terrain).

While a net value miscalculation can relate to 0001897 , anecdotally in 44.12 // 44.07 dwarves still express exaggerations to rooms like smallest size meagre quality ones as much better than you may expect them to.
(0039781)
Talvieno (reporter)
2020-02-01 14:38
edited on: 2020-02-01 14:39

Neither 0010700 or 0010790 apply in this case. This isn't relating to room "quality", but rather to the displayed monetary value. It's important in this release in particular because it seems like it's supposed to be difficult to get from ☼1 (shrine) to ☼2000 (temple) to ☼10000 (temple complex) It's possible the bug has been there for a while, in which case 0001897 might explain it and we simply never had the actual values available.


- Issue History
Date Modified Username Field Change
2020-02-01 09:45 Talvieno New Issue
2020-02-01 10:22 FantasticDorf Note Added: 0039771
2020-02-01 14:38 Talvieno Note Added: 0039781
2020-02-01 14:38 Talvieno Note Edited: 0039781 View Revisions
2020-02-01 14:38 Talvieno Note Edited: 0039781 View Revisions
2020-02-01 14:39 Talvieno Note Edited: 0039781 View Revisions
2020-02-05 12:51 Loci Assigned To => Loci
2020-02-05 12:51 Loci Status new => confirmed


Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker