Surprise fix in the update?

[Daniel_Hatcher]

They just need to delete pet jobs altogether. This is an MMO. Solo elsewhere.

In the same process they'd need to delete other jobs that also break this tradition. Such as: DD's that are able to Tank.

Pet jobs shouldn't be required to be solo jobs, this is the fault of SE, if they made pets useful in party/alliance situations then they wouldn't be, also players make it so by not inviting them to anything due to there being others jobs that do it better.

[Sargent]

To my knowledge, we still lose the timer if the mob dies before Blood Pact: Rage goes off, so SMN is still in the same boat as BST on that. This only affects support abilities which shouldn't be interrupted when the mob dies anyway.

[Babekeke]

Ward as well, unless I missed something?

That's what this whole thread is about... they just fixed it. Though the quote is that "Blood Pact: Ward abilities will no longer be interrupted if the mob dies before the action goes off", this may only actually apply to enhancing wards, not offensive wards.

[Arcon]

That's what this whole thread is about... they just fixed it. Though the quote is that "Blood Pact: Ward abilities will no longer be interrupted if the mob dies before the action goes off", this may only actually apply to enhancing wards, not offensive wards.

I thought they fixed Ward being interrupted when the mob dies, not timers being reset, unless I misinterpreted that. So timer reset should still be broken for both Rage and Ward.

[Camiie]

I don't see why they should get kudos for this. They fixed what never should have been broken to begin with, and it took them a decade to do so.

[Flyinghippress]

I thought they fixed Ward being interrupted when the mob dies, not timers being reset, unless I misinterpreted that. So timer reset should still be broken for both Rage and Ward.

Previously when you used a BP:Ward and the monster died before it went off, the move would be stopped and the timer reset. Now when you use a BP:Ward and the monster is killed before it goes off, the move will still go off.

With BP:Rage, if the monster is killed before the ability goes off, the timer is reset and the ability obviously doesn't go off. The fix they made to BP:Rage months ago was that if you used the ability and your avatar was out of range, it wouldn't reset the timer like it used to.

[Herby]

Previously when you used a BP:Ward and the monster died before it went off, the move would be stopped and the timer reset. Now when you use a BP:Ward and the monster is killed before it goes off, the move will still go off.

With BP:Rage, if the monster is killed before the ability goes off, the timer is reset and the ability obviously doesn't go off. The fix they made to BP:Rage months ago was that if you used the ability and your avatar was out of range, it wouldn't reset the timer like it used to.

Don't forget that there are also monster-targeted ward pacts! I think he is right when saying the timer reset is still there for monster targeted ward pacts.

[Arcon]

Don't forget that there are also monster-targeted ward pacts! I think he is right when saying the timer reset is still there for monster targeted ward pacts.

This is what I meant. I know they fixed one thing, but there's still another and (in my opinion) more serious matter they need to focus their attention on.

[Kysaiana]

It's cool that they fixed Wards stopping when a mob dies. But it's lame that you still lose Rage timer when a mob dies. Same goes for healing breath on wyvern, adventuring fellow spells, and TP moves on BST pets. Fixing one part of the issue is nice and all, but why are the rest ignored? It's kinda like plugging up a small leak in a dam when next to it is a huge hole.

[Mirage]

I'm starting to think that avoiding enemy-targeted pet skills from being wasted is impossible without rewriting half the server software. They've simply painted themselves into a corner and can't get around it.

I dunno about them, but that would be too awkward for me to admit to it, at least!