- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
Difference between revisions of "v0.31:Dwarf cancels Store Item: Item inaccessible"
(burrows, from first-hand experience and experiments.) |
m (Clarification of Stockpile issue) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
This occurs when a dwarf is fetching an item and the path between the dwarf and the item is suddenly blocked. | This occurs when a dwarf is fetching an item and the path between the dwarf and the item is suddenly blocked. | ||
| − | For instance, the item is in a room and you lock all the doors between the dwarf and the item. This error can also crop up if the item is underwater, which gets annoying when one dwarf drowns and the spouse constantly wants to retrieve the items (spouses share ownership of each other's items). | + | For instance, the item is in a room and you lock all the doors between the dwarf and the item. This error can also crop up if the item is underwater, which gets annoying when one dwarf drowns and the spouse constantly wants to retrieve the items (spouses share ownership of each other's items). It can also happen if a dwarf dies while in a region your civilians are forbidden to enter - until the restriction is lifted (or the corpse is forbidden), an endless stream of "Store Item in Tomb" jobs will be generated and immediately cancelled. |
| − | It can also happen if your dwarves are assigned to a | + | It can also happen if your dwarves are assigned to a [[burrow]] with a stockpile and there are items to be stored on that stockpile from outside of the burrow. Jobs to store items are generated by the stockpile and even if only some of your dwarves are burrow-restricted they will try to take the job (because only burrow location of job-generating building - stockpile - is checked at this moment) and fail with this message when they realize they can't go there. Stockpiles don't stop generating fetch jobs for items no one is permitted to go to but do stop when there is no actual path (e.g. a locked door). |
| − | In all cases of repeated spam it is recommended to determine/guess what item is causing this and forbid it. You may have luck with looking into {{k|j}}jobs screen and {{k|v}}examining jobs or disabling your | + | In all cases of repeated spam it is recommended to determine/guess what item is causing this and forbid it. You may have luck with looking into {{k|j}}jobs screen and {{k|v}}examining jobs or disabling your [[stockpiles]] one at a time to see which one will stop the spam. |
{{Errors FAQ}} | {{Errors FAQ}} | ||
Latest revision as of 12:48, 17 January 2012
| This article is about an older version of DF. |
This occurs when a dwarf is fetching an item and the path between the dwarf and the item is suddenly blocked.
For instance, the item is in a room and you lock all the doors between the dwarf and the item. This error can also crop up if the item is underwater, which gets annoying when one dwarf drowns and the spouse constantly wants to retrieve the items (spouses share ownership of each other's items). It can also happen if a dwarf dies while in a region your civilians are forbidden to enter - until the restriction is lifted (or the corpse is forbidden), an endless stream of "Store Item in Tomb" jobs will be generated and immediately cancelled.
It can also happen if your dwarves are assigned to a burrow with a stockpile and there are items to be stored on that stockpile from outside of the burrow. Jobs to store items are generated by the stockpile and even if only some of your dwarves are burrow-restricted they will try to take the job (because only burrow location of job-generating building - stockpile - is checked at this moment) and fail with this message when they realize they can't go there. Stockpiles don't stop generating fetch jobs for items no one is permitted to go to but do stop when there is no actual path (e.g. a locked door).
In all cases of repeated spam it is recommended to determine/guess what item is causing this and forbid it. You may have luck with looking into jjobs screen and vexamining jobs or disabling your stockpiles one at a time to see which one will stop the spam.