|
|
Is it possible to designate the workshop? Do you have unoccupied dwarves with the required labor enabled? A save uploaded to http://dffd.bay12games.com would be helpful. |
|
|
|
Like I said, I activated MANY dwarves with dyeing. About half the fort has dyeing, if not more, and I often have many idlers. UPDATE! Though it took 2 strait years, it turns out that I saved the game, quit, and restarted. Suddenly they built the workshops! I thought that must be the workaround, so I build two more... it's been another year, and they haven't touched them. I tried repeatedly saving and quitting and re-entering, but it's all a no-go. E-flipping-gads... But at least I am up to 10 dyers shops total now! Only 9 more to go to meet my desired number ^.^
|
|
|
|
A save would be helpful so Toady can reproduce this bug on his end (given that it doesn't seem to be common). Are you using any labor-related utilities like autolabor, autohauler, or workflow? |
|
|
|
No, no utilities. Heck, I haven't even added any of my usual mods. I'm just playing vanilla. |
|
|
|
OH! I figured out what was going on! The problem had begun to extend to all parts of the fort, and it was obvious something was amiss: I had consistently 20 idlers yet nobody would haul a rotting corpse to an empty stockpile. This happened a number of times in a year, and that is just one notable example: everything in the fort was slowing down, a month's worth of work was taking a year... so i began paying attention to the cancellations. It's all collect webs: no web, or weave thread: no dyed thread. It had to do with the auto-collect-webs task at my 32 looms. My underground was at one time producing vast quantities of web, so I had built a huge number of looms to maximize production. These looms would generate web-collection tasks and the dwarves would take on the task. Then, they would find that there was no viable web, and the task would be cancelled. I have my dwarves somewhat restricted due to an increasing population of forgotten beasts, so web has gone way down. In the mean time, the cancelling dwarf has some lag between cancellation and choosing any new task. Also in the mean time, the collect webs task refreshes. The dwarf takes the task, realizes there's no web, and cancels. There's a lag time between cancellation and selection of a new task. Also, in the mean time, the collect webs task refreshes. The dwarf takes the task, realizes there's no web, and cancels. There's a lag time... you get the picture.
I just greatly sped up everything in my fort, and freed up all those perpetual idlers, by turning auto-web collecting off, and auto weaving off. Now I'll just do these things intermittently: build up a bunch of dyeable thread, then let them weave it all, and only turn on web collection if there's a lot of web about. |
|
|
|
That sounds like 0002869, then. I think that the delay between accepting jobs is intentional to reduce the amount of cancellation spam, but I think that dwarves only accepting these jobs is an issue. |
|
