it’s been going on for over a decade, Blizzard has known about it for a LONG time and simply doesn’t care or doesn’t have a developer competent enough to fix it.
So basically it comes down to they are lazy or stupid.
Sorry if that seems overly harsh but it’s been atleast 10 years of this, it simply can’t be anything else at this point.
Sadly, It likely boils down to “It’s not costing us any money, why waste money fixing it?”
Had this issue yesterday in Breckenridge Hollow. No dots on me, but I wouldn’t go invis on stealth activation
There’s definitely an issue somewhere. I was just Spark farming on my rogue and I was constantly in and out of stealth. I couldn’t pinpoint if it was when I would cross into the pvp zone or what. It seemed to trigger randomly. No AoE. Just pulled out of stealth
Nope I’ve experienced this several times and there’s nothing in the combat log at all. I started monitoring this because I was wondering why I could be AFK in the middle of a field only to come back to a non-DK attacking me.
Successful Vanishes are easy unless there’s a bleed. Just macro cloak to vanish. Never fails.
Walking within range of an incense (Eg, Sagacious Incense) will also cause stealth to break.
You can leave range and hit stealth, then walk back into range to receive the buff and it will break stealth. 100%. Every time.
I even made a video of it… (In the hope that generating enough negative attention may help prompt blizzard into finally fixing it…)
Upvote this.
Recently leveled up my Outlaw Rogue and have been experiencing this, too. Especially terrible in Mythic +'s and Battlegrounds. Don’t even get me started on the annoyance it causes in PVP World Areas.
Ok. So a little update for anybody interested.
After speaking to a GM and being informed it is not their area (This is true, the are not techs, they are customer service representatives) I was put in touch with a “Tech Specialist” who informed me, and I quote “Now, we have already linked your report to a case that we use to help them make those priorities”
He then suggested that I report this via the bug reporting system to further the case, and put a link to the video in the report.
I have done this, and ask that anybody who is following this thread and wants to push this with me so we can hopefully get it fixed to please do the same.
(anybody with the capabilities who can also manage to record and submit video evidence of stealth dropping for no reason would be VERY much appreciated)
Thank-you all in advance, let’s get this fixed! <3
(A link to the bug report can be found here → Rogue stealth-break issues worse than ever in Dragonflight ← )
Feel free to head on over and upvote it.
I appreciate your effort but at this point that’s blizzard’s job.
Collating detailed information about bugs along with demonstration video clips and relevant context is QA’s job. Not the players. It should work like this: “hey lots of players are complaining about stealth breaking, get QA to test a bunch of scenarios regarding this”, and then they create jiras (or whatever bugtracker they use) explaining each situation they encountered in detail. I already have a job, I am not interested in being a volunteer game tester for a multi billion dollar game company.
The devs, specifically coders, could add logging server side whenever stealth breaks on a player, along with context (location? spells, scripts, etc running on the player? etc.) and then mine those logs for anomalies.
It seems that things tend to break stealth by default unless defined/scripted/configured/etc otherwise. For example: the blackjack talent during the beta broke your stealth when sap ended on your target, which seems to indicate that adding a debuff to your target breaks stealth by default and they probably had to specifically configure it to not break stealth.
If this does indeed works this way then this is untenable in the face of the many one shot spells and hidden buffs used to run various items, toys and environment effects throughout the game, because the people developing all these things evidently can’t remember every time to flag things as “should not break stealth”. Heck perhaps they don’t even know those things can possibly break stealth.
So if that is the case gameplay programmers could (should!) refactor the code that manages stealth so that stealth doesn’t break by default and that breaking stealth have to be setup explicitly for all the spell/effects/debuffs/scripts/etc that have a legitimate gameplay reason to break stealth (and there should be comparatively few of them!).
They could even architecture it so that only something that gets added to the combat log is allowed to break stealth, so that when stealth breaks we can look at the log and understand what we did wrong (like “you were unstealthed by a flare.” or “you were unstealthed because of so and so’s AoE spell”).
Great reply, and I agree wholeheartedly with what you said.
And I especially agree with this (And I quote) “Collating detailed information about bugs along with demonstration video clips and relevant context is QA’s job. Not the players.”
But see the problem is. The players have been complaining about these issues for 10+ years now, and nothing has been done.
There have been thousands of bug reports, forum posts etc etc during this time. Yet nothing gets done.
What I am aiming for is to cause enough of a stink, to have people going around abusing these exploits until it gets to a point where blizzard can no longer deny there is an issue. THAT is how these things get fixed. When it shows potential to cause loss of income due to an undesirable product. THEN it will get fixed.
I come from another game called Eve online. CCP (the company that owns it) refused to fix issues that players had complained about for years. WE responded. WE let it be known that we wont stand for it, and WE got it fixed. After years of denial. (It was called “The summer of rage” google it if you are interested)
Long story short, This will only get addressed if we MAKE them address it.
Running through AV bg just now and was constantly unstealthing. I turned on all the spell messages of what happened to me in the combat log, and it seemed that improved garrote was showing up multiple times and then I would get the message that stealth had faded. Not sure why or if it is the reason but it seemed odd that it would show up so many times in a row. The longest run was 24 times in a row then stealth faded.
It seems like it will run twice per second then wait 5 seconds and repeat.
01:35:15> your Improved Garrote refreshed you
01:35:15> your Improved Garrote refreshed you
01:35:20> your Improved Garrote refreshed you
01:35:20> your Improved Garrote refreshed you
01:35:25> your Improved Garrote refreshed you
01:35:25> your Improved Garrote refreshed you
on and on. But again, not sure if this is anything or working as intended.
Would like to add Thank you for your effort to get this taken care of Flearidden. I’ve never heard of anyone getting to the tech specialist stage lol. I’ve never had any response from my complaints over the years.
Try it on a target dummy, and if you have a specific scenario to reproduce it i suggest going onto the PTR and use the bug reporter tool on that specific talent (there is a hotkey that you can use to open it as indicated in the talent tooltip) and giving a succinct explanation on how to reproduce the bug.
I have a feeling that reports going through beta/PTR in game bug report tool are directly triaged by blizzard’s QA and have a better chance to get acted upon. During beta they even explicitly said that it was the only way to report bugs, forums bug reports would be ignored.
Forum bug reports probably have to go through community managers or customer support before they have a chance to reach QA, which would mean the ball is more likely to be dropped.
Customer support in particular are probably the wrong interlocutors for this as their job is to help you troubleshoot problems on your end, so it typically take some effort to make them see that the problem is a game bug and should be escalated to some other people.
As an example when I reported that blackjack unstealthing bug with the beta bug report ingame tool it was fixed in the next beta build.
Another example is another long lived bug where quickly mouse turning as you landed after using a glider in BGs would immediately disconnect you (which smelled a lot like some movement cheat detection false positive). It was bugged for probably as long as the glider existed, so ten years.
I reported it during beta through the ingame bug report tool and this bug has been finally fixed in DF, which doesn’t seem like a coincidence.
I haven’t noticed to be an issue so far in DF, well at least not like past expansions where seemingly every few minutes stealth would fail.
I’ve noticed that when my undead racial, Touch of the Grave, procs on something (from dots still rolling after i restealth, for example) it will knock me out of stealth. Is this intended? I don’t remember this happening before.
Also sometimes I just randomly pop out of stealth for no reason when I’m not attacking anyone. This is new as of Dragonflight.
Yeah, happened to me too while in AV, and trying to ninja a flag. I couldn’t even enter the bunker without getting popped out of stealth repeatedly.
This has been an issue since Classic.
I honestly feel as though Blizzard just gave up on it.
Nature’s vigil from druids seems to find us even around 30 yards away and break us out of stealth too.
Something on paladins does too but no judgement debuffs but you randomly get pulled out.
Warlock malific rapture def does and sometimes demonlogy goons follow you indefinitely through vanish until called off.