ye i run 5 bots witch is annoying i only quest lvl up classes i dont farm with gatherbuddy and it also has a bug in hb when targeting a mob it keeps targeting it sometimes.
Standard Response to Incomplete Posts [CLICK HERE] Standard Response to Incomplete Posts [CLICK HERE] Standard Response to Incomplete Posts [CLICK HERE]
No, that's incorrect. I think you misunderstood my request for you to "try" the English client to assist me in troubleshooting your Rogue's Pickpocket issue. Non-English clients are supported and statements suggesting otherwise are incorrect and will mislead other members. Thanks for your post and good luck with your Rogue, Bobby53
*NEW* Singular 3.0.0.2150 available for download! 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. I continue to receive numerous posts from veteran forum members that don't include the details needed (as described in Reporting Bugs linked above. So, trying a slightly different approach to communicate this time and we'll see how it goes: you must attach a complete debug log with any post you must attach a complete debug log with any post you must attach a complete debug log with any post 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 above link for details. 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 This is both a bug and enhancement release. Fixes for a number of reported bugs are present (thank you for taking the time to post!) Also include are a lot of changes to Holy Priests. Any post regarding Holy Priest spell priority, mana management, configuration, etc. 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.2150 --[/B]- [B]General[/B] *new* - Extensive rewrite to Holy Priest support. See the Priest section for info. change- Class Config form (settings GUI) now dynamically sizes. The size of the form and the current tab displayed is remembered. *new* - Solo Pet Tanking. While solo, classes with a Pet will send that pet to agro targets attacking the player, as long as the pets current target is not the player. This will increase survivability in multi-mob fights especially at lower levels. A setting in Class Config named Solo Pet Tanking can be set to false if you prefer the Pet remain on your current target. This applies to solo (questing/grinding) only. In PVP and Instances, the Pet will always attack players current target. fixed - problem with list of Bosses not initiliazing change- Singular no longer prevents Combat or other behaviors when on transports. This was interfering with some DungeonBuddy scripts. The primary place this would be needed is during questing and that should now be handled by Quest Behaviors if needed change- Heal settings are output to long once per context change. previously output for each behavior which referenced them creating setting spam in log in some cases. Currently only noticeable with Shaman and Holy Priests change- Auto Attack started only for Melee classes/specs. This has been requested numerous times, so if you encounter any issues be certain to attach a complete debug log with your post fixed - Targeting. Singular does not target often, but will validate the current target and switch if the Bot indicates it should. Some minor refinements as well as a bug fix for some cases where Questing bot had a BotPOI that was different than the Targeting.FirstUnit it prioritized fixed - workaround for some issues where HonorBuddy SpellManager.canCast() was indicating false for certain spells. fixed - Evade mobs issue (character stops fighting back.) Mobs in WOW have begin having single Evade spell misses without being evade bugged, causing issues with Combat Routines that check for Evade bugged mobs. Singular will now require a minimum number of evade misses on the same NPC before it will be treated as evade bugged. [B]Hunter[/B] change- All Specs - Misdirection will only be cast as part of Pull Buffs in Instances. If the BotBase in use does not call the Pull Buffs behavior (Raidbot for example) you will need to cast Misdirection manually if needed or request a change to the BotBase. fixed - All Specs - Revive Pet should now work. Additional logging added in this area, so be sure to attach a complete log file if you continue to have a problem *new* - All Specs - support for Heart of the Phoenix as instant Revive for Tenacity Pets *new* - All Specs - support for Bullheaded and Last Stand pet abilities change- All Specs - will no longer cast stun or slow abilities prior to Disengage if the Narrow Escape talent is taken (since that does it for you.) [B]Shaman[/B] change- Elemental - additional log info to help identify issue where character stops fighting [B]Mage[/B] *new* - All Specs - should now summon refreshment table during last 15 seconds of Battleground Preparation phase (prior to start.) Previously only summoned table if the Mage needed food. [B]Monk[/B] fixed - Mistweaver - should now remain in Stance of Wise Serpent at all times change- Mistweaver - will consume Mana Tea during combat in all contexts. Previously was only during Rest [B]Paladin[/B] change- Retribution - in Normal and Battleground contexts, will cast Guardian of Ancient Kings if 4 or more mobs or current target will live more than 30 seconds. Previously only cast for AOE situations [B]Priest[/B] *new* - Holy - rewrite of Instance and Raid healing logic *new* - Holy - heal settings now appear on the Group Healing tab of Class Config. Separate values for each healing context are kept (Battlegrounds, Instances, and Raids) change- All Specs - Shadowfiend and Mindbender now share the same mana % setting in Class Config. Default increased from 50% to 75% and is only cast if current target expected to live longer than 15 seconds [B]Rogue[/B] *new* - All Specs - added setting Fan of Knives Count to allow user to control number of mobs required for FoK to cast fixed - Combat - when Blade Flurry is active will favor using Eviscerate over Rupture as finisher *new* - All Specs - support for Shadow Blades [B]Warlock[/B] fixed - All Specs - Pet summoning logic should now work as expected on all systems. Will now wait slightly longer after Dismount, will summon Pet more quickly if it dies during Combat, and will cancel a summon in progress if live pet appears while Summon Pet cast is in progress fixed - Demonology - Doom check for target life expectancy increased from 30 seconds to 45, as on machines with lag we were still casting Doom on characters it would never tick on
going to test this new version once i start my quest bots today again lets hope its now fixed to with the missed spell thing and mob targeting. then im really happy
singular version 50 seems to be working nice the new one didnt seen a bugged mob spell hit yet but i wil look at it more it seems to be targeting fine now to.
Trying to do heal as discipline in bgs using the default profile and routine and its throwing all kinds of problems ends up doing a few bgs then stopping and going afk. Tried a fresh install and having problems still only plugins are watch the chat and gearbuyer. *trying update will post back if still problems.
this new version looks nice the 50 version it even tags friendly mobs now that are yellow with quest thnx for this update the one quest in uldem it never took those camels quest because they where yellow now it does awsome
To All Singular Users: Prior attempts to explain what is needed did not work (just scroll up a few posts for the pi?ata colored messages), so some literal example of real posts may work better: Example of Post that will be ignored [CLICK HERE] Example of Post that gets prompt attention [CLICK HERE] Thanks for reading and good luck with your Singular toons, Bobby53
All CR Debuggings are turned on in the Logfile ---- Release 3.0.0.2150 --- What Class+Spec are you?: Paladin Retri. What 'context' is the bot in? (Instance, BG, Normal): Guadians of Mogushan LFR What level are you?: lvl90 Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? from [17:16:03.045 N] to [17:16:39.602 N] AND [17:34:41.752 N] to [17:35:20.288 N] What happened (be specific)? Did you attach a complete debug log? (choose one: YES or YES) There are times where my toon, in this Raid my Paladin, are doing nothing. Just use AutoHit no Spells nothing. I got this Situation on my Shaman too, from time to time. First Timestamp is from the first Boss and Second Timestamp from the last one.
Anth, Thanks for the post with log file. The description is a bit vague however so I am not sure exactly what it was you were seeing as all kinds of problems during the BG. I did see an issue via the contents of this log file that will be fixed in the next release which appears will affect all healers trying to reference a heal target that has gone out of range or left the group. If you want to specify any specific issues that you may have encountered I'll be happy to look into them further. Thanks for the post and good luck with your Priest, Bobby53
View attachment 11984 2013-04-03 11.18.txt Having problem with rogue during questing with attacking mobs.It sometimes attacks and at other time it just stands there doing nothing i say 40% of the time.I checked to see if it was a plugin but i don't think it is.is this just a bug or do i need to fix something in settings?
tumbum, Thanks for the post. Please do not post any additional logs at this time. We are going to focus on your Retribution Paladin for now. I will have a paladin specific debugging release available for you shortly that will help narrow down specifically where it is going wrong. Look for a follow up post from me shortly, Bobby53
dna9418, Thank you for the attached log file. Unfortunately I'll need more information to be able to research this for you. Specifically, I need a point of reference where you observed it doing nothing. This can be a LOGMARK you add (see LogMark plugin in my sig), the local system time on your computer when you see it occur, or possibly the name of a uniquely named mob (a boss for example) that the problem happened during. The Reporting Bugs [CLICK HERE] post describes this and provides a template you can copy and paste. Without a point of reference and no obvious errors, I don't really know what part of the log file to focus on. That is especially true in cases where the problem is the absence of something. Thanks again for your post and I'll keep an eye out for your follow up, Bobby53
tumbum, Thanks for your patience. In preparing the debug version I mentioned, I found the issue you encountered in this log. There was behavior which occurs only during Bloodlust, Heroism, etc. where it attempts to use a potion. However, the potion consumption was handled incorrectly so it was repeated over, and over, and over, etc. until Bloodlust expired. The result was a 40 second (duration of Bloodlust) pause in combat which matches what is present in your log: Code: [17:34:40.523 N] [Singular] Casting Exorcism on Gara'jal the Spiritbinder.0082 @ 99.5% at 3.2 yds [COLOR=#0000ff][I]... followed by 40 seconds of ....[/I][/COLOR] [17:34:42.819 N] [Singular-DEBUG] .... h=100.0%, m=100.0%, moving=False, mobs=1, Gara'jal the Spiritbinder.0082, 98.7%, 4.9 yds, loss=True [COLOR=#0000ff][I]... and then casting resumes ...[/I][/COLOR] [17:35:21.273 N] [Singular] Casting Inquisition on Me @ 94.3% I know you mentioned this occurring with your Shaman too. That would be due to something else and is not related. Although Bloodlust/Heroism was mentioned which is clearly a Shaman spell, the code causing the issue is unique to Retribution Paladins and only in their Instance spell priority. Any other stoppage you encounter other than the one specifically described here for your Ret Pally is due to something else and would need to be researched separately. Look for a fix for the Ret Pally issue in the next release, Bobby53
What Class+Spec are you?: Shaman Ele. What 'context' is the bot in? (Instance, BG, Normal): Questing Dailys Golden Lotus What level are you?: lvl90 Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? from [18:54:05.676 D] to [18:56:23.788 N] AND [18:58:34.258 N] to [19:02:41.504 N] What happened (be specific)? Did you attach a complete debug log? (choose one: YES or YES) Toon get hit, but doesnt Fight, just stand there push down the Totems and Heal himself.
tumbum, You currently have your Pull Distance set to 1. Here is the config info at HB startup: Code: [18:39:07.117 D] PullDistance: 1 Singular will output a warning when the Bot is started as well: Code: [18:42:33.595 N] [Singular] Your Level 90 Tauren Elemental Shaman Build is [18:42:33.595 N] [Singular] ... running the Questing bot in Shrine of Two Moons [18:42:33.595 N] [Singular] ... Zone: Pandaria using my SOLO Behaviors [18:42:33.660 N] [B][Singular] your Pull Distance is 1 yds which is low for any class!!! [/B] If you get that message at startup, you'll want to Stop the bot, click Settings and change it to between 30 and 40 for an Elemental Shaman. Some of Kick's questing profiles temporarily set it to 1 yard to avoid getting into combat. If a profile aborts or doesn't include the code to restore the original value, you'll end up with 1 set as your choice for Pull Distance. I rechecked the log you submitted previously for your Elemental Shaman doing dailies. The Pull Distance there was set to 20, so I don't believe the Pull Distance was the only issue you encountered. Changing Pull Distance to the values I mentioned will give you better results in other circumstances, but it seems there is another circumstance affecting you as well. No other data needed at this time. Will look specifically at the quest from your earlier log and follow up tomorrow. Thanks for the post and the detailed submissions, Bobby53
