Quote:
Originally Posted by PabloEdvardo
[You must be logged in to view images. Log in or Register.]
Thanks, appreciate the detail. Would love to see it fixed. Made bard kiting in PoF extra risky for no reason.
Edit: ah I just noticed your screenshot of the bash/hits landing. I'd never seen that evidence before. Not sure if kicks still make sense, but that might prove that bashes are actually intended (rip)
|
There was an invisible (no model / shadowed man type) NPC in lavastorm with no visible name, deep in the lava, that was targettable and could be engaged. Since it had no name, it registered as "Pain and suffering" to the client, which, in those screenshots without context has apparently led to some confusion in emulator development between that lavastorm NPC and actual pain and suffering damage.
But no, "pain and suffering" should not be punching anyone for 100 damage, bashing, or doing any type of standard melee combat. That is a specific NPC in actual combat, not the actual pain and suffering mechanic at work.
Quote:
Originally Posted by Ennewi
[You must be logged in to view images. Log in or Register.]
it is identified to others in text only as "!".
|
The ! is just the end of the sentence. When you're slain by anything it ends in an exclamation point. The name of that lavastorm NPC was a null value. Not even a space.
All actual records of real legitimate pain and suffering show exactly what was described above, where every tick it either misses you and you get your standard hp regen for that tick, or you get the message about bleeding to death and go deeper into the purple instead of regenning hp.
It's basically supposed to be a death save roll while you are in the purple, where there are two outcomes:
Outcome A) Pain and suffering tries you strike YOU, but misses: You regen your hp for the tick
Outcome B) YOU are bleeding to death: You lose the same amount of hp you would have regenned for the tick
No outcome should involve being struck for melee damage, or hit by special combat abilities.