0004000: Dwarf Digging Priority ignores depth

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0004000

Dwarf Fortress

Dwarf Mode -- Jobs, Designations

public

2011-02-17 10:32

2011-03-19 10:19

Reporter

idgarad

Assigned To

Logical2u

Priority

normal

Severity

minor

Reproducibility

always

Status

resolved

Resolution

duplicate

Platform

ALL

OS Version

ANY

Product Version

0.31.19

Target Version

Fixed in Version

Summary

0004000: Dwarf Digging Priority ignores depth

Description

I build a 3 level deep moat and flood only the bottom level. But designating multiple levels of channels the dwarves dig down immediately to the lowest level, dig around a bit then proceed back up only to have cave ins. While not severe it greatly inhibits digging shafts of 2x2 or larger. This makes it difficult to queue up a digger dwarf to dig down a 10 z depth 3x3 shaft for instance.

Steps To Reproduce

channel a moat of 3 width (make a donut for instance)
Go down a level
channel the same moat
Watch in horror...

Additional Information

This is minor in the fact that if we are trying to queue up (for instance using quickfort) a fortress it would be nice that the dwarves first complete the digging on the current level before going down.

Programatically it looks like they are running through a nested loop where it goes

for each y
  for each x
   for each z

to an extent. Where as doing
for each z
for each x
  for each y

you resolve the cave in issue (simplification). Altering this may also resolved 3x3 stairwells which allow each level to be complete before descending the next level.

I never actually noticed this until .19 since I A: started building moats and B: starting using quickfort for build macros.

Tags

behaviour, channel, collapse, designation, Z axis

Attached Files

Relationships

duplicate of

0001463

new

Dwarves prioritize tasks oddly

Notes
(0015193) Logical2u (manager) 2011-02-17 10:59	Dwarf pathfinding is prioritized strangely is the main gist of your report I gather, which is covered under 0001463.

Issue History
Date Modified	Username	Field	Change
2011-02-17 10:32	idgarad	New Issue
2011-02-17 10:35	idgarad	Tag Attached: annoying
2011-02-17 10:35	idgarad	Tag Attached: behaviour
2011-02-17 10:35	idgarad	Tag Attached: channel
2011-02-17 10:35	idgarad	Tag Attached: collapse
2011-02-17 10:35	idgarad	Tag Attached: designation
2011-02-17 10:35	idgarad	Tag Attached: Z axis
2011-02-17 10:59	Logical2u	Note Added: 0015193
2011-02-17 10:59	Logical2u	Relationship added	duplicate of 0001463
2011-02-17 10:59	Logical2u	Status	new => resolved
2011-02-17 10:59	Logical2u	Resolution	open => duplicate
2011-02-17 10:59	Logical2u	Assigned To	=> Logical2u
2011-03-19 10:19	Logical2u	Tag Detached: annoying