Subtlety Rogue Folio Bug

Hello, I’d like to report a serious issue related to the Rogue’s “Subtlety” specialization.

Here’s my raider io profile; I play this spec all the time and know what I’m talking about because I see this happen constantly.

https://raider.io/characters/eu/howling-fjord/%D0%A1%D0%B0%D0%BB%D0%B0%D1%82%D0%B8%D1%81%D0%BE%D1%81

This issue has already been discussed in two previous threads—here are the links—but the descriptions were only superficial.

https://us.forums.blizzard.com/en/wow/t/omnium-folio-is-pulling-random-mobs-in-m/2322809

https://us.forums.blizzard.com/en/wow/t/omnium-folio-ability-ninja-pulling/2322416

In short, the problem is that certain mechanics of the abilities—specifically the Apex talents—cause the Folio to attack enemies who are NOT currently in combat with you, even though that wasn’t the original intent.

However, the most important thing is that this issue doesn’t just trigger the rogue’s own Folio—it also allows the Folios of other players in your party to do the same.

Let me explain how this works with an example:

  1. A clone created by a secret technique or an Apex ability is a type of NPC that appears when the ability is used. It generates a sort of fake aggro around itself, even targeting those who aren’t actually in combat.

  2. Your folio—or your allies’ folios—takes this fake aggro as real, which means enemies around you who aren’t actually in combat can become potential targets for the folio (it triggers very often).

  3. And just like that—the folio is already flying toward a random pack somewhere out there, even though there clearly wasn’t any combat there.

For your interest, you can check out a short WoWlog report where four ninja pulls were completed in four minutes of Nexus (two in the second pull, one in the third, and the last one in the fourth).

https://ru.warcraftlogs.com/reports/xXN9DQKgkvy7pW2F

Also, here’s an example of how to trigger an enemy with a 100% chance outside of combat, which I recorded on video.

https://youtu.be/EmSl5gJBz04

In short: we pick up the dark orbs, wait for them to charge, apply a debuff to the main target, and then cast the orb—it will fly to another target because the third talent in the Folio tree causes our orbs to fly to targets that don’t yet have a debuff.

As the statistics show, this issue only occurs if there’s a Subtlety Rogue in the group—there are no problems with other specializations.

An additional problem is that a new Folio talent became available this week—because of it, Folio more often targets enemies that don’t have its secondary debuff. Consequently, this means it even more frequently targets enemies that no one has attacked, and which aren’t actually in combat.

So when playing in our own group, we ALL have to turn off Folio to avoid unnecessary problems. But as you can imagine, this isn’t quite right—after all, next week there will be a very powerful buff in the 4th row of Folio talents, and missing out on it because of this bug is simply wrong.

And when playing in LFG—it’s obviously impossible to get everyone to turn it off, which is why people will simply start avoiding games with rogues of this spec.

Therefore, I strongly request that this issue be fixed as soon as possible, since it significantly impacts the game, and most importantly, I really don’t want to ruin other players’ gaming experience because of this serious problem.

44 Likes

Bump. sub rogue clones are the best.

11 Likes

same issue, folio upgrades are unusable in mythics

12 Likes

As a sub player who has been having problems with the folio technology since day 1, i salute you for your hardwork bud. Id also like to add, because i think they might be related, a problem that ive been having with warlocks, demo or affli (never played with destro) since m+ day 1: sometimes locks pet go crazy and start pulling out of combat mobs, like the folio rn. But to solve this i just started playing without locks lol. I say this because i think that the logic of the bug might be similar (shadow clones interaction generating that fake aggro).

8 Likes

Caused me to bricked multiple 21s until I realized the folio was bugged on sub rogue… Was like how is everything getting butt pulled!?!

8 Likes

Thanks for posting. Guess I won’t be doing keys until this is fixed.

7 Likes

This problem is not exclusive to subtlety, it would be nice to see it fixed before next week.

Removing the Folio is currently only a minor damage loss, within 0.5-06% dps.
The next week’s unlock pushes it to a total of roughly 3%, which is more noticeable and makes it harder to convince your dungeon group to remove.

Quick actions would be appreciated given that the system is supposed to carry over into the next seasons of the expansion.

8 Likes

Been having this happen a great deal in keys, swift action would be greatly appreciated.

9 Likes

Had the same issues today, my group slammed our heads against a Maisara Cavern for quite a few attempts and couldn’t figure out where the random mobs kept getting pulled from until we saw this post. We all took points out of omni folio and the run went perfectly smooth after that.

8 Likes

A swift bugfix would be really appreciated. Not a single lifeform survived in my Seat key some minutes ago as the folio pulled every single mob that inhabits the dungeon.

8 Likes

Anyone heard anything yet on a fix yet?

7 Likes

Its insane that it has been bugged since launch, it got way worse this week, we have all this info and reports and blizzard cant even say that they are aware of the problem and working on it…. ngl makes me want to uninstall right away

7 Likes

It’s unplayable. Playing sub griefs keys. If this were happening to any other class they’d have fixed it by now.

10 Likes

Any chance of getting dev team (or bug team) acknowledgement? Kind of a rather large issue for us sub rogues, especially considering the power increase from omnium next reset…

8 Likes

Can we please get a bug fix asap? This bug has caused a huge number of key bricks for my group. We’ve resorted to having everyone in the group click off folio for now, but this will be a big nerf to us this upcoming reset with the secondary stat rune being available.

8 Likes

for the love of god please fix this. and the pet interactions.

9 Likes

I just tried doing a key as sub, my first in a while. This spec (with the folio) is unplayable in m+. Pulled every pack in Nexus Point without being in combat with it.

9 Likes

I bricked NPX a few days ago and had a very upset healer and tank due to this bug. Left side gets chained pulled until everyone is dead.

Group was baffled. I gently explained that I think my spec is bugged, apologized, and logged off.

I suspect that Blizzard doesn’t know how to fix this and I guess that means Sub is just dead now?

Feels bad man.

8 Likes

If they dont know how to fix it and its dead and gone, at the very least they should tell us, so if we wanna keep playing and trying m+ for title or mount or w/e we could focus on assa or outlaw.That is the very LEAST they could do. But imho what they really should do is:
a) disable all the folio system until they fix it - i know it sounds drastic but its for the best. its a system that will last a long time and atm its known to have issues not only with sub rogues (even though rn subs get most of the blame), but also with hunters, aug and locks - pet/clones classes.
b) change sub rogues to something like no clones, but bigger hits. less damage instances but we get the % of a single harder hit and keep it on a par with our current damage. This is also severe and sucks on class fantasy (and the clones do look cool), but that makes them keep the folio undercontrol (even with the other classes bugs, they are not as consistent) and give sub players the deserved shot at title/mount and the deserved fun time they paid for when subscribed.
I dont know, but thats what i can think right off the top of my head. Maybe there are better solutions out there, but truth is THEY SHOULD HAVE HAD IT FIXED BY NOW. Or at least told us.

8 Likes

At this point I’d say getting rid of clones is the move. Whatever the fix is, it needs to be asap. This is actually game breaking and clones have been causing other issues all expansion without a word from Blizzard.

8 Likes