Print

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

[Starver]

I was recently told (and then forgot to check for myself, just realised) that construction jobs are no longer (all else being equal) LIFO. Surprised me to be told that, my typical nanomanagement technique uses that as one of the elements, and I'd not noticed it detailing (edit: <- 'derailling'!) due to being wrong. But then the other elements might have made its absence inconsequential, which probably means I'm overusing such contongencies anyway.

Efficiency (least dwarf movements,/involvement, or especially least player interaction) isn't really my forté. I'm more on the lines of thorough and complete, in whatever I do, and never mind the amount of pause time it requires to poke and prod it that way.

[Mobbstar]

It might be worth considering that, should you see the minecart track through, burrows could be used to further split the haulers into "loaders" and "fetchers":  One group is in a big burrow that excludes the actual minecart track, focused on fetching logs towards the station.  The other group, possibly a single dwarf, is assigned to the track and the cargo area.

Is it possible to put several minecarts on the same track?  Will they block each other when pushed/guided?

[PatrikLundell]

You can put multiple carts on a track, but they will collide if going opposite ways when pushed/powered. I don't know if that also happens when guided. The typical solution is a round trip track.

I'm the one who mentioned to starver that things changed in 0.40.19 (I think), so it's not an independent data point, but yes, jobs are posted to the job board and dorfs take them based on some counter intuitive and not fully understood rules.
- For the same job type, priority seems to take priority (except for some bug cases), while geometric distance (possibly with a weight factor for the Z axis) is used, although I'm not clear of over which distances the algorithm uses when there's a dorf position, an item pickup position, and a drop off position.
- For tasks where the target effectively is an area (such as the possible positions around a tree trunk to be cut) the geometrically closest one is taken, including when that single tile isn't part of the burrow or when the dorf actually has to pass through the other eligible tiles to reach the position (to build a wall from the wrong side).
- For tasks of different kinds the logic is completely muddled. Harvesting beats anything (although hauling to the hospital might have a higher priority), capable of cancelling a dorf's 3 day trek to perform a priority 1 digging activity.
- Hauling away old bones beats hauling of freshly slain corpses (actually, they're probably at exactly the same priority, leading to dorfs filing past the carcass as they head toward the old bones that were geometrically closer when they took the task) as well as fresh meat. The meat reaches priority parity when the meat has rotten...
- Construction (walls, floors, etc.) has a lower priority than refuse hauling, as does bridge building and tree felling (regardless of priority).
- Some hauling appears to have higher priority than workshop jobs.
- Trade depot hauling beats even refuse hauling in priority.
- There doesn't seem to be any priority given to corpse bits of sapients (destined for the corpse stockpile) over refuse: they seem to have the same (high) priority, so there's no attempt to reduce the corpse view shock impact as early as possible.

[Salmeuk]

You can put multiple carts on a track, but they will collide if going opposite ways when pushed/powered. I don't know if that also happens when guided. The typical solution is a round trip track.

I'm the one who mentioned to starver that things changed in 0.40.19 (I think), so it's not an independent data point, but yes, jobs are posted to the job board and dorfs take them based on some counter intuitive and not fully understood rules.
- For the same job type, priority seems to take priority (except for some bug cases), while geometric distance (possibly with a weight factor for the Z axis) is used, although I'm not clear of over which distances the algorithm uses when there's a dorf position, an item pickup position, and a drop off position.
- For tasks where the target effectively is an area (such as the possible positions around a tree trunk to be cut) the geometrically closest one is taken, including when that single tile isn't part of the burrow or when the dorf actually has to pass through the other eligible tiles to reach the position (to build a wall from the wrong side).
- For tasks of different kinds the logic is completely muddled. Harvesting beats anything (although hauling to the hospital might have a higher priority), capable of cancelling a dorf's 3 day trek to perform a priority 1 digging activity.
- Hauling away old bones beats hauling of freshly slain corpses (actually, they're probably at exactly the same priority, leading to dorfs filing past the carcass as they head toward the old bones that were geometrically closer when they took the task) as well as fresh meat. The meat reaches priority parity when the meat has rotten...
- Construction (walls, floors, etc.) has a lower priority than refuse hauling, as does bridge building and tree felling (regardless of priority).
- Some hauling appears to have higher priority than workshop jobs.
- Trade depot hauling beats even refuse hauling in priority.
- There doesn't seem to be any priority given to corpse bits of sapients (destined for the corpse stockpile) over refuse: they seem to have the same (high) priority, so there's no attempt to reduce the corpse view shock impact as early as possible.

As long as this above list holds true, I believe the common practice of maintaining a caste of hauling-only dwarves is the simplest way to balance your need for job completion, and your need for things to go places. By simply adding more or less dwarves to either side (workers vs. haulers), you can mitigate some of the above 'muddled annoyances' and save yourself some headache.