Not working on both...xcelsius is doin all the stuff on its own, we do share sometimes some code snippets to each other, but only some small parts,no full rotations So...yes sushi is different from yrb2
Today or tomorrow...I've changed a some stuff for subtlety and have to test assassination / combat before I can push the update
I'm really curious.. i raid high end tier constantly on my rogue, been in several top 40 guilds. And i no longer find joy in raiding w/o combat routines.. smashing a million buttons is not me anymore. Theres plenty of choice when it comes to rogue combat routines, but not sure what outperforms the other.. Can you elaborate on this? Will this routine outperform lets say YBR, Tuanha etc. ?
new version is up and waiting for approval fixed Vanish / Preparation in Combat and Assassination fixed Cleave in Assassination fixed an issue with melee range Crimson Tempest in cleave fixed FoK / Ambush fixed in Vanish Fixed AOE detection (Multidotting not affected from fix) fixed a bug with shadowmeld fixed a bug with pooling + cp fixed Preparation fixed for all Speccs a bug in Assassination should be fixed where Routine decided to stack 5 CP while vanishing a bug in Assassination should be fixed where Routine decided to pool energy fixed a bug in logging where CurrentTarget informations were written to the log instead of Target informations changed priority in builder task for Assassination changed a condition for Rupture in Subtletly which should fix the dropping of Rupture from Maintarget fixed a bug in poison spreading where rupture was used on off-target
i have tested subtlety whih tuanha,yrb2,soapbox and sushi on a single raider dummy Every cc I passed a lot of testing, responsible can be said that in this block, the subtlety of sushi single target is the best, I haven't tested aoe,so not clear how effective so,subtlety single DPS sushi>yrb2>soapbox>tuanha BTW:Combat rouge because I haven't tested, so I can't comment
If the newly released version is 1.0.1.39 the issues I reported lately still exists for combat. Does not refresh SnD and RS on time, pools energy to max and so on. Even though it's performing a little bit better now it looks to me it is scripted to pool energy to 120 in some situations which does put energy to max and it also misses out on eviscerates at red insight and 5CP due to this. This is with no CD's at all. During AR and BL I suppose this would be a great loss? View attachment 10472 2015-01-31 12.01.txt
tbh ... there wasn't ever changed anything in combat specc, i'll look at it, have to respecc my rogue first
class:subtlety human lv100 rouge target: raider dummy bot:enyo（enable force combat） two problem 1.when i target the dummy (have enabled auto stealth in cc),Suddenly sushi used vaish directly with opener,Don't know why to do so, it looks like a mess 2.as you see,never use Preparation in the log 3.when enable auto stealth and when i target a dummy,it will auto stealt or vanish（stealth cd) first,then it will use premeditation.yes it is right ,But in the later ，sometimes it will use Slice and Dice and sometime it dont
Well IDK what's been changed or not, just pointing out what I am experiencing. Maybe I need to change some settings for enyo then? Try it out and see how it performs for you
alright could find the issue .... stupid .... i never let him go down to preparation, routine always left the rotation before it came down to prep ... this is fixed with next update (should be ready in the evening)
no what i wanna say is ... it never changed... so these issues were always in there. i'm going through the combat specc right now and expect a fix for your reports in the evening
Hi, i have some dudes about this CC version pay 1- Include all specs?? 2- I have 672 subs rogue, how is dps compare with YRB2? I raiding all SOO with YRB2 and have excellent results, but today i think that no its the best CC
1.) precombat does not kick in here (using stealth), because ur forcing the routine to use instantly the combat rotation, i could workaround it and add a combat check for this, but generally that's not the fault of the routine 2.) will be fixed with next update (works already on my local copy) 3.) will look at the SnD issue, currently we excluded SnD after prem if we are in combat for more than 1 second, because it should be refreshed by 5 CPs usage
