Night Market: My skills constantly bug out?

Nemesis7884 · April 30

Meaning not working, not firing, issues with targeting mobs - especially everything beam type related... is that only me? Only happens in the night market :-/

OccultNerd · April 30

Also had the same issues on my Necro DPS and Warden Healer, couldn't use some skills and couldn't heavy attack unless I swapped bars which is fine on my Healer but the DPS is a 1 bar build 🤦🤣

Mashille · April 30

I've had a similar issue. It seems to happen on random enemy NPCs, where my abilities just will not target them, but for a different NPC right next to them it'll work fine. It's strange

langewapper · April 30

had the same with my subclass templar no more beams no more health nothing working for seconds
and zos change the name to night market trial

Malprave · April 30

Happened after playing NM for hours. Used to happen to me pretty consistently on one of the bosses in March of Sacrifices

HunterTheCapricorn · April 30

Had the same. Also animations bugging out when you cancel skill animations by bar swapping (which is mandatory to play) and then having stuck skills. Also the ping is extremely high (constant 999+) only in Night Market for some reason on top of that only 50fps in big groups on a 5090.

BardokRedSnow · April 30

Same, my engulfing dragonfire bugs out after 2 seconds when there's around 8 or more players with me in a fight, was annoying.

Aydh · April 30

Had same issue last night. Single target direct damage stuff wouldn't fire on some mobs. happened a handful of times yesterday and to everyone in our group on the same mobs. Different mobs, different zones. Couldn't pinpoint a root cause. Possibly was due to mob clipping into terrain, we were not sure.

whitecrow · April 30

Yes, my first and second skills would not fire. Nightblade DPS.

E_Lucan · April 30

Nemesis7884 wrote: »

Meaning not working, not firing, issues with targeting mobs - especially everything beam type related... is that only me? Only happens in the night market :-/

Yes! I played on my DK today and about half of the time my fire breath just didn't happen, my character did the animation for it but no fire came out and the enemies took no damage. Same happened with my ultimate (DK banner). I also cannot seem to target some enemies with heavy attacks or direct damage in general, such as the animated armour knights in The Parch. I can't play my heavy attack build in the event for this reason as many of the mobs seemingly cannot be targeted.

ectoplasmicninja · April 30

Same problem on my arcanist last night, along with 999+ ping maybe 30% of the time. Things would go from vet trial insanity to a slideshow in an instant, with people teleporting all over and my inputs delayed by upwards of ten seconds at times. Really difficult to contribute properly especially with the already chaotic "group" setup.

sshogrin · April 30

Posts about bugs like this should be in the "Bug Reports" section of the forums.
ZOS will find them easier to fix.

Sythen88411 · April 30

Skills where not rendering but working when taunting.

AcadianPaladin · April 30

First big fight, my heavy one bar build could not heavy attack. Normal (cast) skills only. When I hit HA, only a LA appear to go out but it registered no damage at all.

SeveN085 · April 30

Think it has to do with aggro distance. It's the same animation stutter when you're trying to use skills on those mobs. Just like in normal zones when you run too far away you can only target mobs once and it will cause them to disengage and run back to their spots while being untargetable. There's some kind of check(individual) when you can't target mobs that are too far from their original spots, but since aggro distance is really short in Night Market it can get really janky. It looks like some mobs will get out of range for you, but not for the others that pulled them and it's only those that aggro'ed them will be able to target them.

ZOS_Hadeostry · April 30

Greetings,

After further review we have decided to move this thread to a category we think is more appropriate for this topic, as it's reporting a potential bug