Running a bot while questing that will run to the mod and engage it, but then doesn't cast any abilities. Using DK combat routine. I just get this on ALL my abilities: Attached log below. I should mention I have another DK bot that is running at the same time and is running just fine.
Lokhan, Thanks for the post. The log file attached is a partial log file and is missing a lot of the detail I need about your session. Please also set the Debug Logging setting to true in Class Config form so additional detail about what is going on is provided. Thanks for the post and good luck with your DKs, Bobby53
exxezzz, Thanks for the log file. That is a Quest profile or Quest behavior issue: Code: [Ref: "[A - Quest] 85-86 The Jade Forest [Kick] ($Rev: 2455 $)" @line 921][04:42:50.380 D] Inserted new hook [Combat_Main @0] 8bf89439-3420-4c35-8401-d50eaffe5e30 [04:42:50.380 D] Inserted new hook [Combat_Only @0] 2e626d1e-93f7-4484-ba09-b648a4a24cb6 [04:42:50.380 D] Inserted new hook [Death_Main @0] 46515353-7352-49f9-b6ec-2282f6667c52 [COLOR=#ff0000][B][04:42:50.703 D] [Singular-DEBUG] warning: Pull Distance set to 0 yds by Questing Profile[/B][/COLOR] [04:42:51.702 D] Activity: Waiting for respawn of MobId(64596) [04:42:54.611 N] [Singular] Casting Cat Form on Me @ 100.0% When the Pull Distance is 0, the Questing botbase does not call the Pull Behavior of the Combat Routine (in this case Singular) because no mob can be at a distance < 0 yards. Although the message highlighted above was output by Singular, it was merely reporting the situation since it affects its behavior as it did here. Thanks for the post and good luck with your Druid, -Bobby53
See Bobby53's Standard Request for More Info [CLICK HERE]. Another user submitted a similar issue with log file, so assuming you have the same problem it will be resolved in the next release. Until then you'll need to BG as Holy or Shadow.
klodzio12, Thanks for the post with Log file! That behavior is due to a bug introduced in the Disc Priest rewrite and will be fixed in the next release. Until then, the only work around to use your Priest with Singular in a Battleground is as Holy or Shadow. Thanks for the post and good luck with your Priest, Bobby53
[Singular] Behaviors disabled in Pet Fight What Class+Spec are you?: SHAMAN ENH What 'context' is the bot in? (Instance, BG, Normal): GB2 + PokehBuddy What level are you?: 90 Have you made any modifications to Singular?: NO What time (HH:MM:SS) or LogMark did your issue occur? EVERYWHERE What happened (be specific)? No interference, just log spam Did you attach a complete debug log? (choose one: YES or YES) YES Hello. I'm running PokehBuddy with Gatherbuddy and Singular. I keep getting this message spammed all over the log: [Singular] Behaviors disabled in Pet Fight - contact Pet Combat bot/plugin author to fix this If I understood, this message should be directed at the PokehBuddy author and not you, but I thought I'd check. Thanks for you time. Log File: View attachment 5444 2013-06-21 23.29.txt
Tamahawk, Thanks for the post with log file! Yes, you are correct -- this indicates an issue with the botbase or plugin you are using. Singular currently includes a hack to allow recognizing when it is in a pet fight and disabling its behaviors (which shouldn't have been called during a pet battle.) The botbase or plugin providing Pet Battle support should be taking control so the Combat Routine (in this case Singular) is not called. That isn't being done in some of them however, so it is temporarily being accounted for in Singular (when you are not in a Raid.) Thanks for the post with log and good luck with your Shaman, Bobby53
*NEW* Singular 3.0.0.2638 available for download! Change History for this release appears below. Complete Change History as always is included in the .ZIP See the Reporting Bugs [CLICK HERE] post for details on how to request assistance, post about a problem, or ask questions about the behavior of your botting session with Singular. Still receiving too many bug/question posts regarding behavior users watched that don't contain a complete log file and point of reference to when a single event happened. So, no multi-color bright lights this time. Just a simple request to provide the detail. Don't forget to use the LOGMARK! button. It is located on the Class Config window and will place a mark in the log file making it easy for you to indicate when something happened that you have a question about or problem with. This button provides the same behavior as the LOGMARK plugin. Having a problem while running Singular that you want to report? Click the LOGMARK button immediately when you notice. A line will be added to the log file at that time and now you have a very accurate way to let me know when the problem occurred. Ok, now that's out of the way: - Download the latest version of Singular.ZIP from Post #1 in this thread - .ZIP in Singular thread will always be the current version - HonorBuddy will contain an older version until a new release of HB posts Any post must include a debug log file (a file created with Debug Logging set to true.) To do this, click Class Config and set the Debug Logging option to 'true' then run until you create the issue again. The resulting log file will contain more info than a standard log file which will be essential in understanding the decisions being made by Singular which you weren't expecting. As always, the prior version is still available for download. If you encounter a problem due to the new release of Singular you can always downgrade as needed. Worth mentioning one more time due to the large number of posts without log files that are received, but you must attach a complete debug log with any post. Please see the link at the top of this post for details.
Hi bobby53, i have no bug to report but would like to request a small setting/option within the class-config.. Enable/Disable facing targets out of combat using singular in conjunction with my plugin http://www.thebuddyforum.com/honorb...ataloged/123631-plugin-nobothere-1-0-0-a.html creates odd behavior, especially in battleground starting zones, where the plugin occasionally targets other players and always perfect faces them - even if they move. regards, randomstraw
randomstraw, Thanks for the post, but that is a bug. A change was made quite awhile back so that Singular does not face targets out of combat, but the class/specialization you are using may have remaining logic causing it to face. Please attach a log and I'll be happy to research for you. Thanks for the post, Bobby53
Hi bobby53, thank you for the reply. I'll attach a log that run some, until i turned my plugin off [log is cut here, was 12mb... and there shouldnt be anything important after.] searching for [NBH]: [Targetting: will indicate where the plugin did work. thank you.
randomstraw, Thanks for the post with log. There was a stray command in the Hunter Rest behavior causing Hunters to face out of combat. That will be fixed in the next release. This is only impacting Hunters so you should not see that behavior with any other class. Thanks for the post and good luck with your Hunter, Bobby53 [size=-2]Ref: Randomstraw's original post w/log[/size]
What Class+Spec are you? Druid, Restoration What 'context' is the bot in? (Instance, BG, Normal): Grinding, Normal What level are you? 54 Have you made any modifications to Singular? No What time (HH:MM:SS) or LogMark did your issue occur? Logmark 2 What happened (be specific)? I died because my Character does not use self heal, Restoration for example. Only if he is not infight. Did you attach a complete debug log? (choose one: YES or YES) Private Paste - Pastie
Any progress or ideas on the Savage Roar not working? Crucially important, especially with the glyph.
Hi, rogue pickpockets, but wont lockpick the chest, just use skill, but no targeting the chest, between logmarks 1 and 2. View attachment 4404 2013-06-23 03.35.txt
Zetto, I'm not encountering an issue with Savage Roar not being cast. You'll want to follow the steps in Reporting Bugs [CLICK HERE] for me to look into why it is not being cast for you. Be sure to set the following Options before running: Settings & Tools: Set Log Level to Diagnostic Class Config: Set Debug Logging to true Set Debug Spell.CanCast to true Thanks for the post, Bobby53
iezequil, Thanks for the post with log file. Unfortunately I am not experiencing any problems with Pick Lock. To look into this further for you I will need a log produced with some debug settings. Be sure to set the following Options before running:Settings & Tools: Set Log Level to Diagnostic Class Config: Set Debug Logging to true Set Debug Spell.CanCast to true That should include enough information in the log file for me to trouble shoot for you. Just run again and post the new log and I'll look into this again for you. Thanks for the post, Bobby53
