Tumbum, Thanks for the post, but if the quest profile needs to interact with an object it will either need to first disable the combat routine (so the Questing botbase does not call it) or use the appropriate Quest Behavior for the interaction. Please report the issue to the profile author if still occurring, -Bobby53
hodge74, Thanks for the post. While Singular allows customization of many things, selecting the offhand imbue for Enhancement Shaman is not one of them. -Bobby53
FadetoGrey, Thanks for the post. I'll look into this further and follow up when something more determined, but at this point still looking into it. -Bobby53
FadetoGrey, I ran my Warrior in a like manner and was unable to duplicate. Please follow the steps in Reporting Bugs (click here) post which describes setting Log Level to Diagnostics and using a LOGMARK to indicate what point the problem occurred and I will research further for you. Thanks and good luck with your Warrior, Bobby53
prostatemonkey, Thanks for the post. After reviewing your diagnostic log file was able to determine the source of the problem. I had made some improvements in the last release with trap handling and diagnostics, but unfortunately introduced an error. Fix will be included in next release which will be available after some additional testing and review. Thanks again and good luck with your Hunter, Bobby53
Shaman: "Twist Water Shield Mana %" 15 is to low as default (for low level chars) my (lvl 48) enhancement shaman is a lot out of mana default it should be 40-50%
*new* Singular v3.0.0.3421 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. Code: [B]--- Release 3.0.0.3421 --- [/B] General fixed - exception occurring when checking Auras and unit goes invalid Hunter fixed - All Specs - bug preventing Traps from being set when using Launcher Paladin note: Blinding Light support will be in next release. This update issued quickly to address Hunter trap issue Rogue *new* - All Specs - Pick Pocket Only Pull setting (usable only with Grind Bot or profiles designed specifically for pick pocketing only.) Will only pick pocket mobs and avoid combat whenever possible. Must be solo (disabled if in party/raid) fixed - All Specs - Pick Lock: now correctly recognizes Heavy Junkbox 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.
What Class+Spec are you?: Prot Warrior What 'context' is the bot in? (Instance, BG, Normal): Questing What level are you?: 61 Have you made any modifications to Singular?: no What time (HH:MM:SS) or LogMark did your issue occur? Logmark 1&3, Logmark 2 What happened (be specific)? Logmark 1&3: targets enemy and begins to run towards them, at the same time tries to move somewhere else repeatedly darting back and forth. Logmark 2: pulls and enemy then walks away from it. Did you attach a complete debug log? (choose one: YES or YES) Yes View attachment 4128 2014-04-16 12.29.txt
kloopy, Thank you for the detailed post! Issue pertains to Protection Warrior only and will be releasing an update later today. Thanks for taking the time to post and good luck with your Warrior, Bobby53
*NEW* Singular 3.0.0.3427 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. Code: [B]--- Release 3.0.0.3427 ---[/B] Paladin *new* - All Specs - will cast Blinding Light when solo or battleground. Cast if current target is player facing you or 3+ mobs attacking you Warrior fixed - Protection - fixed exceptions causing failed pulls and some erratic movement with some Quest Behaviors [B]--- Release 3.0.0.3421 --- [/B] General fixed - exception occurring when checking Auras and unit goes invalid Hunter fixed - All Specs - bug preventing Traps from being set when using Launcher Paladin note: Blinding Light support will be in next release. This update issued quickly to address Hunter trap issue Rogue *new* - All Specs - Pick Pocket Only Pull setting (usable only with Grind Bot or profiles designed specifically for pick pocketing only.) Will only pick pocket mobs and avoid combat whenever possible. Must be solo (disabled if in party/raid) fixed - All Specs - Pick Lock: now correctly recognizes Heavy Junkbox 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.
Twisty, Dark Simulacrum support added in next release. As for Howling Blast, that isn't enough info. You will want to follow the steps in Reporting Bugs (click here) if you observe behavior you would like me to research. -Bobby53
Hello, I have looked around but can't find how to disable mana potion use for none mana classes or all of them. I have try to set "potion at mana%" to a negatve value but it's not working. edit: attached logs Regards. Mgl
mglbd, Thank you for the log file, but it lacks the diagnostic info I need to research issues. Please be sure to follow the steps provided in Reporting Bugs (click here) if you encounter a behavior while using Singular that you would like me to research for you. I have seen this issue reported before however so can advise on what occurred. First, it is important to note that any action taken by Singular (your combat routine) which appears in the log window or log file will begin with the text '[Singular]'. For the symptom you described, the relevant lines from the log provided are: Code: [10:06:33.202 N] EnabledPlugins:[10:06:33.202 D] Anti Drown [B][10:10:06.257 N] Used Potion de mana supérieure![/B] You will notice that the line is not prefixed with the tag [Singular], so the Greater Mana Potion use was invoked by a different component. In reviewing your log, I noticed the following: Code: [10:06:33.202 N] EnabledPlugins: [10:06:33.202 D] Anti Drown [B][10:06:33.202 D] DrinkPotions[/B] The DrinkPotions plugin does not check if your character uses Mana and will consume them if the plugin is enabled and a mana potion exists in your bags. If you disable that plugin, you should no longer encounter a problem. Note: the Drink Potions plugin is not needed with Singular and is provided in support of non-Singular combat routines. Singular provides full support for Health, Mana, and Restoration potions and provides settings in the Class Config section allowing you to specify when they are used. That support also includes other consumables which restore health and mana such as Healthstones, Life Spirit, and Water Spirit. Additionally, Singular only uses Mana replenishment items on characters which use Mana for energy. Thanks for the post and good luck with your previously mana thirsty Warrior, -Bobby53
howling blast seems to be working correctly on a new dk that I'm leveling via Kick's profile. Good to hear about dark simulcrum - any idea when it will be released?
Questing Druid - Feral Toon try to kill an Yellow NPC while Turning in a Quest and Targetting him. [11:29:31.207 N] (Singular) YourCurrentTarget: changed to: Sage Highmesa.004B
Tumbum, Thank you for the diagnostic log and the specific point of reference. In the lines just prior to the point of reference given, some active component set the BotPOI to a type Kill and named the yellow mob you provided as the target: Code: [11:29:30.907 D] Changed POI to: Type: Kill, Name: Sage Highmesa [11:29:30.979 N] (Singular) YourCurrentTarget: changed to: Tundra Crawler.42EB h=100.0%, maxh=8982, d=48.9 yds, box=12.0, boss=N, trivial=N, player=N, attackable=Y, neutral=N, [COLOR=#ff0000][B]hostile=Y[/B][/COLOR], entry=25454, faction=14, loss=Y, facing=N, blacklist=N, combat=N, flying=N, abovgrnd=N [11:29:30.982 D] [QDBG] Done with forced behavior Bots.Quest.QuestOrder.ForcedIf. [11:29:31.130 D] Goal: Nothing [11:29:31.130 D] [QDBG] Starting behavior [ForcedQuestPickUp QuestId: 11677, QuestName: Stop the Plague]. [11:29:31.141 D] Goal: Picking Up Quest - Stop the Plague : QuestID - 11677 : To - Sage Highmesa : ID - 25604 [11:29:31.207 N] (Singular) YourCurrentTarget: changed to: Sage Highmesa.004B h=100.0%, maxh=18582, d=4.9 yds, box=4.1, boss=N, trivial=N, player=N, attackable=Y, neutral=Y, hostile=N, entry=25604, faction=1921, loss=Y, facing=Y, blacklist=N, combat=N, flying=N, abovgrnd=N, IsBotPoi=Kill so appears to be working as intended from the Combat Routine perspective. Singular doesnt take action on its own to kill things as it is primarily passive and waits to be given a target and told to kill it. That is what happened here. What component initiated that is unclear because it did not announce its intentions and we dont get information indicating when a plugin has modified the targeting filter. You may want to disable your plugins or check them for possible sideeffects in this case. If the mob wasnt aggroed to you though, I agree with you in that it should not have been attacked. -Bobby53 Edit: Just noticed in the log snippet that I pasted that although the mob is Neutral, it appears to have turned Hostile after turnin. That is likely the reason for core, botbase, or one of the plugins for attacking it.
Just a quick question regarding the mage routine... specifically in arcane spec. It sometimes forgets to case arcane rune after moving and there are times when i dip to 20% mana which is not good Also is there any way to let it multidot and to use a bomb instead of arcane blast?.
