Provoke not working?

[Baelwulf]

Maybe it has a range of effectiveness limit like Collaborator?(With Collaborator you and your target must be within something like 8.8' of the target)

[Narse]

Provoke has a short activation time. It could be that the monsters path into, then out of your Provoke range before it goes off. People who have seen this happen with spells will know what I'm talking about. The monster is red, but your spell never hit it and you have no hate.

But when that happens your timer doesn't get used...

[Byrthnoth]

For spells it doesn't. But spells aren't JAs. Idk, I'm just throwing it out there.

[Furionstormrage]

Apparently if you voke near max range it can happen.

This, had it happen to me several times.

[Wenslydale]

If I had to guess, it's the max distance. Also, different zones seem to have different max distances. In Mount Zhaylom on puddings the max distance is 21.4 (using FFassist, not Windower. There is a discrepancy between the two at times.), but in Vunkerl on Tigers my max distance is 22.7. My only thought as to why this occurs is terrain/pathing options.

[Weeks]

I think that's mob size, not zone. Something huge like Behemoth gives you like an extra 5' on your actions.

[Stromgarde]

If I had to guess, it's the max distance. Also, different zones seem to have different max distances. In Mount Zhaylom on puddings the max distance is 21.4 (using FFassist, not Windower. There is a discrepancy between the two at times.), but in Vunkerl on Tigers my max distance is 22.7. My only thought as to why this occurs is terrain/pathing options.

If I had to guess, I'd imagine one calculates with sqrt(Δx^2+Δy^2), and the other uses sqrt(Δz^2+(sqrt(Δx^2+Δy^2)). Based on your experience with tigers, it sounds like the game is very forgiving with Δz. This is in addition to mob size, but I don't think that would make much of a difference between tigers and puddings.