Maintenance for the week of April 6:
• PC/Mac: No maintenance – April 6

Target is too powerful for this effect

Sethyss
Sethyss
✭✭✭
Anyone else getting this message with certain trash mobs when trying to use knockbacks or other CC abilities more than once?

I play with a bow, and use Magnum Shot to knockback/stun when trying to manage fights with packs of 2 or 3 trash mobs.

I am currently in the vr9 Malabal Tor area and a lot of the Drublog orcs there have become immune to Magnum Shot after the first use. These aren't bosses, just normal mobs patrolling around the open world area.

Is this working as intended?
  • Neferath
    Neferath
    ✭✭✭
    Well with patch 1.2.3 introduced, players who break a cc get immunity to similiar effects for 1-2 sec. Maybe this applies to npc mobs too now?
  • fyendiarb16_ESO
    fyendiarb16_ESO
    ✭✭✭
    Neferath wrote: »
    Well with patch 1.2.3 introduced, players who break a cc get immunity to similiar effects for 1-2 sec. Maybe this applies to npc mobs too now?

    I am really hoping this is a bug and it is only intended to work this way against players.
  • Sethyss
    Sethyss
    ✭✭✭
    Neferath wrote: »
    Well with patch 1.2.3 introduced, players who break a cc get immunity to similiar effects for 1-2 sec. Maybe this applies to npc mobs too now?

    Possibly, couldn't find anything in the patch notes though. There was a bit about some dungeon bosses receiving the correct immunities now, but that is all I can find.

    It is not all trash mobs though, only certain kinds, which makes me think it is a glitch that has sneaked in with the update.

    Maybe with the player immunity in PVP, any NPCs that are a playable race like the Drublog orcs also got the immunity. If that is the case then the issue deserves a massive /facepalm.
  • Hilgara
    Hilgara
    ✭✭✭✭✭
    Its here
    •Automatic crowd-control immunity and crowd-control break immunity will now protect you from the same types of crowd-control.

    basically if you (or apparently any NPC) breaks out of CC you cannot reaply the same CC for a period of time.
    Edited by Hilgara on June 25, 2014 12:26PM
  • Sethyss
    Sethyss
    ✭✭✭
    Hilgara wrote: »
    Its here
    •Automatic crowd-control immunity and crowd-control break immunity will now protect you from the same types of crowd-control.

    basically if you (or apparently any NPC) breaks out of CC you cannot reaply the same CC for a period of time.

    If it was applying to all npcs then I would accept that, but right now it is only certain types that seem to get this immunity, which makes me think its not intended.

    Seems a stretch to say that the part of the patchnotes quoted is the explanation for this issue, unless the "you" is also for the benefit of any NPCs reading the patchnotes.
    Edited by Sethyss on June 25, 2014 12:54PM
  • Hilgara
    Hilgara
    ✭✭✭✭✭
    Sethyss wrote: »
    Hilgara wrote: »
    Its here
    •Automatic crowd-control immunity and crowd-control break immunity will now protect you from the same types of crowd-control.

    basically if you (or apparently any NPC) breaks out of CC you cannot reaply the same CC for a period of time.

    If it was applying to all npcs then I would accept that, but right now it is only certain types that seem to get this immunity, which makes me think its not intended.

    Seems a stretch to say that the part of the patchnotes quoted is the explanation for this issue, unless the "you" is also for the benefit of any NPCs reading the patchnotes.

    Could only be those that are capable of breaking out of CC. Some mobs have a random chance to break CC too, although this is usually 1 pip bosses. 2 pip bosses always break CC

  • coryevans_3b14_ESO
    coryevans_3b14_ESO
    ✭✭✭✭✭
    It's applying to 0 pip npc mobs randomly. Drauger bane npcs are one of them. Definitely not that many of them. I have been running all over the place trying to reproduce the affect.
  • Hilgara
    Hilgara
    ✭✭✭✭✭
    I'm told this is only a 1 or 2 second cooldown so unless you are spamming the dame button again and again its shouldn't cause problems.
    Edited by Hilgara on June 25, 2014 1:41PM
  • cigarsmoker
    cigarsmoker
    ✭✭✭
    I've been getting this from day one. Actually before day one, I had early access. All the 'large' mobs like harvesters and such are too powerful for any CC, which really screws over nightblades who are all about the stun, off balance, etc.

    It's a bad world to be a nightblade in, and has been for a long while. :(
    "900 years of Time and Space and I've never met anyone who was unimportant" - The 9th incarnation of The Doctor
  • Mallow
    Mallow
    ✭✭✭
    I was about to make a thread about this. I got this on several regular mobs (Skeletal Ravagers, I think) in the Mal Sorra delve in Coldharbour. I was on my Templar and using the solar ability that has a snare (not in game at the moment and can't remember what it's called). Not ALL of the Skeletal Ravagers did this though, just some of them. *scratches head*
  • Sethyss
    Sethyss
    ✭✭✭
    Hilgara wrote: »
    I'm told this is only a 1 or 2 second cooldown so unless you are spamming the dame button again and again its shouldn't cause problems.

    I don't understand why you are continuing to try to excuse the issue when it is not something you have experienced for yourself.

    From first hand experience, the immunity definitely feels longer than 1 or 2 seconds, but I will admit that it may just feel longer in the heat of battle. But even if it is only 1 or 2 seconds, that's enough of a delay after a CC wears off to become a nuisance if you had previously been using a skill to lock one mob down in a pack of three. That isn't spamming, that is controlling the a fight.

    There is nothing currently in the patch notes to suggest that this change was intended, but if it is intended that is fine and I will either change my choice of weapon or carry on through the rest of the game playing pot luck on which trash mobs do/don't have this immunity. If they could confirm this one way or another, then great.

    However, if this change was not intended then I would prefer that they know about it now as there are undoubtedly going to be some fixes pushed out in the wake of patch 1.2.3.
Sign In or Register to comment.