View Issue Details

IDProjectCategoryView StatusLast Update
0009804Dwarf FortressDwarf Mode -- Transport/Haulingpublic2016-05-29 15:42
ReporterJustAnotherLurker Assigned Touser11 
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionduplicate 
PlatformWindowsOSWindows 7 Home PremiumOS Version64-bit
Product Version0.42.06 
Summary0009804: Hauled Minecarts able to collide with units?
DescriptionI've had two instances of injury from minecarts despite having none that are meant to be in motion. Most minecarts are either assigned to single-stop routes as quantum stockpiles, or sitting in a furniture stockpile.

The first case happened several years ago ingame, and I didn't really pay much attention to it, but one of my dwarves had his leg broken by a minecart. I believe the minecart in question was being hauled back into place after being grabbed for encrusting by my jewelers.

The second case occurred when I sold a couple of spare low-quality copper minecarts to the visiting elven merchants. Upon their departure, one of the merchants immediately had his head struck and crushed by a minecart. While the idea of an elf failing to properly secure a minecart on his pack yak and having it crush his head is highly amusing, I doubt it's intended.

Mind, even if this is unintended behavior, it may be interesting to leave in as accidents of the sort that happen when you combine booze-soaked midgets with heavy moving objects. Clumsy elves being a bonus.
TagsNo tags attached.

Relationships

duplicate of 0008211 new Minecart retains momentum while being hauled 

Activities

JustAnotherLurker

2016-05-28 22:46

reporter   ~0035328

Last edited: 2016-05-28 22:51

On further investigation, the minecarts were not actually sold. They were just piled in the trade depot. So, the clumsy elf is tripping over a minecart rather than having it fall off his yak?

Anyway, repeated save-scumming has thus far failed to reproduce the issue. Seeing as the fortress has run for 8 years with only the two minecart injuries, I don't expect it to be consistently reproducible, and the low rate probably means it should be ignored.

Loci

2016-05-29 15:16

viewer   ~0035331

possible duplicate 0008211

user11

2016-05-29 15:42

  ~0035333

Yes, unless you have a save that shows the problem to be materially different from 0008211, let's keep discussion of this there.

Issue History

Date Modified Username Field Change
2016-05-28 21:31 JustAnotherLurker New Issue
2016-05-28 22:46 JustAnotherLurker Note Added: 0035328
2016-05-28 22:51 JustAnotherLurker Note Edited: 0035328
2016-05-28 22:51 JustAnotherLurker Note Edited: 0035328
2016-05-29 15:16 Loci Note Added: 0035331
2016-05-29 15:42 user11 Note Added: 0035333
2016-05-29 15:42 user11 Relationship added duplicate of 0008211
2016-05-29 15:42 user11 Status new => resolved
2016-05-29 15:42 user11 Resolution open => duplicate
2016-05-29 15:42 user11 Assigned To => user11