Divine Arbitration (its broke)

[shamlove]

So the last week ive been playing my freinds cleric and every time i used Arbitrate on someone who was very low health you saw the reg things. everyones health goes down and theirs goes up..

but wait. then they get one hit and poof are dead... reminds me of the cheal bug, anyone else getting this crap? and VI wanna fix it pleasethx.

[Sirensa]

It's not broken - it's lag.

[Destinae]

It's called latency, the updates are probably client side and the actual heal is serverside...

[Samus Aran]

....

(Credit goes to Attrib)

[Slysx]

This happens alot, It isn't usefull with less then 200 HP, it will always do that up/death thing.

[Makata]

Unless it's being used to save an unvirtued caster.. using DVA on an almost dead group member is stupid. You save that person's life.. for about 3 seconds. If you can't land the follow up heal, you just took a nice dump on everyone's hp to stall the inevitable.

Off-topic, I know. Sorry ;p

[kasey]

HAHAHAHAHAH @ jerle

[Suineg]

And this is why people should not play clerics if they don't know what they are doing. I almost stopped reading the moment I saw:

ive been playing my freinds cleric

/shrug

[Jhentar_AN|Trib]

Bah Lukee, you played a friend's cleric the other day

[Karenne]

This happens alot, It isn't usefull with less then 200 HP, it will always do that up/death thing.

It has nothing to do with the number of hps, but it has everything to do with the hit(s) received between the divine arbitration casting and the server *echo* to that casting on the rest of the group.

And yes, it's extremly annoying, and make the skill almost useless in certain conditions.

[Suineg]

Haha Jhentar that doesn't count when my main is a cleric

[Ukerric]

Originally posted by Karenne
It has nothing to do with the number of hps, but it has everything to do with the hit(s) received between the divine arbitration casting and the server *echo* to that casting on the rest of the group.

Welcome to the world of authoritative client.

The problem is that the client can decide you are dead. It does so because it keeps track of your health, and when you go below -10 (the old AD&D neg-HP rules), you then die... and the client notifies the server: "I've just died, please make a corpse at X/Y, and gate me to bind point".

The real point isn't the echoing to the rest of the group, it's echoing to the "healed" group member. Because that's the group member who decides he died.

[Sentient]

This is incorrect, the client doesn't decide anything. The server is always correct and calls all the shots.

This is why bugs like fake mana drain exist. The client assumes it was hit by the dot and predicts that the server will drain your mana. When you cast a spell (usually insta-click), the server updates your client with the correct mana amount.

This is the same for HP, only the server can decide when you die.

The server only updates HP bars once per tick or if you directly damage the player/mob (nuke). This means, the server has already calculated hits that you won't see for another 1-6 seconds. If you hit DA and aren't due for a HP update for 5 more seconds, the player could be receiving his final blow on the server-side already.

If you died on the client side, the server would do a sanity check and say, nothing hit you / you have no dots, it is impossible that you are dead, it would then update the client with your correct current health. It is the exact same thing it does when the client reports you oom and you cast an item spell.

[Megumi]

It is bugged..

Its not something constant, but id say 1/4 times I use it; whoever has the least hitpoints in the group will not get healed regardless of their range. I normally use it right after ressing a group member if we arent fighting. It saves me alittle mana. Its kinda funny to be standing next to someone I'm grouped with, that has 20% health and Divine Arb ging off does nothing to them.

This started happening about 2-3 weeks ago, maybe more.

[Kodylan]

I did have it happen once. But I think it was just poor timing on the attempted heal, not lag. That killing blow probably hit the person right as your heal did, which killed them - you just saw what your client was telling you before it actually updated.