hunter on GB 2 rarely fights, mostly pet beats the mobs, he is only casting missdirect on pet ... i press 1 button myself, starts to fight till goes out of combat and then again is not attacking. cannot post a log now, but ill post one when i get home
Bobby53's Standard Request for More Information [CLICK HERE] Most likely due to the same spell database issue in HonorBuddy that caused problems for Warlocks casting Corruption, but would need a complete debug log attached. Thanks for the post and good luck with your Shaman, -Bobby53
Bobby53's Standard Request for More Info [CLICK HERE] I can look at it when a log is available. Most likely this is due to Misdirect aura not being detected after cast due to the issue with HonorBuddy spell database, so would be fixed when a new version of HB is available. If you encounter again and can provide a debug log post again and I'll research this further for you, -Bobby53
Hello. I have the same problem as the warlock above me with my lock just spamming corruption on the target, but when i posted in support forums, Tony told me to post it in your thread. So i dont know if they know its a problem on HB's end not on the singulars, or why would i need to post the log here when u cant fix it? Either way, ill give u the log file.
Hello Bobby. Did you view yourself the singular since the new patch 5,4? (Hunter). It functions nothing at all more. The Hunter makes hardly still harms. Before the patch with 5.3 the Hunter ran in the arena very well. Exhibition you asks the problem on. And revise those singular for the Hunter, thank.
Thanks for the log file. That version of honorbuddy does not contain the updated spells database. Your only option would be to check the most recent beta release. Thanks for the log, Bobby53
It is an honorbuddy issue, similar to what warlocks experience. Your only option is to try the latest beta release since this is not a singular bug
Getting this Error with the new HB Version Compiler Error: f:\*\Routines\Singular\SingularRoutine.Context.cs(349,61) : error CS0234: Der Typ- oder Namespacename "Plugins" ist im Namespace "Styx.Common" nicht vorhanden. (Fehlt ein Assemblyverweis?) *edit* ok looks like the latest Singular is shipped with the new HB release. and working.
here you go Bob, and thx a lot is the biggest one that i have from yesterday , i hope you are right about MD aura, anyway, thanks edit: soz, file was too big
Corpse release after death is not working in 3058, I have reverted to 3022. EDIT: faulty code in 3058 (SingularRoutine.Behaviors.cs line 302) Code: new Action(r => { ResetCurrentTarget(); return RunStatus.Failure; }),
Problem is PQR being enabled while Singular was running. I usually do this as I have higher HPS this way and PQR may miss something that Singular will do. Issue hadn't occurred before 5.4 though, but would be nice to have an option to ENABLE/DISABLE Earth Stone on myself or.... as a Restoration Shaman make Water Shield the dominant spell buff over Earth Shield. Also, just noticed Singular attempting to Target/Attack opposing factions, doesn't clear target or target hostile NPC's. Log attached
Got a request for you bobby. This one is due to my own idiocy and trying to run instances and pvp at the same time with the same set of glyphs. Do you think you could add a check for hunters to disable the use of Explosive Trap in instances/raids if they have the Glyph of Explosive Trap? Knockbacks in instances are a big no-no.
HB Developers decided to remove a namespace that has existed for awhile but had become redundant without advance notice. There will be other components commonly used that will encounter this error as well until updated. A different namespace Styx.Plugins is the replacement. They fixed up the release of Singular present in HB, but the error will be encountered with the copies of SIngular downloaded from this thread when used with the latest release of HB until Singular is updated tomorrow. -Bobby53
HB7032V76, Greatly appreciate the log file, but to make it fully useful I need to know when you saw the issue occur. A LOGMARK is the best way to indicate that, but providing the log timestamp works as well (just more work for you.) I see a lot of LUA failures. I am going to look into that further. -Bobby53
copyleft, While I appreciate your taking the time to post, that statement is incorrect. It would be more useful to provide a post as described in Reporting Bugs [CLICK HERE]. It is an HonorBuddy bug as it wasn't handling the DeathBehavior correctly. As it stood, the DeathBehavior was being handled differently by multiple BotBases. Singular was modified to address a previous bug when interacting with DungeonBuddy. This exposed an undetected bug in HonorBuddy. It has since been fixed in a subsequent release of HonorBuddy, so you should be able to update and have your problem resolved. -Bobby53
kravitz, Thanks for the follow up and log file. You are on your own with running PQR at the same time. Cool idea, but I can't provide support for it. It's the equivalent of a user /facerolling the keyboard while Singular is running. Singular automatically determines the shield that makes the most sense based upon the context you are botting in and the current combat scenario. If you are in a context where you have Earth Shield on your toon and believe Water Shield is more appropriate, follow the steps in Reporting Bugs for posting a log and providing a LOGMARK for the moment you are referencing. As for the targeting, that is the BotBases responsibility. It specifies and selects the target then invokes the Combat Routine only when it is needed. Once combat is over, the Combat Routine doesn't play any active role. If the current target cleared when it is dead, you'll post to the author of the botbase you are using that it is not clearing the target after death, looting, etc.. Thanks for the post, -Bobby53
ShortRound, I have to tell you knockbacks in a LFR is one of my guilty pleasures and you are asking for me to disable that ? LOL -- I truly enjoy being on my Feral Druid and waiting for a Boomkin to drift close enough for plausible deniability then casting Typhoon and immediately start /yell-ing at the Boomkin. Wouldnt fly in Guild runs, but in most LFR's they always blame the Boomkin even when he doesn't have it talented. With the change in Cata to Glyphs being learned once, the Glyph actually serve as your setting. My suggestion has been for raiders to keep a stack of Tome of the Clear Mind around for glyphs they want to control for botting. It's 50 silver each and you have definitive control of whether you have knockback or not. Hope that helps, Bobby53
View attachment 92096 2013-09-20 13.28.txt Running in my 5 man in partybot, leader using grind bot and singular. It doesn't seem to care if mobs are tapped, it attacks them any way. Is there a way to prevent this? Attached log has 2 mob fights in it. The first is non-tapped, the second is tapped.
