Maintenance for the week of September 8:
• [IN PROGRESS] PC/Mac: EU megaserver for maintenance – September 9, 22:00 UTC (6:00PM EDT) - September 10, 16:00 UTC (12:00PM EDT)
• [IN PROGRESS] PC/Mac: EU megaserver for maintenance – September 9, 22:00 UTC (6:00PM EDT) - September 10, 16:00 UTC (12:00PM EDT)
Pierce Armor - Failure to Fire
Gabriel_H
✭✭✭✭✭
This skill simply will not fire. It has now happened in multiple locations/dungeons/trials.
The issue is not distance or line of sight. The keypress even regsiters on the bar (with the icon showing the keypress animation) but the skill won't fire.
While switching to another taunt (which fires without issue - Leashing Throw, Inner Fire, Explosive Charge) does taunt the mob, it not only means a loss of nearly ~9,000 penetration, but also then having to compensate on the fly when a skill that should fire does not.
This is simply not playable in difficult content. It's causing group deaths, due to taunt loss, and a huge drop in DPS, due to the penetration loss. Players should select skills for fights based on the mechanics, not on whether a skill will actually fire.
"I can't taunt" - a phrase I have said way too many times lately. This is a core tanking skill, it NEEDS to work. This isn't like other reports of skills taking 2, 3, or 4 key presses but the skill itself just simply stops working on some mobs and bosses no matter how many times the key is pressed.
While this is obsviously a bug, a serious one at that, I'm posting this in General as a way to highlight the problem and to let others know - Do NOT trust this skill to work. I have seen multiple reports from players about skills not working, I am yet to see anything from ZOS. Whatever changes you've made recently have broken a core mechanic - you need to show some respect to your players and comment on it.
The issue is not distance or line of sight. The keypress even regsiters on the bar (with the icon showing the keypress animation) but the skill won't fire.
While switching to another taunt (which fires without issue - Leashing Throw, Inner Fire, Explosive Charge) does taunt the mob, it not only means a loss of nearly ~9,000 penetration, but also then having to compensate on the fly when a skill that should fire does not.
This is simply not playable in difficult content. It's causing group deaths, due to taunt loss, and a huge drop in DPS, due to the penetration loss. Players should select skills for fights based on the mechanics, not on whether a skill will actually fire.
"I can't taunt" - a phrase I have said way too many times lately. This is a core tanking skill, it NEEDS to work. This isn't like other reports of skills taking 2, 3, or 4 key presses but the skill itself just simply stops working on some mobs and bosses no matter how many times the key is pressed.
While this is obsviously a bug, a serious one at that, I'm posting this in General as a way to highlight the problem and to let others know - Do NOT trust this skill to work. I have seen multiple reports from players about skills not working, I am yet to see anything from ZOS. Whatever changes you've made recently have broken a core mechanic - you need to show some respect to your players and comment on it.
2
-
valenwood_vegan✭✭✭✭✭
✭✭✭Yeah this has been happening to me with numerous skills - across multiple dungeons, and seems to relate to specific enemies.
To boil it down to one specific example - the final boss in Volenfell, with the 3 centurions...
If I target the guardian's strength or the guardian's soul, everything works normally. As soon as I attempt to target the guardian's spark, most of my skills simply WILL NOT work - nothing happens at all. This includes skills like arcanist flail, or templar sweep that don't even require a target. As soon as I stop targeting the guardian's spark, these skills work normally again. It's also not some kind of LoS issue because light and heavy attacks still work.
But that's just an example. There's a random storm atronach in tempest island with the same issue. And I've had it happen in other dungeons as well - just a moment ago in spindle II (though I couldn't tell which specific enemy was the issue there, too much happening). As far as I can tell, it always relates to targeting the same specific enemies, but there may be other ways that the problem gets triggered. I honestly don't play enough or care enough currently to spend any of my time trying to test further.
I don't know what zos did, but something is severely broken yeah.Edited by valenwood_vegan on September 6, 2025 8:47PM1
