2890: Somethin wrong about named mobs set to"X can't be confused!"

Reported by 🌟 Greenpeace at Mon, 26 Dec 2016 13:24:34 UTC
gamemechanic bug
new
2 confirmations

Description

As far as i can tell most named/quest/epicmobs do have immunity to confuse-spells on uth, thats working as intended.
But 2 things related to it are working a little different on live.

On uthgard if you try to confuse a named or epicquest mob (in my case mystical steed in CF ) you will have high chances to get a "x resists your effect!" before seeing a "X can't be confused!"

On live however it will never come to a "X resists the effect!" as "X can't be confused!" kicks in before a resist-check.
So there is no way on live to pull a questmobs like mystical steed by a resisted confuse-spell.

Also on live mobs that are set to "no confuse" will never get hit by confused normal mobs around them.
On uth you are able to confuse mobs around a named/questmob and they will attack everything. exploitable!

Reproduction Steps

1. Log a class able to confuse mobs
2. Go to a spot with highlvl named/epicquestmobs etc.
3. Try to confuse them, do they resist the spell and aggro on you?
4. Try to confuse mobs around the named and let them attack the named mob.
5. Compare with live. See differences?

Intended Behavior

Adjust the mechanics around "X can't be confused!" to work livelike and nonexploitable.

Evidence

This is on live:
https://www.youtube.com/watch?v=d6_prYHy9sM

See how it only shows "X can't be confused!" when i try to confuse it. Yesterday i pulled that same mob to a guardtower near parthanan farm and on the whole trip i kited it i wasn´t able to land 1 single DD! Just when the 3 guard-NPC started to hit i was able to land some dd.

Also see how the only mob next of the steed is confused but still not going to attack the steed, since its also unattackble for confused mobs.

I also tested another spot with no-confusable mobs vs normal mobs to be sure as these far darochas mightbe set as part of the epicquest.
But i got the same result. (Will record and add to comments in a bit.)

Status

issue is new, and needs confirmation
requires 1 more confirmations
votes (priority): 3
2 players say this report is valid, 0 disagree

Comments

Note: You need to be logged in to post comments.
Loading Comments...