[14/Dec/2013 - Update #2] - Fixed a bug in aura caching system, which would return the incorrect values on some checks.
just off topic abit: i am doing well as frost mage (at 567 ilevel). I am hearing everyone is talking about arcane or fire is better for heroic progression. WHat would you recommend for which spec Millz? i wonder which is a better spec for me atm. Thanks you for great cc and for any help
Hey - Arcane and Frost are pretty close; Simulationcraft Results Frost has a bit more mobility than what Arcane does in my opinion though.
Your ilvl doesn't really tel us a lot so I can only give your a rough idea. Fire for heroic is a NO because u cannot always get the dps when it needed, you see it climbing up the ranking ladder because a lot of guilds have SoO on farm and this is there fun spec. Frost is very nice for cleave fights and has 2 builds you can use, there is haste and mastery build. For either build you will want crit I always aim for 28% crit max But Dont be concerned if you cant get 28% crit then make your choices from there either go to 38%-40% haste them put everything into mastery for icicle damage or if you have enough haste go for your break points ie living bomb +2=37.52%, +3=62.47%, +4=87.44% haste for the added ticks. My choice for SoO has been living living bomb for almost all fights because of my role/guild tactics. For arcane some like 40% haste with 85% plus in mastery is the way to go. but u can raid with less haste. All in all it depends not so much what ilvl you have but more the stats on the gear you have got that will let you know what you can do. Frost is my go to spec for heroic but arcane if you got the right gear is just as good But there is not the instant damage there so for siegecrafter ect if your on the belt frost is better unless you are hording all your cool downs for it.
I have experienced this issue with all releases i have tried prior to .708 as well as the current .711. I have never had this routine work without a small delay between casts unless both anti-lag settings are off.
Have you got a log file? It's using the item by the ID, so language doesn't matter. Just pushed an update. Have a go and see if it's running any quicker now.
It is still casting evocation twice. I have tried with minify disabled, with anti lag 1+2, just 2 enabled and all 3 enable with same result it will cast evocation twice, but there is a issue when in combat it will cast evocation clip it cast something else then try again to cast evocation, watched it for a entire fight trying to do this just to see if it would sort it's self out. It has only did this from your latest update.
I have the same problem, tried the same combinations of antilag and not running minify. Have quite low latency 20ms.
Hi planning on buying this soon, testing the free version while levelign but got a question, is there any way to force the profile to initiate combat etc? i notice in the low lvl dungeons takes forever to enter combat and while leveling while i don't want to use quest bot i would like to just pick targets and have the profile attack them for me. Tried lazyraider without leader and no luck tyrael no luck, would appreciate if someone could tell me if it's possible and how to do it, thanks . Fixed, edited tyrael and managed to get it to always be in combat.
Hello! i tried your free version and its great! so i decided to buy your premum routine! So now im just waiting for an email with the full detalis of the SVN. i hope you can read this and and send me the email! cant wait to test the full version
Done Hmm must be because of the new latency clipping. So to explain what I changed with anti-lag #2; Before: - Pause the routine until we're not casting/channeling Now: - Pause the routine until we've got less than our ((latency *1.1)+50) ms remaining on the cast. 100ms latency would mean start trying to cast the next spell.. queuing.. at 160ms remaining on the current cast. The routine will be starting to cast a new Evocation, thinking that it's still required, before the current one fully ends (and we gain the buff). I'll add some code in to fix this today. Minor bug is worth it for the potential DPS increase once it's ironed out The normal method it just to cast the first spell to initiate combat - that prevents us accidentally pulling bosses/mobs upon selecting a target. Enabling healing mode in Tyrael is a fix/workaround to this, but it's not recommended.