Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Eschar]

For some reason, the game fluctuates between knowing how many chains there are or not. For example, a job being cancelled because the dwarf "needs chain" despite a chain having just been forged and there being no other jobs that it could have been used in. A bit later, however, the chain will be "found," and will be used if I reassign the job.

DF 44.10, no mods.

[Dutchling]

a chain having just been forged

The chain is probably being used by another dwarf for a task. The task is moving it to a stockpile.

You can check by loo`k`ing (actually, you will probably need to look at the workshop that made it with `t`) at the chain and see if it has "[TSK]" next to its name. If you don't want to wait for the hauling dwarf to be done, pause the game and then forbid and unforbid the chain. This will stop the hauling task, giving you time to build the chain somewhere.

[PatrikLundell]

And adding to Dutchling's answer: if the chain is stored in a bin it becomes unavailable while someone locks the bin for access because they're in the process of putting something else into it or remove something else from it. Don't use bins unless you know what you're doing, or you'll get cancellation issues.
If you're using minecart QSPs you'll get two jobs locking the chain: first to move the chain to the feeder stockpile and then to move it to the minecart.
If you're in dire need of something immediately after it has been made, you can remove that item category from the stockpile(s) temporarily, or block transfer from the workshop by using stockpile links (the latter is likely to bite you in the back, though, as a common reason for "job never done" issues if incorrect stockpile linkage, failing to link a stockpile containing one of the source ingredients, frequently barrels, to the workshop).