PDA

View Full Version : Stabilization doesn't work [v 3.0.10]



Callum
February 16th, 2015, 22:08
It appears that the stabilization roll happens every turn that a creature is below 0 hp, regardless of whether it's already dead or it's stable. It seems odd that it adds a 'Stable' effect on a successful roll, but doesn't check for that effect before rolling again. (I noticed this when advancing the Combat Tracker through 10 rounds in one go.)

Andraax
February 17th, 2015, 03:48
What ruleset?

Mistamichal
February 17th, 2015, 05:34
That would be D&D 5e

Callum
February 17th, 2015, 13:53
Sorry, I should have given the ruleset - this was in 3.5E/PFRPG.

Mistamichal
February 18th, 2015, 00:12
Ahhh.

Moon Wizard
February 26th, 2015, 03:04
I just tested this on the latest 3.0.11, and it appears to be working.

Do you have any extensions running?
Was the Stable effect applied by the automated code, or manually? (must be "Stable", same capitalization, no spaces)
Can you provide a step by step to recreate?

Thanks,
JPG

Callum
February 27th, 2015, 11:26
I only have the "Language Chat" extension running. The 'Stable' effect was applied by the automated code. Here's the relevant section of the log:-


Goblin Warrior 2: [STABILIZATION] [at -10] [FAILURE] [1d20-9 = 0]
Damage [1] -> [to Goblin Warrior 2]
Goblin Warrior 2: [STABILIZATION] [at -10] [FAILURE] [1d20-9 = -4]
Damage [1] -> [to Goblin Warrior 2] [DEAD]
Goblin Warrior 8: [STABILIZATION] [at -7] [FAILURE] [1d20-6 = -4]
Damage [1] -> [to Goblin Warrior 8]
Goblin Warrior 2: [STABILIZATION] [at -10] [FAILURE] [1d20-9 = 7]
Damage [1] -> [to Goblin Warrior 2]
Goblin Warrior 8: [STABILIZATION] [at -7] [FAILURE] [1d20-6 = 2]
Damage [1] -> [to Goblin Warrior 8]
Goblin Warrior 8: [STABILIZATION] [at -7] [SUCCESS] [1d20-6 = 12]
Effect ['Stable'] -> [to Goblin Warrior 8]
Goblin Warrior 8: [STABILIZATION] [at -7] [SUCCESS] [1d20-6 = 11]
Effect ['Stable'] -> [ALREADY EXISTS] [on Goblin Warrior 8]
Goblin Warrior 8: [STABILIZATION] [at -7] [FAILURE] [1d20-6 = -3]
Damage [1] -> [to Goblin Warrior 8]
Goblin Warrior 2: [STABILIZATION] [at -10] [FAILURE] [1d20-9 = 9]
Damage [1] -> [to Goblin Warrior 2]
Goblin Warrior 8: [STABILIZATION] [at -7] [SUCCESS] [1d20-6 = 11]
Effect ['Stable'] -> [ALREADY EXISTS] [on Goblin Warrior 8]
Goblin Warrior 8: [STABILIZATION] [at -7] [FAILURE] [1d20-6 = 3]
Damage [1] -> [to Goblin Warrior 8]
Goblin Warrior 2: [STABILIZATION] [at -10] [FAILURE] [1d20-9 = -2]
Damage [1] -> [to Goblin Warrior 2]
Goblin Warrior 8: [STABILIZATION] [at -7] [FAILURE] [1d20-6 = 7]
Damage [1] -> [to Goblin Warrior 8] [DEAD]
Goblin Warrior 2: [STABILIZATION] [at -10] [SUCCESS] [1d20-9 = 10]
Effect ['Stable'] -> [to Goblin Warrior 2]
Goblin Warrior 8: [STABILIZATION] [at -7] [FAILURE] [1d20-6 = -3]
Damage [1] -> [to Goblin Warrior 8]
Goblin Warrior 8: [STABILIZATION] [at -7] [FAILURE] [1d20-6 = 5]
Damage [1] -> [to Goblin Warrior 8]
Goblin Warrior 2: [STABILIZATION] [at -10] [FAILURE] [1d20-9 = 3]
Damage [1] -> [to Goblin Warrior 2]
Goblin Warrior 2: [STABILIZATION] [at -10] [FAILURE] [1d20-9 = 0]
Damage [1] -> [to Goblin Warrior 2]
Goblin Warrior 2: [STABILIZATION] [at -10] [FAILURE] [1d20-9 = -4]
Damage [1] -> [to Goblin Warrior 2]
Goblin Warrior 2: [STABILIZATION] [at -10] [FAILURE] [1d20-9 = 8]
Damage [1] -> [to Goblin Warrior 2]

So you can see that it keeps rolling, even after the 'Stable' effect has been applied - and then tries to apply the effect again, or adds more damage. This eventually results in the death of the 'Stable' goblin - but even that doesn't stop the stabilization rolls!

I'll try to recreate it and give you a step-by-step, but I'm not sure when I'll get the chance to do that. It's worth noting (as I said in my original report) that this was using the "advance 10 rounds" option from the Combat Tracker. It looks as though this isn't actually entirely sequential - all the rolls are apparently made at the same (initial) value, despite the damage being added (or the 'Stable' effect applied); on the other hand, it does know not to apply the effect a second time, and also knows when enough damage has been dealt to kill the goblin.

Moon Wizard
February 27th, 2015, 19:56
I missed the advance 10 rounds detail above, but I bet that's the issue. All the rolls will be triggered at once, since there is no way to advance a round, wait for all rolls to complete, then advance a round again automatically. In the end, it should be correct, just not optimal.

Cheers,
JPG

Callum
February 27th, 2015, 21:34
Unfortunately, it doesn't end up correct, as you can see from the example above. The goblins both end up dead and stable! Also, all ten rolls are made at the same value - when it should depend on the current damage, each round.

Nickademus
February 27th, 2015, 22:03
Out of curiosity, what is the Con score of the goblins? If it is 10, change it to 13 and try again.

Moon Wizard
February 28th, 2015, 02:54
You're right, because the failed rolls decrease hit points; then the damage is still applied even though some rolls succeed.

Hmm, there's no mechanism currently to have chained rolls, so this will be an issue for awhile. This will apply to any automatic trigger rolls (mainly death saves (5E/4E), stabilization rolls (3.5E), and effect auto-saves (4E)).

Regards,
JPG