Maintenance for the week of November 18:
• PC/Mac: No maintenance – November 18
• ESO Store and Account System for maintenance – November 19, 9:00AM EST (14:00 UTC) - 6:00PM EST (23:00 UTC)
• PlayStation®: EU megaserver for maintenance – November 19, 23:00 UTC (6:00PM EST) - November 20, 17:00 UTC (12:00PM EST) https://forums.elderscrollsonline.com/en/discussion/668861
Also Dark Cloak if you pop it with more than one DoT on you, though if you pop it again you might remove the last DoT and be able to go into sneak. With Dark Cloak, if it fails, just pop it again and pray.
Damage breaks the cloaks as does a status effect....so if an area of effect is cast and you happen to be in it and use the nightblade stealth it will either fail to initiate and eat your mana....or it will start up but disappear fast.
So another nightblade power that makes paths can reveal other nightblades or prevent them from using their stealth abilities.
The aura that a mage can get also does the same thing.
In fact I don't think there is a lot that doesn't break the stealth or prevent it from working.
Its interesting that people are now noticing this...or maybe its just recently they are posting about it.
Its how in pvp I get kills....easiest targets are usually the nightblades
the developers made their powers not that good...and the stealth things are a joke.
<had to edit this in>
Another funny thing that breaks stealth is healing.....yep that's right...your friend who is trying to keep you alive....literally takes away your abilities.
I find this very Ironic....but go figure...they wouldn't fix it during closed beta either.
I have tested this skill extensively, and have the Dark Cloak version.
I've had it fail even when my opponent hasn't even had a chance to target me yet, or use any abilities (stunned from my sneak attack.). And no, it's not from magelight either.
It also happens to me against NPCs.
I still haven't figured out the cause, but if I were to guess, it's something I am doing, and not my opponent.
Whatever the case, at this point I classify it as a bug.