Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001896Dwarf FortressDwarf Mode -- Buildings, Generalpublic2010-05-16 07:332016-01-18 08:59
ReporterWyrm 
Assigned ToToady One 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSWindows XPOS Version
Product Version0.31.03 
Target VersionFixed in Version0.31.20 
Summary0001896: Custom workshops get assigned (a) key by default
DescriptionIn a custom building, if you do not specify a build key with the [BUILD_KEY:] tag, or specify NONE, then it gets assigned the 'a' key. All of them.
Steps To ReproduceMake a custom building. Do not include a [BUILD_KEY:] tag, or specify [BUILD_KEY:NONE]. Voila.
Additional InformationI see no reason why every workshop build should have a hotkey, as some can be rarely used and that hotkey only clutters the interface. Even if there were, the program should bark at us when not specified, and/or assign each a unique hotkey that doesn't collide with other workshops.
TagsIntentional/Expected?
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-05-16 07:33WyrmNew Issue
2014-01-27 14:39FootkerchiefTag Attached: Intentional/Expected?
2015-12-13 07:30HededeNote Added: 0033835
2015-12-13 08:21HededeNote Added: 0033837
2015-12-13 08:25HededeNote Edited: 0033837bug_revision_view_page.php?bugnote_id=0033837#r13641
2015-12-13 10:23HededeIssue Monitored: Hedede
2016-01-18 05:44HededeIssue End Monitor: Hedede
2016-01-18 08:59FootkerchiefStatusnew => resolved
2016-01-18 08:59FootkerchiefFixed in Version => 0.31.20
2016-01-18 08:59FootkerchiefResolutionopen => fixed
2016-01-18 08:59FootkerchiefAssigned To => Toady One

Notes
(0033835)
Hedede   
2015-12-13 07:30   
Probably fixed?

I made few copies of SCREW_PRESS and changed BUILD_KEY in each:

    [BUILD_KEY:CUSTOM_SHIFT_B] works as expected ("B")
    [BUILD_KEY:NONE] these three also work as expected (no key)
    [BUILD_KEY:]
    BUILD_KEY:
(0033837)
Hedede   
2015-12-13 08:21   
(edited on: 2015-12-13 08:25)
Fixed in 31.20. Bug is present in 31.19, but is not in 31.21.