April 3, 201510 yr See screenshot. It seems that the Gul with a DR of 0.0 takes no damage when hit, instead of the expected 21. Or the text in the stats window is wrong. Anyway, I am pretty sure than 21 - 0 should be larger than 0
April 3, 201510 yr That was a miss. Look at the "Accuracy - Defense" score. EDIT: I'm dumb and blind; ignore my post Edited April 3, 201510 yr by Insolentius
April 3, 201510 yr That was a miss. Look at the "Accuracy - Defense" score. No, he rolled a 90, minus 25, for a result of 65. That's a hit.
April 3, 201510 yr That was a miss. Look at the "Accuracy - Defense" score. No, it was a hit. Notice the text "(Hit)". It seems that the Gul with a DR of 0.0 takes no damage when hit, instead of the expected 21. The damage was 0.0 because your target is already dead. Sometimes when a hit happens very soon after a target has been defeated it gets into the combat log, because the game hasn't had time to fully appreciate the dead status of the target. In those cases you will see a hit for 0.0 damage in the combat log.
April 3, 201510 yr That was a miss. Look at the "Accuracy - Defense" score. I'm confused. The diaglog says "Hit" Accuracy was way lower than defnse, true. Yet the roll was a 90, with a final being 65, a hit. What am I missing? Is there an instant "miss" if your Acc - Def is a negative number?
April 3, 201510 yr That is because Gul in question was already dead, but not before Durance started hit animation and because it was dead it could not take more damage anymore, which it show that damage done is 0. As you can see from your auto-pause information that Durance target was destroyed. Edited April 3, 201510 yr by Elerond
April 3, 201510 yr That was a miss. Look at the "Accuracy - Defense" score. No, it was a hit. Notice the text "(Hit)". It seems that the Gul with a DR of 0.0 takes no damage when hit, instead of the expected 21. The damage was 0.0 because your target is already dead. Sometimes when a hit happens very soon after a target has been defeated it gets into the combat log, because the game hasn't had time to fully appreciate the dead status of the target. In those cases you will see a hit for 0.0 damage in the combat log. Ah, ok. Minor bug in the combat log due to order of events. Log posted an entry after the combat was actually resolved. Perhaps an enhancement would be to indicate "Target Dead", or, not log that event at all. Edited April 3, 201510 yr by Plazmid
April 3, 201510 yr That is because gul in question was already dead, but not before Durance started hit animation. Durance try to overkill the gul. (to make sure he don't stand up). Yes i know, my english sux.
April 3, 201510 yr Author That was a miss. Look at the "Accuracy - Defense" score. No, it was a hit. Notice the text "(Hit)". It seems that the Gul with a DR of 0.0 takes no damage when hit, instead of the expected 21. The damage was 0.0 because your target is already dead. Sometimes when a hit happens very soon after a target has been defeated it gets into the combat log, because the game hasn't had time to fully appreciate the dead status of the target. In those cases you will see a hit for 0.0 damage in the combat log. Oh, that explains it. This reduces it to a minor display bug. Thanks for the explanation!
Create an account or sign in to comment