Before You Begin

• I confirm I am using the latest version of the addon (outdated versions may have problems that were fixed on the newest release).
• I confirm I am playing on official Blizzard servers (not private servers).
• I checked for an existing, open ticket for this issue and was not able to find one.
• I have updated the issue title to clearly describe the problem.
• I am reporting an issue with the default specialization priority (not a custom or imported priority).

Specialization

DH - Havoc

Describe the Issue

Hello! The rotation stops after the second Eye Beam out of meta; from what I understand, it holds off on felblade (to proc inertia) for Eyebeam, but in the end, it just spams Chaos Strike nonstop.

How to Reproduce

1. Enter game as DH Havoc
2. Go on target dummy
3. fight him for like 1 min with aldrachi reaver inertia raidbuild.

What is your information source?

APL Conditions - I found a possible typo or mistake

Snapshot (Link)

https://pastebin.com/F5D3Jkt0

Raidbots Sim Report (Link)

https://www.raidbots.com/simbot/report/8CxpikxHMej5Tw2Vb6NgrK

Additional Information

No response

Contact Information

Discord : wolfiegoldie

I am still having this issue as of most recent build

Define "most recent build" with a version number

v11.2.0-1.0.0k

Are the suggestions acting wonky due to not having tier yet?

There are lots of APL tuneups coming to DH in the next version, this ticket is resolved. If you still have issues after the next release, open a new ticket.

Also having this

Your sim also does this. Does it eventually eye beam?

chaos_strike(0.08), chaos_strike(1.08), chaos_strike(2.65), chaos_strike(3.65), chaos_strike(5.56)

Your sim Sim

No it does chaos strike in a loop, only building fury with VR and felblade if needed to cast more chaos strike

Also having this. Imported the previous update's SIMC APL and works just fine now.

What is your information source?

APL Conditions - I found a possible typo or mistake

What's the typo in the APL?

Maybe I chose the wrong issue category but the issue still stands and it wasn't a problem in previous version

can confirm this is also happening to me.

Just adding myself to this. I reverted back to H and turned off auto update and it's fine again. Thanks!

(we don't need more confirmations, we are working on it)