Does it not support all tier 7 talents atm in Arms? Was about to test [Siegebreaker]. And it stop after a few casts in. View attachment 8440 2014-11-19 20.22.txt
Routine not working at all for me with updated HB I get this error message when I go into the profile and the profile shows no options, See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1. at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Char[] data, Int32 length, Int32 invCharPos) at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() at System.Xml.XmlTextReaderImpl.ParseDocumentContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlReader.MoveToContent() at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options) at System.Xml.Linq.XElement.Load(String uri, LoadOptions options) at System.Xml.Linq.XElement.Load(String uri) at Styx.Helpers.Settings.Load() at Styx.Helpers.Settings..ctor(String settingsPath, String oldSettingsPath) at FUPremium.Interfaces.Settings.InternalSettings.get_Arms() at FUPremium.Interfaces.GUI.UserInterface.Interface_Load(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- Honorbuddy Assembly Version: 2.5.12061.757 Win32 Version: 2.5.12061.757 CodeBase: file:///C:/Users/***/Documents/Honorbuddy/Honorbuddy.exe ---------------------------------------- ---------------------------------------- <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
can confirm this, happened to me today while doing heroics. Skyreach and the one with the "worm", where you're standing at a platform and the boss is attacking standing in the air/water
I think to fix the ravager placement issue with all those encounters you leave ravager out of the rotation and put it in a special "exceptions" category in the profile where when we hit a specific hot-key we've assigned to ravager on our spellbars it pauses rotation and allows us to place ravager where we mouse over and then the rotation notices ravager is on cool down and continues where it left off? This eliminates the need to completely remove ravager out of the rotation and forces us to use it off CD instead? I know it would mean more coding sorry haha As for the rotation completely stopping randomly in encounters trash/bosses and having to stop the bot and start it again I have no idea what's causing this but I assume its happening to everyone else too? It just seems to happen more often in AOE scenarios with at least 5+ mobs. Seems the aoe in all the rotations is either only coded to handle 3-4 mobs at a time and when it gets too hectic it doesn't know whether to use Thunderclap (alot of the profiles use it once or twice in entire fight) or Dragon roar/Shockwave don't get used off CD and stalls. I'd love to attach logs but id have about 50+ of them in the past week or so of testing. These are just the few things I've noticed that happened at these precise moments, I know you're still updating your Gladiator profile and in my opinion and everyone else's you should focus on the only 2 viable options for warriors at the moment which are glad dps and prot wars. Fix those 2 main specs first and then worry about the others for future content T17+ Since Glad is still simm'd as best DPS spec for us even after first tier of raids Lastly (I know this is a long post but I'm trying my best to accurately pin point bugs and try help you in whatever way i can) Whenever I hearthstone or Garrison hearthstone or Load into an instance (accept Dungeon que) or even leave instance wow crashes I've found this is fixed when i turn the profile off before leaving/taking hearthstones so a heads up to anyone else having this exact issue. I feel this is more so to do with HBs side of the client but then again it only happens with your profile active.
I've seen all your concerns and instead of replying to you all I'd sum it up: 1: Ravager has placement issues as it seems - This will be fixed in the upcoming version. I'll be checking if the unit is properly in Spell line of Sight and if it's not flying. 2: Rotation stopping - On this I think I've found the cause. One would be Ravager, and the second would be a mistake in range checks. These 2 should be fixed in the upcoming release. 3: Fury doing low DPS - The rotation didn't get edited in the transition from prepatch to WoD - Hence the low DPS is caused by WoD and not by the routine. Ofcourse I will closely monitor this and make adjustments where needed. 4: Gladiator's thunderclap behavior is being worked on. I'll make a logic which determines whether we need to use Thunderclap as optimal or Devastate. 5: Mounted combat - This is fixed in next push. I'm happy with all the reports and I will fix them as soon as possible ofcourse. You can expect a push with these fixes today. Changelog is: Version 0.0.0.8-B4 ==================================================== * Core: Changed default setting for Interrupt Method to Always. * Core: Added a more reliable method to get system's uptime. * Core: Added logger for Ingame FPS. * Core: Fixed mounted-combat - Should be able to fight now on the Horde and Alliance combat mounts. * Core: Solved an issue where combat would halt - even when we have a valid target selected. * Core: Added DiagnosticLogging for the Casting methods - Can see what spell is trying to be cast. * All Specs: Improved ravager's placement logic. * All Specs: Fixed a range issue with Heroic Throw. * Fury: Added ragedump execute to Fury. * Prot/Gladiator: Should not use the appropriate Shout when in Gladiator or Defensive stance. * Prot/Gladiator: Distinguished defensive and gladiator stance in the questing rotations.
It also seems that the routine stop if u switch a talent or two. U need to restart hb to get it to work again. Should have a log, but only got a long one. View attachment 15276 2014-11-20 11.08.txt
is it possible that in pvp battleground or arena the harmstring or slow debuff will be applied to my enemies or must i do it by myself?
Thanks for your hard work nom! We keep posting feedback not to be mean but to help you make the best warrior CC out there Looking forward to the changes cause my routine keeps stopping, my loading window keeps freezing (when I use Fury Unleashed) and Ravager not targetting well.
hey guys, ive noticed that the CC wont work in arenas, i know its not a pvp cc, but will this work in the highmaul gladiator sanctum arena thing ?
Confirmation here with the log, never do shockwave in defensive stance View attachment 5792 2014-11-20 10.04.txt
Arms feels really rough. Dosnt wait for CDs that are close and mortal strike before CS even if a couple secs off, causing lower numbers then my manual play. Dosnt always mutlidot with rend. Biggest issue atm feels like timing. Also it is not using bladestorm as much even tho its in mulit tar count. Not using Stormbolt in opener on boss with CS even tho set to boss only and dosnt line up SB with CS..
The randomly stopping issue seems to be happening to more routines - Could anyone experiencing this with FU2 confirm that it also happens when using a different routine? These rotational and lining up issues will get solved soon tm. You are absolutely right that it needs work . During MoP, Fury was the way to go and arms was a bit neglected. That will get solved! Is being worked on! Yes - Added to the todo list. I've not tested it with arena's. If it doesn't work, then sorry. Will eventually get fixed but very low prio. Can you get me a logfile - The code for shockwave looks alright. I need the full logfile please.
Will there be a pushout tonight or there was more fixes to take care of? Prot feels however decent the few dungeons I tried it out on.
