Halifirien said:
Oh, and I'm stoked that WHM's Benediction cures status ailments. I'm also hoping the MPK change means people won't be able to steal Beastmaster claims.
Oh, snap, that's a good point. It probably won't work THAT well though because if a BST is probably going to lose claim on something, their pet probably has all the hate and the pet is the thing dying.
Rones said:
Now! That is only true because of this change. In the past you could still claim without getting hate and leave the mob attacking someone who couldn't fight it like I have described in three different examples.
Yeah, but, the "Accordingly" bit is literally just a direct zomgobvious blurb pointing out something painfully simple to understand - if you're a high enough level to understand claim stealing issues, you're also a high enough level to understand how
hate works and that if you do not have
hate, the mob won't attack you...
Rones said:
You couldn't take claim though unless it was unclaimed. If it was a claimed enemy, everything works like it always has. This is refering only to unclaimed enemies and how they are claimed. Reread the very first sentence:
Okay, let me go back and re-state exactly what I said in my last post, but this time with the tiny little explicit mention of "mob going unclaimed" for your benefit. Except with a slight modification because I made an error while typing it.
Tagrineth said:
What if you were to take claim by overriding my enmity just slightly after something happens that causes the mob to go yellow, then immediately Cure IV myself? Or you? Or pop Invincible (I know, bad choice, cause the damage would be negated anyway, but the hate draw is significant)?
I'm sorry for skipping the italicised bit in the first place, I assumed you'd be able to fill that in since you're such a hyper genius and I'm so ignorant.
Regardless of my wording, though, you still bypassed my question.
If that situation were to happen, and I boosted my enmity past yours again after you take the unclaimed mob,
do I get attacked? But that seems to contradict the update notes quite explicitly.