Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0011443Dwarf FortressDwarf Mode -- Interface, Workshop Profilespublic2020-03-07 19:332020-03-08 14:42
normalcrashhave not tried
DefaultWindows 10 Home1909
0011443: Crash when certain item names are trying to be displayed
In the workshop profile window, certain items will consistently crash the game when their name is trying to be displayed.
For my tests, I tried to find plump helmets by filtering "PLU" (game crashed before i could get further), "LUM" (same as before), and by simply scrolling to its page manually. The second to last page and seemingly any pages containing items after the letter M will crash the game as well.
1. Go to any workshop
2. Go to Workshop Profile menu
3. Go to Work Orders menu
4. Create a condition for a work order (the top and bottom workshops should already have orders)
5. Add a material condition and filter "LUM", "PLU", or scroll from the top all the way down to past M or go to the second to last page
Save File: http://dffd.bay12games.com/file.php?id=14907 [^]

I have had this problem with 2 new worlds after the v47 update.
No tags attached.
Issue History
2020-03-07 19:33fiendNew Issue
2020-03-07 19:38fiendNote Added: 0040327
2020-03-07 19:42fiendNote Edited: 0040327bug_revision_view_page.php?bugnote_id=0040327#r16397
2020-03-08 04:29Shonai_DwellerNote Added: 0040328
2020-03-08 14:42fiendNote Added: 0040333
2020-03-08 14:43fiendNote Edited: 0040333bug_revision_view_page.php?bugnote_id=0040333#r16399

2020-03-07 19:38   
(edited on: 2020-03-07 19:42)
I forgot to label reproducibility as "always", as well as mentioning that my game is completely unmodded except for a few edits to the init and d_init files.

init changes being disable intro, lower volume, change display FPS to 144 (to match monitor)
d_init changes being enabling seasonal autosave. I did this after the first crash due to this bug after losing 4 hours of progress.

2020-03-08 04:29   
Duplicate of 0009905?
2020-03-08 14:42   
(edited on: 2020-03-08 14:43)
It does appear to be a duplicate, even down to the error log, my mistake.
Although it does appear that the other issue didn't attach a save file like I did, so this issue may still be helpful