Print

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

[Miles_Umbrae]

Instead of dorfs running from stockpile to workshop and back again with a single item, for example one gem or one seed, why not have them bring the entire bag/bin/pot/barrel to the workshop  and keep completing work-orders until the container runs out of items applicable to that workshops work-orders, for example bringing an entire leather-bin to the workshop and staying there making leather-bags until either the bin is empty or all orders for leather-bags are done, or a farmer bringing an entire pig-tail seed bag and keeps planting tile after tile until he/she runs out of seeds or farm-tiles.

[Dorsidwarf]

Don’t farmers already do this and that’s why we get the godawful farming cancellation spam as the farmers keep arriving at stockpiles to find that another dwarf ran off with the bag containing the seeds they wanted to use?

[Miles_Umbrae]

Not AFAIK.
The problem that exists now is that they grab the bag, go and plant one single seed, and the return the bag.

[Bumber]

What if another dwarf needs items from the container?

[Miles_Umbrae]

That's the only issue Bumber.
But which is more realistic; that a jeweller goes to the stockpile and picks up a single rough smoky quartz, a farmer only brings a single flax seed? Or that they pick up a whole bag/bin of the material to turn out multiple jobs while at the workshop?

[anewaname]

Bags and bins seem to have changed in behavior over time. From testing in 43.05, they will not be carried once their item name receives the <##> postfix for the stockpile number, unless they are not on their stockpile. They are placed on the stockpile and stay there.

The conflicts causing the job cancellations seem to occur only when two dwarf jobs are at specific stages at the same time, one dwarf with a "store item in bin" job, who has accumulated all of the items on the job list, will begin his walk to the container, which TSK's the container, which then causes the second dwarf, who's "take item from container for whatever" job is at a pre or post movement stage (he is ready to begin his walk, or has just ended his walk, to the container), he finds the container is currently TSK'd and the job cancellation occurs. There could be some variation of when the jobs check if the target bin is TSK'd, but it is basically those two jobs in conflict at specific stages of those jobs.

[Miles_Umbrae]

Ah, okay.
Thanks for updating me about that anewname .. (I'm still trying to catch up after about a year of not playing)