View Issue Details

IDProjectCategoryView StatusLast Update
0006467Dwarf FortressProjectilespublic2014-05-10 21:43
ReporterDwarfChef Assigned To 
PrioritylowSeverityminorReproducibilityhave not tried
Status newResolutionopen 
PlatformPC 
Product Version0.34.11 
Summary0006467: Falling damage before obstacle report
DescriptionNot sure if the falling physics is working as expected. And, damage reports happen before or with no collision report.

Dwarf is on a bridge 2 z levels above ground, tries to build an unsupported floor which collapses. Single-stepping through the aftermath, I see:

Dwarf goes UP one z-level, above the space where he had been standing. Dwarf goes back down one z-level, is now on top of the bridge where he was standing. Dwarf goes sideways 2 squares, is now off the bridge, starts falling. Dwarf falls 2 z-levels, hits ground, stays there until he gets up.

In the log, the message order is 'takes damage', 'caught in dust', 'hits obstacle', 'takes more damage'. If the first 'full force of impact' is from hitting the bridge, there is no slam into obstacle message. If it is from dust or hitting the ground, the caught in cloud and slam message are after the damage report. If the "section of cavern has collapsed" message did the damage, then it makes sense but is unclear.

Also, does the dust push dwarves? Is it possible for dust to push the dwarf off the bridge between the tick when the dwarf enters the bridge square and the tick where the dwarf would hit the bridge? I'm not sure why the dwarf got moved sideways and how it didn't "slam into an obstacle" the bridge.

Steps To ReproduceBuild a bridge or grate into a nice open area 2-z above the ground. Build an unsupported floor off the end of that. Follow the flying dwarf.

I haven't had time to reproduce yet, will get to it later.
Additional InformationThe relevant bits of the log:

A section of the cavern has collapsed!
`L_Glass' â€ıngizcatten, Glassmaker cancels Construct Building: Unconscious.
The dwarves suspended the construction of Wall.
The Glassmaker's left lower leg takes the full force of the impact, bruising the fat through the (pig tail fiber robe)!
The Glassmaker's upper body takes the full force of the impact, bruising the skin through the (sheep wool cloak)!
The Glassmaker is caught in a cloud of boiling magma!
The Glassmaker is caught in a burst of red sand!
The Glassmaker is caught in a cloud of boiling magma!
The Glassmaker slams into an obstacle!
The Glassmaker's left hand takes the full force of the impact, bruising the muscle through the (llama wool left mitten)!
The Glassmaker's left lower arm takes the full force of the impact, bruising the muscle through the (sheep wool cloak)!
The Glassmaker is caught in a burst of red sand!
TagsIntentional/Expected?

Activities

UristDaVinci

2014-04-21 22:30

reporter   ~0024720

Suggested title change:
The message "The X slams into an obstacle!" will not be added to the combat log unless if it would be the first thing recorded/if the unit was not in combat.

-If the unit is already in combat prior to the cave-in (i.e. is in a sword fight), all slam messages appear.
-If the first harmful thing to happen to that unit was the cave-in, the first slam message is not recorded. I guess the first injury to the unit puts it in combat mode, allowing future slam messages to be recorded.

UristDaVinci

2014-04-21 22:33

reporter   ~0024721

Fun trivia related to cave-in dust:
- The dust appears to randomly teleport creatures to a location above and to the side of where they were standing. It may be limited to destinations that are obscured from view by dust (unproven). It then simply drops the creatures.
- The creatures don't seem to gain any lateral velocity.

UristDaVinci

2014-05-10 21:42

reporter   ~0024752

Not a bug.

In the init file announcements.txt there is the line:
[UNIT_PROJECTILE_SLAM:A_D:UCR_A]

UCR_A means:the announcement will be associated to any active unit combat/hunting/sparring reports, but if there are no reports it will not create one.

If the bug reporter wants them to appear in the combat log always, change the line to:
[UNIT_PROJECTILE_SLAM:A_D:UCR]

Add Note

Note

Issue History

Date Modified Username Field Change
2014-04-18 09:13 DwarfChef New Issue
2014-04-21 22:30 UristDaVinci Note Added: 0024720
2014-04-21 22:33 UristDaVinci Note Added: 0024721
2014-05-10 21:42 UristDaVinci Note Added: 0024752
2014-05-10 21:43 UristDaVinci Tag Attached: Intentional/Expected?