Hey bobby is it possible to add in hunter routine line that bot don t pulling and killing btw hot spots ? I appropriate any help ty !
I try everything but nothing work i only manage add in quest profile HTML: <CustomBehavior File="FlyTo" Land="True" X="1365.073" Y="2136.622" Z="361.6244" /> but then bot just flying btw these cords and not attacking
Please blacklist the following items for the bot to consume. Focus Augment Rune Hyper Augment Rune Stout Augment Rune These can appear as dungeon reward for specific roles and drop very often from bosses in Raid Finder These are BoE and many of us want to either sell them or send them to other characters for use for raiding. They should never be allowed to be consumed by the bot once looted.
Yes this god please! I just lost 20 of them! that's like 2k I will seriously donate to someone that can fix this.
What Class+Spec are you?: Blood Deathknight What 'context' is the bot in? (Instance, BG, Normal): Questing/Grind Bot What level are you?: 68 Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? N/A, Passive What happened (be specific)? Does not ever use Plague Strike Did you attach a complete debug log? (choose one: YES or YES) Yes, no wait...yes
trtamrta, Thanks for the post. As mentioned earlier, to receive support you will need to provide a log file as described in Reporting Bugs in Singular (click here). Singular is a Combat Routine. Combat Routines (all of them, not just Singular) are told when to attack by the BotBase (in this case Questing.) You control what the Questing BotBase attacks with a quest profile. Additionally, the questing profile supports a lot of custom behaviors in addition to your use of the FlyTo custom behavior. For support in using the Questing BotBase or writing Questing Profiles, you will want to begin by posting in the HonorBuddy Support forum. Thanks for the post and good luck with your toon, Bobby53
Instead of a donation, just provide a log file. To receive support follow the steps described in Reporting Bugs in Singular (click here). This isn't an optional step. Happy to address any consumption being done by Singular or advise on how to prevent outside of Singular once the issue with log is posted. -Bobby53
Thanks for the log. This appears to be specific to Normal context (Solo) behaviors. Thanks for the post and fixed in next release of Singular, -Bobby53
have a problem with dismounting melee bot. in options set "Melee dismount range"=10 but bot dismounting in range 40 or above. BotBase questing, grinding. What iam doing wrong?
my 97 warlock didnt turned to left or right when questing it was befor i had to use another cc to get it working it was all the way working good from 1-97 but then it start having issue with turning to left and right
acmodey, Thanks for the post and sorry for your confusion. There are way too many components involved each which can alter how the other performs its task. You will want to follow the steps in Reporting Singular Bugs (click here) even in a case where you are just asking a question. Following those steps will provide all the information needed for to research your question/issue and provide an accurate and detailed answer. Most likely what is happening is that the Melee Dismount Range mentioned is a Singular setting and controls when Singular would initiate a dismount. It does not however control other components dismount range or prevent a questing profile from dismounting whenever it chooses. Thanks and good luck with your Singular toon, Bobby53 Hi Mario27, It has been quite awhile since you have posted in the Singular thread and with 5601 posts (and counting) to the HonorBuddy forums you may have forgotten, but you will want to follow the steps given in Reporting Singular Bugs (click here) if you would like a response going forward. The issue is with the Avoid Quest Behavior, not with Singular. Switching to another Combat Routine would have fixed the issue only if it ignores the CapabilityFlags. These flags allow the BotBase and Profile to selectively turn off certain behaviors within the Combat Routine while allowing the rest of its behaviors to be active. This allows for advanced interaction to occur where a component like Avoid can disable combat routine movement and facing, thus allowing it to move the character away from an effect or enemy without fighting the combat routine for control, but still calling the combat routine to allow it to use self-healing and defensive cooldowns while moving. In this case, Avoid disabled Combat Routine Facing and Movement, but never enabled it again which is why you saw the issue. Issue only resolved because another user submitted a detailed account along with a log file as needed. Please review and follow the steps in Reporting Singular Bugs (click here) if you encounter another problem. Thanks and good luck with your Singular toon, -Bobby53 Note to All Members: The rules of this thread are that posts will be deleted without a response if they do not include the details described in Reporting Singular Bugs (click here). If you are a relatively new user I'll respond letting you know that is needed, provide a link, and offer any clarification and assistance needed in providing that detail. If you are a veteran user and your post disappears without a response, that is what happened to it.
no matter what class i use with Singular it seems as it tries to spoon the mob, this affects the pick pocket for rogues as they cannot pick pocket them due to they are being too close. Does not matter what level. the log will not help in this case. it's a range problem when moving towards enemy. Here's a cool picture to show the problem: http://i.imgur.com/e39c2Xm.png i can post more pictures if needed, this is just an example. Also, Singular has a bug with Ressing at Spirit Healer at BG/Ashran/Wintergrasp/Tol Barad and any other places with spirit healer that resses you automaticly within 1 minute.
Are you sure thats singular or are you guessing ? Because thats the most annoying bug i know, ruins my whole profile and forces me to use both addons and plugins for workaround. I'll happily post logs for the both of us to get it fixed. But i was dead sure it was an HB issue and not Singular. @Bobby. Heroic strike is not treated as an off gcd ability for protection. Its waiting to use it in between on-gcd spells. Just woke up, i'll find a log after breakfast <3
Yes i'm sure, i was making a profile for a pvp zoned area and i spent 6 hours trying to figure it out, disabled alot of behaviors and when i disabled singular, Then i found out singular was the problem. it ignores ressing at spirit healer. also talked to many other community developers and they said it was a common issue and it was not HB itself due to Singular overrides the death behavior.
Hello Bobby. Woke up to my poor lil bot being stuck on the same spot for 5+ hours, middle of a instance. Not a single whisper tho lol, not sure if i should be amazed or afraid Check the log somewhere about [08:18:27.844 D] I think it gets stuck after a death around there but no idea. Was sleeping as usual. View attachment 4380 2015-02-22 05.50 - Copy.zip In the same log, im also getting spammed with: Code: [08:18:24.983 N] (Singular) (Singular) Programmer Error - Combat Log Event On Character: filter out COMBAT_LOG_EVENT_UNFILTERED - 0818F400000000000000000006C865A4 Enemy.Paladin.65A4 - Censure 31803 on 0818F400000000000000000003749056 Me [08:18:25.063 N] (Singular) (Singular) GankDetect: received COMBAT_LOG_EVENT_UNFILTERED src=0818F4000000000000000000084A53F9 dst=0818F400000000000000000003749056 Edit. I checked log and it seems to treat heroic strike as an off gcd ability after all. What made me think otherwise is two fold: 1. It doesn't use heroic strike nearly enough and consistently rage caps. (see log entry [04:55:49.381 N] or [04:57:11.404 N] ) 2. If you use heroic strike manually, it will queue all other abilities and cast nothing (where i would expect it to continue normal rotation while I spam heroic strike)
If that was the case, my profile should actually work fine. I have to use this inside my profile to disable the death behavior for it to work. PHP: <DisableBehavior Name="Death"/> If singular already did this, why would I have to disable it myself ?
