So your only real reason for this logic is that you like being an asshat to boomkins? Took me a while to figure out why my group kept overpulling. I blamed the boomkin as well yet couldn't find any reason for it. Sad thing is this was a full bot group all running...Singular.
I don't know if it's important, but i recognized a NullReferenceException while looking at the logs. Maybe it's interesting for you? It happens at [09:41:57.719 D]. What Class+Spec are you?: Demo Warlock What 'context' is the bot in? (Instance, BG, Normal): Questing Hyjal What level are you?: 82 Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? [09:41:57.719 D] What happened (be specific)? Can't say. Found it while studing the logs.
Jonasx, Thanks for taking the time to post. Unfortunately there isn't an indication in your post of when that occurred. Additionally, the log file however is not a debug log: The HonorBuddy Log Level setting defaults to Normal so it won't include any debugging output. To enable debug, change the Log Level to Diagnostic and the log will contain the information I need to look into the issue for you. In general the BotBase decides what to target, but I am happy to look at this circumstance further as needed and either modify Singular or let the HB developers know a change is needed in the Grind bot. Just repost with a debug log and be sure to either add a LOGMARK or specifically identify what time the problem occurred and and I'll research for you. For details see the Reporting Bugs [CLICK HERE] post. Thanks again and good luck with your grinding, Bobby53
No, the knockback I was referring to was via a keypress, not anything coded into Singular. I stated my reasoning for not providing an option is that you already have control of knockback for your Hunter by choosing whether to equip/remove the glyph. Since you already have control no additional option is needed. Thanks for the post and good luck with your Hunter, Bobby53
Hi Bobby Thanks very much for creating the Singular Routines. I run many toons and have found this routine to be the best in dummy tests in 3 out of the 5. I am having one issue in configuring the Routine and wonder if someone can suggest how to solve it. What Class+Spec are you?: Paladin - Retribution (as an example but also applies to the Priest, Shaman, Hunter and Druid as well) What 'context' is the bot in? (Instance, BG, Normal): Raid What level are you?: 90 Have you made any modifications to Singular?: None What time (HH:MM:SS) or LogMark did your issue occur? All the time (obvious from comments below) What happened (be specific)? I cannot Suspend Honorbuddy while Raiding Did you attach a complete debug log? (choose one: YES or YES) No as it is not really a bug. HB works fine. System: Windows 8 HB Version: v2.5.7857.658 and the Singular versions that came with that file (v3.0.0.3022) I would like to suspend HB periodically while in Raid and recommence it with a hotkey. At times, it is necessary to stop the dps routine and do a certain function like mass dispel (as a Shadow Priest) and then recommence the dps after that. Is there a way to do this whereby I can suspend HB and recommence it with a hotkey? This is what I have tried without success. I have opened up Class Config and then the Hotkeys tab. I have tried to change the Suspend Keys to "F1" . However, when I try to save that key combination of "F1", it does not save that key combination. I don't even know if this is the correct place to configure HB to be suspended. Could you explain what I need to do to get a hotkey that will enable me to suspend HB temporarily? Thanks Lanmaro Apologies if this is a newbie question - but I have not been able to find a solution while trawling through he pages.
singular isnt working with latest honorbuddy it gives an error but the singular that comes with honorbuddy works.
Lanmaro, Thanks for the post. If you have a problem or question, the best thing you can do to receive a timely and accurate answer is follow the steps in Reporting Bugs [CLICK HERE]. That will walk you through creating a debug log file, adding a LOGMARK at the point the problem occurred, and the information you will need to provide along with that log. To accomplish what you are requesting, use LazyRaider (link in my signature.) It is a manual assist bot that allows you to control the movement and targeting while the Combat Routine of your choice handles the spell priority. LazyRaider has a Pause key which allows you to temporarily pause all activity. If you have any questions or issues with LazyRaider, please be sure to post in that thread. Singular does disable the use of AOE spells when you press the AOE Hotkey. I will need to see a debug log to be able to assist further, but be sure to follow the steps in Reporting Bugs as I mentioned so it contains debug info otherwise the log will not be of use. Singular cannot be configured to Pause all activity. The Temporarily Suspend Movement hotkeys do just that. When they are activated they stop movement for a brief period of time, then movement is automatically re-enabled. The purpose of this is to allow the user to setup keys they use in WOW for movement as Temporary Suspend Movement keys, so when the user takes control in game of movement, Singular will temporarily disable movement allowing you full control. That will have no impact upon
View attachment 3268 2013-09-22 19.51.zip I'm having a bit of trouble with my singular CC. What Class+Spec are you?: Warlock, Affliction What 'context' is the bot in? (Instance, BG, Normal): Normal What level are you?: 50 Have you made any modifications to Singular?: No, but HB says I have though I haven't changed anything since initial install. What time (HH:MM:SS) or LogMark did your issue occur? Each logmark I've marked has been an instance of the same thing happening What happened (be specific)? CC will often run past and aggro multiple mobs, then (only with 2+ mobs) instead of casting dots & killing, it will only use 'Malefic Grasp' and no other spells. CC does not ever use health funnel on summoned demon, instead just waits till it dies and re-summons a new demon. Sometimes generates Soulstones but always releases and runs back to corpse instead. Doesn't Loot every mob, runs from mob to mob, sometimes up to 6 or 7 times before looting 3-4 of the mobs (sometimes i'm lucky and they're within loot circle so it's ok). Always casts twilight Ward 24/7, even when not battling shadow-dealing mobs. Did you attach a complete debug log? Yes.
Destruction Lock - 89 - Questing with Kick's Profile - Stock Singular The post above seems like a lot of the same issues. Unfortunately I forgot to flip on the Singular debug, but I'll get that in a bit if it helps. There are 4 logmarks to help identify the key areas. 1) Low health on pet. We are fighting a mob, but not trying to heal at all. 2) We're killing one mob, drop target, and move to another mob. The first mob hasn't died yet, however, my pet does have aggro. It seems when my pet takes aggro, the bot pulls another mob. This doesn't happen every time, but it does happen frequently. 3) Voidwalker dies and we haven't tried to heal him at all. 4) We summon the VW again. Summoning works, but healing seems to have completely stopped.
Sounds like we're having the same issue my friend. Curious about it though, i think it might be the latest version. I'm gonna downgrade to the previous version of HB and see if that changes anything.
2) We're killing one mob, drop target, and move to another mob. The first mob hasn't died yet, however, my pet does have aggro. It seems when my pet takes aggro, the bot pulls another mob. This doesn't happen every time, but it does happen frequently. Same issue, especially with number 2
Thank you for the posts. Unfortunately a debug log was not attached to the posts. Please be sure to set Log Level to Diagnostic when Questing for now so if you encounter an issue the log you already have contains that info. Also note I need a point of reference regarding what point you had the problem, ideally a LOGMARK. See the Reporting Bugs [CLICK HERE] post for details. I am gathering info for the HB Devs as the issue I am seeing (which may not be the same one you are seeing) is that the Questing (either botbase or qb, not sure) is changing its mind after already invoking Pull Behavior for a mob decides another mob should be targeted. While I am in this area would like to review the issue you are reporting as well, so greatly appreciate any debug log you can get me. Thanks for the posts, Bobby53
*new* Singular v3.0.0.3080 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.
[Singular-DEBUG] reset target timer to 00:00:20 log on diagnostic mode. Toon targets quest mobs but does not attack. I have the latest zip installed.
Logmark 1: Demon very low on health (almost about to die, but locks are insane so he doesn't) and we haven't tried to heal him. Logmark 2, 3, and 4: We start killing a mob, drop target, and move to the Injured Gao-Ran instead of staying to kill the mob. It says this quite a bit: [InteractWith-v719(warning)] Unable to engage "Mob Name Here" in 5s--pull-blacklisted for 3m00s As soon as it says that, it switches and decides to go do a quest behavior instead of killing the mob. Definitely doesn't look like Singular, but hopefully you can forward it up!
89 Questing in Townlong : Destro Warlock We stand at the Scout Long (literally right on him) for quest Restless Watch, but we don't interact. Debug log attached.
odarn, Thanks for the debug log file. The issue is due to a bug in the Holy Priest Solo Combat logic. It isn't recommended that you quest as a Healer spec, but it is supported. To work around, change specs to Shadow or Disc while questing. Will be fixed in next release, Bobby53
