can u please tell us on which bosses u encountered the Freeze action from the pet? cause i looked at the code and there is a condition the Freeze is NOT used on bosses
I'm glad it's working well for you Is v2 an unreleased version you guys are working on? I wonder if I should just wait for it before taking a closer look at what I didn't finish tuning last time (like Evocation usage). Cheers!
Oh Ok, Thank you so much. I actually have it updated, but just thought that seal swapping was only used to switch from insight to righteous, and therefore I just figured that it would stay at insight. Awesome bro, very very grateful for your help. EDIT: After playing with this a bit. I notice that it if you switch it during combat you are gold, but when you go out of combat and enter again it will switch back to insight sometimes.
for rain of fire u need to stand near the boss so the middle of the cast is in range for the center of the boss i hope i wrote so u can understand it
Great to hear that you're working on it! Just tested the Demonology rotation from the /branch folder and think it's quite faster (maybe, because I don't have to press "Doom" manually anymore ), but when it changes to meta it still casts Doom frequently. So I tested a little bit and find out that the spell id of the Doom debuff is still 603, as before mop. And with this added in the fourth argument it works like a charm: Code: private static Composite HandleDoom() { return new PrioritySelector( Spell.CastHack("Metamorphosis: Doom", "Doom", on => Me.CurrentTarget, ret => Me.HasAura("Metamorphosis") && (DoomTimeLeft < 29 || (DoomTimeLeft < 40 && Me.CachedHasAura(113861)) || Me.CurrentTarget.HasAura("Doom", [B]603[/B])) // Lua.RunMacroText("/cast Doom", ret => Me.HasAura("Metamorphosis") && (DoomTimeLeft < 29 || (DoomTimeLeft < 40 && Me.CachedHasAura(113861, 0)) || !Me.CurrentTarget.HasAura("Doom", 0)) )); } Just wanted to tell you that, in case you don't have a foreign tester And thanks for such a great rotation!
i am getting this error .. PureRotation 1.2.3]: Woops, we could not set the rotation. [PureRotation 1.2.3]: Could not load file or assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. PureRotation Log: WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Could not load file or assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. PureRotation Log: WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Could not load file or assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. PureRotation Log: WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Could not load file or assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. PureRotation Log: WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Could not load file or assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. PureRotation Log: WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Could not load file or assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. PureRotation Log: WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Could not load file or assembly 'System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. PureRotation Log: WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. [PureRotation 1.2.3]: Unable to find Active Rotation: System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module) at System.Reflection.RuntimeModule.GetTypes() at System.Reflection.Assembly.GetTypes() at Styx.Common.TypeLoader`1.(Assembly ) at System.Linq.Enumerable.<SelectManyIterator>d__14`2.MoveNext() at Styx.Common.TypeLoader`1.(Assembly[] ) at Styx.Common.TypeLoader`1.Reload() at Styx.Common.TypeLoader`1..ctor(Assembly asm) at PureRotation.PureRotationRoutine.GetRotations() in d:\my friend\my friend\Routines\PR\PureRotation.Behaviours.cs:line 105 Bot Stopped! Reason: None Given Initialization complete.
Great job with updating WW Monk, uses Tiger's Eye brew now effectively, thanks! And the amount of work you put into Lock is really appreciated, especially after they felt dead for so long. Not sure if I've ever said it as well, but excellent job on DKs too, being top dps consistently is a nice feeling. However, Fury warr is still rage capping too often, and missing procs about 3/5 times. Also, the toggle for Hunter's Mark on a Hunter still doesn't seem to work. On some bosses it just spams it every few seconds when and if another hunter marks it
Hi guys! There's a really big problem with Restoration Shaman routine. HST and MTT overwrite the HTT when the latter is used just before the first two finish the cooldown. HTT is the most powerful healing cooldown of the shaman and this problem sometimes prevents the proper use (I wiped my 10 man during Jin'rok's Lightining Storm XD). Another little problem is the Earth Shield usage on Gara'jal: When the tank is phased in the spirit world, the routine stop all healing and try to spam Earth Shield on him.
sry for my last commit yesterday ... i think i was brain-afk, there where some changes that where done for V2 ... The Destruction-Warlocks will have Problems with ... Rain of Fire ... ----------------------------------------------------------- I'll revert them now, RoF should work again, sry for this with rev 1152 RoF should work again
Thanks for the report, although the code you've added will check that your target has less than 603 stacks of doom on it The core code has been drastically changed for major performance improvements, which is why the routine runs quicker with v2.0.0. I've changed the whole method to the new style of checking on branch.
rain of fire destro lock CR doesnt seem to be casting rain of fire at all during single target or aoe. I had everything set to true.
I'm still finding that DK Unholy does not cast very often and the DPS isn't great. It's letting sudden doom procs and dark transformation procs drop. Currently in 518 gear with LMG and it's pulling around 95k on raid dummy (with flask), whereas frost is around 125k.
The one i noticed it the most was Iron Qon, i was a bit high when doing it so it may have been trying to freeze the adds just before him which can't be frozen. I will try it again later.
