Print

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

[Xolroc]

I can see why this would happen, but it does seem rather stupid to me.  If you've got idle dwarves, and "collect webs" set on repeat, multiple dwarves should go out to get webs until there are none left.

Putting a bug report here because Mantis is refusing to send my confirmation email, and the bug report forum is closed.

[blue emu]

Build several Looms.

[Drazinononda]

^ That

If you only have one loom, then you only have one active "Collect Webs" job. It's not a bug, it's intended behavior; all the workshops work the same way. You can't pack ten masons into the same workshop to all make blocks at the same time, either.

[Xolroc]

My point is that logically, since collecting webs doesn't involve actually being at the loom, multiple dwarves should be able to collect webs without requiring multiple looms.

[SharkForce]

and if your dwarfs don't have any place to turn it into thread when they get back, you would probably get constant job cancellation spam, see them drop the web, get caught in it if that actually makes it deploy, and break free... thus destroying the web.

which would be a much more annoying and wasteful way of only being able to generate one (useful) web collection job per loom, so... personally, i prefer the version where only one job is generated per loom.

[Brilliand]

and if your dwarfs don't have any place to turn it into thread when they get back, you would probably get constant job cancellation spam, see them drop the web, get caught in it if that actually makes it deploy, and break free... thus destroying the web.

which would be a much more annoying and wasteful way of only being able to generate one (useful) web collection job per loom, so... personally, i prefer the version where only one job is generated per loom.

No, they would just dump the web in the loom and leave it there for a dwarf with a bin to retrieve (in older versions, they would carry it to a bin themselves).  I build looms right next to clusters of webbing (where a GCS was recently slain) and don't allow weaving at those looms, and the resulting thread gets piled into bins and carried up to the weaver stockpile just fine.

Once the dwarf picks up the web, it becomes a thread, and it can't change back under any circumstances.

[gestahl]

Does changing the auto collect webs order help?

[Brilliand]

Does changing the auto collect webs order help?

If you want to do what I do, you have to disable both auto collect and auto loom, to prevent them from showing up in the same workshop.  Building the web collection loom(s) next to the webs is nice because each web collection job takes much less time, but it's still only one job at a time per loom.