Ive looked through the coding and cannot find anywhere to disable battle shout. asl well as commanding shout... anyone got any ideas?
Same here...it´s weird, i try to look ar in all the .cs but nothing at all i need that fix it bc is a big fcking "hey look at me i´m a bot"
some weird glitching is happening when i have HB attached and hearth or go into certain BGS (isle of gilneas) I get wow not responding/crash for some reason.
I notice that my feral druid is pretty often at full energy even thought it could be spending that energy on abilities. Any idea whythis is? Also Im not a big fan on the autocast dash
Is there any way to make Killing Spree for rogues manual instead of automatic? It got me killed at several SoO bosses, which was... unfortunate. It's too random as is.
thats exactly the program i use...but the thing is i really don´t know exaclty where that string or variable is it...so i just look´d up on warriors.cs etc...if you can tell me where i need to go i can look at. Thanks
I managed to find it. At least for Fury. In the Fury.cs I just did a search for shout and deleted the first entry. Right above it is a "//Buff Up" Comment Now it doesn't spam battle shout anymore edit: I deleted the shout entries in Warrior.cs first but they did nothing. And if you delete any other entries in the .cs it crashed honorbuddy. But I'm now running just fine
It is possible that I may have linked the wrong post. However, bobby53 said that he will not be uploading any zip files of the updated Singular. They will be pushed out with the updated Honorbuddy when it's released from now on until further notice.
@zeldrak: Thanks, that is correct. A number of the issues being seen as problems with Singular are due to APIs and data that need to be corrected in HonorBuddy. There are a few fixes available in Singular now worth obtaining prior to an HonorBuddy update however, so am posting a release. At the point a new release of HonorBuddy is available containing that version of Singular, it will be removed. Thanks for your support, -Bobby53
*new* Singular v4.0.0.3756 available for download! Keeping it short, lot's to do.... - Download from Post #1 as usual - See the .ZIP file for Change History - Only Death Knights and Druids have been looked at in detail. - Buff spamming by Death Knights, Monks, and Warriors fixed. - Other buff spamming issues will be fixed by new version of HonorBuddy (such as Mage with Molten Armor) IF YOU POST, ATTACH A LOG - Otherwise the post will be ignored. A lot of change between versions of HonorBuddy, versions of Singular, and other things that words without a log are insufficient. Thanks for your help with detailed feedback and patience with the spell priority revision process, -Bobby53
Heya bobby, Cheers for the update. Reading through the change log looks like most of the issues I was seeing should now be cleaned up. There is just one other minor thing I would love to see added. Currently there is no UI setting to disable the vanish for dps boost for Rogues. While this isn't an issue when in groups, this does cause problems when soloing. I see in the logic for it, the Rogue must be behind the boss, have SnD up, and less than 2 combo points, and when you are soloing it is normally quite hard to hit those conditions, especially the behind the boss part. There are some bosses that walk away from you for a transition or ability, namely LK... I have been manually editing out the Sequence to manually control Vanish, but would love a UI toggle for it in between all the other work you are doing.
Hello, First and foremost, thank you for the combat routines. Really appreciate your work. Onto the task at hand. Arms and fury warrior rotations are not working correctly. Especially in arms spec, "Rend" is the most vital part of gameplay. Arms -> "Must" use rend and refresh it 5 seconds before it expires. Arms -> Must use whirlwind above 40 rage. Arms -> Must use execute upon activation. Arms -> Dragon Roar must be used "outside" the Colossus smash debuff window. Fury -> Must use raging blow upon reaching 2 stacks. Fury -> Must use wild strike above 90 rage and upon activation. As a final note, both specs auto-cancel bladestorm almost immediately upon activation. I hope this little bit of feedback helps. Thank you very much in advance.
You'll need to post a log or your post may get archived without consideration. Just be sure that when you post something to bobby's thread, you always, Always, ALWAYS attach a log file. Just letting you know, just in case your post goes unanswered.
up the fix plz for others to use will give credit or rep if u do P EDIT: didnt see the fix on the front page
I recommend for the warrior rotation, arms, to use whirlwind to prevent rage capping and when there is more than two targets
