0007848: Nobles demand impossible metals - Dwarf Fortress Bug Tracker

(0028338)
Quietust (reporter)
2014-08-04 20:20

It's possible that this bugfix only affects newly-created dwarves and doesn't apply retroactively to existing ones.

(0028339)
Loci (manager)
2014-08-04 20:20

Most likely this was fixed in 40.06 by preventing the selection of divine metals when a dwarf is generated. Since you copied over a dwarf from 40.05 with an already-generated preference for a divine metal, it really isn't all that surprising that his preference remained intact. It simply isn't worth the development work to ensure that save games are "fixed" when they are ported to a new version--that's effort that would be much better spent fixing long-term bugs than adding short-term convenience.

(0028340)
lethosor (manager)
2014-08-04 20:25

Has anyone been able to reproduce this in a fresh world in 0.40.06? If not, I'll close this in a couple days, unless we hear from Toady regarding whether this is intentional or not.

(0028341)
Dwarfu (manager)
2014-08-04 20:29

This may have been taken care of already (before being reported):
http://www.bay12forums.com/smf/index.php?topic=141736.msg5541864#msg5541864 [^]

(0028342)
crossmr (reporter)
2014-08-04 20:31

My mistake, I thought this was fixed in 40.05 not 40.06. So many bug fixes I was confused on when this one happened.

Yes he was a dwarf that came from the 40.05 save and wasn't a migrant post transfer.

(0028517)
lethosor (manager)
2014-08-07 06:31
edited on: 2014-08-07 06:32

All right, I'll resolve this. If anyone can reproduce this in a fresh 0.40.06+ world, please PM me or another manager on the forums to have the original report (0007590) reopened.

Issue History
Date Modified	Username	Field	Change
2014-08-04 19:48	crossmr	New Issue
2014-08-04 20:20	Quietust	Note Added: 0028338
2014-08-04 20:20	Loci	Note Added: 0028339
2014-08-04 20:25	lethosor	Note Added: 0028340
2014-08-04 20:25	lethosor	Assigned To	=> lethosor
2014-08-04 20:25	lethosor	Status	new => needs feedback
2014-08-04 20:26	lethosor	Relationship added	duplicate of 0007590
2014-08-04 20:29	Dwarfu	Note Added: 0028341
2014-08-04 20:31	crossmr	Note Added: 0028342
2014-08-04 20:31	crossmr	Status	needs feedback => assigned
2014-08-05 06:49	lethosor	Tag Attached: Intentional/Expected?
2014-08-07 06:31	lethosor	Note Added: 0028517
2014-08-07 06:31	lethosor	Status	assigned => resolved
2014-08-07 06:31	lethosor	Resolution	open => no change required
2014-08-07 06:32	lethosor	Note Edited: 0028517	View Revisions

Notes
(0028338) Quietust (reporter) 2014-08-04 20:20	It's possible that this bugfix only affects newly-created dwarves and doesn't apply retroactively to existing ones.

(0028339) Loci (manager) 2014-08-04 20:20	Most likely this was fixed in 40.06 by preventing the selection of divine metals when a dwarf is generated. Since you copied over a dwarf from 40.05 with an already-generated preference for a divine metal, it really isn't all that surprising that his preference remained intact. It simply isn't worth the development work to ensure that save games are "fixed" when they are ported to a new version--that's effort that would be much better spent fixing long-term bugs than adding short-term convenience.

(0028340) lethosor (manager) 2014-08-04 20:25	Has anyone been able to reproduce this in a fresh world in 0.40.06? If not, I'll close this in a couple days, unless we hear from Toady regarding whether this is intentional or not.

(0028341) Dwarfu (manager) 2014-08-04 20:29	This may have been taken care of already (before being reported): http://www.bay12forums.com/smf/index.php?topic=141736.msg5541864#msg5541864 [^]

(0028342) crossmr (reporter) 2014-08-04 20:31	My mistake, I thought this was fixed in 40.05 not 40.06. So many bug fixes I was confused on when this one happened. Yes he was a dwarf that came from the 40.05 save and wasn't a migrant post transfer.

(0028517) lethosor (manager) 2014-08-07 06:31 edited on: 2014-08-07 06:32	All right, I'll resolve this. If anyone can reproduce this in a fresh 0.40.06+ world, please PM me or another manager on the forums to have the original report (0007590) reopened.