I think the issue with arcane is the way it switches between burn and conserve it very often goes into conserve when you least want it I've seen it go into conserve at -1% like wtf.
My pet hate for arcane atm is that if you have cooldowns turned off it will spend charges as soon as 4 stacks is reached we need some way to control that shit.
I quiet often do dry burn phase which basically means I will camp four stacks with out blowing cooldowns I use it more and more in mythic and to a lesser degree in heroic. It's handy having a option to dry burn then evocation then conserve untill you want to pop your cooldown it can be a huge overall damage increase.
Also the way the routine deals with pause on any none movement keys it causes a huge loss in dps if you use custom keys and if you disable it you spend your time pausing the routine which causes even more issues I have seen logs on here with 1500ms thats insane basically the routine is taking a 1.5 second break every time a button is pressed, it's madness but I understand because if you can barely get it to blink with it on and it's impossible with out, but 750ms seems to be the lowest I can go even that involves mashing the button.
In mop the routine was harder for humans but easy for bots because you looked for conditions and acted on them in WoD the return of burn and conservre has made it harder for the bot to act how a human would WW Monks suffer for the same type of issue.
As for fire it suffers the same issues with the pause issues, but it also plain just messes up for example if you have only combust on +3 selected then remove it with out restarting honorbuddy it will be hit and miss if it will even work.
Ignite also seems to have issues sometimes i've seen ignite at 14k with my setting saying 8k for trash and by the time the routine gets to cast it's a 6k or it misses it all together waiting for a new ignite I get around it by always unglyphing combustion hoping a few of the many will be decent and they all mostly tend to be decent the routine handles unglyphed combustion better.
I would hazard that's to do with other spells already being in a queue, but it should be dumping the queue and cancelling the current cast and getting the bloody cumbustion full stop. why is fire pve rotation an extra tick it's adding more overhead to the routine it should be standard. It's obvious thats there is a overhead issue sometimes.
All in all the routine suffers form lack of human type intelligence making it less effective imo.
I'm still catching up on reading the backlog of posts, but figured I'd reply to some stuff instead of waiting until I've read everything. Quoting dilbog's post above as it contains most items I'm wanting to address.
Fire is so RNG it's unreal. You can stand at a target dummy and run the rotation 10 times in a row and have completely different results every time. Some people have better success with the 'normal' rotation, others are happier with the 'advanced pve rotation' - so you need to test both really and see how you get on.
I've got a new update with a few changes in, but I need to test the changes thoroughly as soon as I get a spare moment!
Arcane -> The burn/conserve phase is dynamically calculated when to perform this. I've added some debugging into the logs to see why it's not triggering early enough to enter burn phase before a boss approaches death. Simcraft's calculation to work this out has changed since I implemented mine, however their calculation is ridiculous. I'll see what the new debug logging highlights first before taking this further.
Fire -> I've got a few changes for this to better handle inferno blast and meteor usage. Combustion won't be waiting as long to be cast either - it's better using it on a high combust instantly than risking the ignite power dropping off. It'll now consume any pyroblast procs (including tier bonus) before using combustion, but that's it.
Manual cast pause -> I'm changing this to a new, more reliable method. Upon the first key press, the routine will pause for the specified time. Pressing the key twice within that paused window won't make the routine re-trigger/stack/cancel the pause. It should just *feel* better.
Anyway, sorry for the slow updates. It's hard enough to keep up day to day nevermind trying to go back over 3 weeks worth of backlog ! I'll have to stop taking vacations
Note to self: #4533
