mandriva, Thanks for the post. Please be sure to attach a log file with future posts (see Reporting Bugs in Singular (click here) ). Will add support for Exotic Munitions talent in next release. Thanks for the post and good luck with your Hunter, Bobby53
tecknoe, There is control of certain spells offered in the Class Config dialog where you control general and class specific settings for Singular. However, there is not a place where you control priorities of one spell over another. So to get a revision follow the steps in Reporting Bugs in Singular (click here) and I'll research and advise on why the behavior is functioning as is or resolve for next release. In this case, improved fight assessment logic was introduced and other spell priorities for Shadow updated, but appears the Instance logic (in effect for Dungeons/Raids) was not. I will revise the check for Mind Sear which was being cast when multiple mobs existed but were not clustered. I don't see a specific point where it was cast and only in combat with a single mob. If you encounter that again please follow the steps in the Report Bugs post I referenced for adding a LOGMARK to indicate the point this occurred. Look for a revision to the Mind Sear hole I saw in the next release. Additionally will fix the issue of Devouring Plague and SW: Death not being prioritized in AOE rotation. Thanks for the post and good luck with your Priest, Bobby53
What Class+Spec are you?: Hunter Survivial What 'context' is the bot in? (Instance, BG, Normal): Normal What level are you?: 22 Have you made any modifications to Singular?: nope What time (HH:MM:SS) or LogMark did your issue occur? start of HB What happened (be specific)? see attachment Did you attach a complete debug log? (choose one: YES or YES) YES View attachment 7300 2015-05-27 14.58.txt
Shadow Priest , normal Gundrak, 100 lv, no modifications to Singular. The problem is that my bot doesnt use any AoE skills on mobs , neither Mind Seer, nor any T90 skills. Even if he gathers a pack of 30-40 mobs he starts to kill them 1 by 1 using only Shadow Wordain, while he can easily kill all of them in 1 second by any AoE. Log attached. View attachment 18480 2015-05-28 22.52.txt
Hi, MrPewterSchmidt, The documentation is built into the configuration popup. Its on a panel on the bottom of the configuration window when you click on the configurable. In my experience, the descriptions have always been crystal clear. cheers, chinajade
evengaar, Thanks for the post with log. You will need to add a logmark as described in Reporting Bugs in Singular (click here) if you would like me to research a specific occurrence of this. I looked briefly around: Code: [18:54:19.000 N] (Singular) .... [0] h=100.0%/m=98.7%, moving=False, form=Shadow, orbs=0, SoD=0, divins=0, [B]aoe=5[/B], target=Слад'ран.7205 @ 3.2 yds, th=100.0%, tface=True, tloss=True, sw:p=0, vamptch=0, devplague=0 and at this point vs 5 mobs it appears to be multi-dotting SW: Pain which is by design. I have added logic to next release if a Mind Sear target is available resulting 4+ mobs hit an all are trivial mobs it will cast Mind Sear. If extensive trivial mob farming is desired and that does not address your needs, you may want to look at other available combat routines which are designed specifically for that purpose. Thanks for the post and good luck with your Priest, Bobby53
Singular does not attack the sun mobs on the second boss in temple of the jade serpent. Could you please make it do this or help me out with how to tell the bot to attack them (but not the invonrable, invisible one with the same ID) I am really stuck here PHP: <WoWUnit Name="Sun" Entry="56915" X="845.2639" Y="-2469.184" Z="178.2088" /> <WoWUnit Name="Sun" Entry="56915" X="850.3611" Y="-2474.321" Z="178.1967" /> <WoWUnit Name="Sun" Entry="56915" X="830.0677" Y="-2466.603" Z="179.2412" /> <WoWUnit Name="Sun" Entry="56915" X="836.632" Y="-2467.156" Z="178.1396" /> <WoWUnit Name="Sun" Entry="56915" X="839.6597" Y="-2469.155" Z="182.4971" />
Hey there Bobby, huge fan of your shaman CC all the work you've been putting into Singular. Currently I'm botting a feral druid, just hit level 36 wooo . While it has been leveling i noticed a lot of the time when it starts swimming in water it will try to mount and swim around on the mount...I was hoping you could add some sort of logic for druid that when in water it'll switch to travel/aquatic form. It will make it look more normal and cut down on the time it takes to travel around. Thanks!
Fom20, Thanks for the post. If you encounter an issue (like the one with travel/aquatic) you will want to follow the steps in Reporting Bugs in Singular (click here). Am actually levelling Druid now and saw a related issue so am looking into that, but if you encounter again will probably want to repost with log and details in the event what you encountered is not due to the same issue. There is logic already in Singular to do what you are describing, so there is some unexpected behavior occurring here. Thanks for the post and good luck with your Druid, Bobby53
Please can you update Singular so if used with a botbase called 'HazzNyo' it loads in the same way it does for Enyo. It keeps changing back to questing settings and trying to attack instead of heal?
Hi Bobby, I last posted mentioning that the bot when navigating through water tends to swim while mounted rather than dismounting and going into aquatic form, well i just caught it doing it again.. What Class+Spec are you?: Feral Druid What 'context' is the bot in? (Instance, BG, Normal): Questing in Talador What level are you?: 94 Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? Issue occurred at ~16:46:00 What happened (be specific)? The bot was swimming through a lake mounted instead of dismounting and swimming in aquatic form which would be a lot faster Did you attach a complete debug log? (choose one: YES or YES) YES If i do not have the correct diagnostic settings on to see the problem in the log please let me know so next time i spot an issue i can have the proper details for you =)
Hello, I'd like to make a suggestion/request here, for the unholy dk, in particular but the death grip part should apply to all specs. The bot is first using icy touch, then death grip, then plague strike. What should happen is just death grip->plague strike. With the death grip glyphs, the range increase and refresh after kill, it is much much faster, and icy touch doesnt need to be cast at all because plague strike will apply both diseases. It makes for much faster pulling and more efficient rune usage. Would be great to implement these for next release, thanks in advance =)
hazard, Had responded to this previously but I don't see my reply. The request is a bit vague referring to the same as Enyo or changing back to questing settings. I don't develop or support Enyo so if there are specific results obtained you will want to indicate what those are without referring to Enyo. In other words, I don't use Enyo and have no plans to use HazzNyo so requests for certain behaviors should reference the behavior specifically. Am also not certain what you mean by changing back to questing settings, as there really aren't questing settings in Singular. My assumption is that at least in part you are requesting support Allow Movement = Auto setting in Singular causing movement to be disabled if HazzNyo is the active botbase. That will be in the next release. If any other behavior or side-effects should be looked into, please see the Reporting Bugs in Singular (click here) post for details on submitting an issue/request for changing existing behavior. Thanks for the post and good luck with your efforts, -Bobby53
Fom20, Had replied to this post previously but don't see my reply. Your Druid is not using Aquatic Mode because it has not been enabled in your settings: Code: [14:31:58.292 N] (Singular) UseAquaticForm: False Click the Class Config button, Druid specific tab, and change Use Aquatic Form to True. You should see it used going forward for that character. Thanks for the post and let me know if you encounter any issues, -Bobby53
roneo1, Thanks for taking the time to post. You'll want to refer to Reporting Bugs in Singular (click here). This post describes the details needs for requesting a change to behavior you observed (regardless of whether it is considered a bug, an enhancement, or simply a preference.) Thanks for the post and good luck with your DK, Bobby53
Hi there Bobby! What Class+Spec are you?: Paladin (Ret) What 'context' is the bot in? (Instance, BG, Normal): Questing What level are you?: 95 Have you made any modifications to Singular?: No What time (HH:MM:SS) or LogMark did your issue occur? ([17:45:22.909 N] What happened (be specific)? My paladin was trying to complete the quest [Disrupting the Flow] which involves groups of mobs in the area. He would run to the generators and while doing so would enter combat with multiple mobs (2+) but rather than attacking them it would start running around not facing the mobs, casting judgement whenever it was facing the target which would be for only a split second, unable to use any of its melee abilties. Did you attach a complete debug log? (choose one: YES or YES) YES I should add that everything was running smoothly up until this point. I've had the bot running all morning without issues.
Fom20, Thanks for the detailed log and description. Singular is a Combat Routine. The Combat Routines role in the HonorBuddy architecture is to simply do what its told. If it isn't told to do anything, then it will do nothing. If it's Capabilities are disabled by the BotBase, Profile, etc. then it won't use them. Based on the log it appears the Questing Profile has performed several actions to intentionally limit the Combat Routine from attacking at certain points when completing this quest. The first is while approaching this quest area the Targeting Distance was changed to 1. This means only targets within 1 yd (basically standing on top of your character) would be targeted. This can be seen at: Code: [17:43:21.324 D] TargetingDistance setting of the profile has been changed to 1 ... and remains that value until ... [17:43:29.918 D] TargetingDistance setting of the profile has been changed to 10 ... at which point you have aggroed 4 mobs ... [17:43:30.153 N] (Singular) (Singular) Pull More: in combat with 4 mobs, finishing these before pulling more disabled Movement and Facing (by disabling those capabilities in the Combat Routine) frequently when Questings Avoid logic kicked in as seen in these statements: Code: [17:43:34.514 D] [Avoid] Running from Fiery Trail[B][17:43:34.516 D] Capability state flags changed. Movement: DontCare -> Disallowed.[/B] [B][17:43:34.516 D] Capability state flags changed. Facing: DontCare -> Disallowed.[/B] [17:43:34.611 N] (Singular) .... h=80.8%, m=91.5%, moving=Y, mobs=4, Shadow Council Pyromancer.8480, 68.4%, 2.4 yds, face=Y, loss=Y [17:43:34.625 N] [Singular] *Avenging Wrath on Me @ 80.8% [17:43:35.073 N] [Singular] warning: facing disabled and not facing Shadow Council Pyromancer.8480 @ 0.0 yds [17:43:35.240 D] [Avoid] Done running from Fiery Trail [B][17:43:35.253 D] Capability state flags changed. Movement: Disallowed -> DontCare. Reason: All entries in CR CapabilityManager have been removed.[/B] [B][17:43:35.253 D] Capability state flags changed. Facing: Disallowed -> DontCare. Reason: All entries in CR CapabilityManager have been removed.[/B] [COLOR=#ff0000]... [B]less than 1 second later[/B] ...[/COLOR] [17:43:36.108 D] [Avoid] Running from Fiery Trail [B][17:43:36.109 D] Capability state flags changed. Movement: DontCare -> Disallowed.[/B] [B][17:43:36.109 D] Capability state flags changed. Facing: DontCare -> Disallowed[/B]. [17:43:36.487 N] (Singular) .... h=72.0%, m=94.6%, moving=Y, mobs=4, Shadow Council Pyromancer.8480, 68.4%, 2.7 yds, face=N, loss=Y [17:43:36.847 D] [Avoid] Done running from Fiery Trail [B][17:43:36.858 D] Capability state flags changed. Movement: Disallowed -> DontCare. Reason: All entries in CR CapabilityManager have been removed.[/B] [B][17:43:36.858 D] Capability state flags changed. Facing: Disallowed -> DontCare. Reason: All entries in CR CapabilityManager have been removed.[/B] So what appears to be happening is that the avoidance logic of the profile is being invoked frequently. When the avoidance ends and the character begins to face its target the avoidance logic is invoked again. This is not a Singular issue and I won't be able to help directly. It will require a HonorBuddy Quest Profile Dev to look into how it is attempting to complete [Disrupting the Flow]. I'll forward to the HB Devs as one of them will need to look into the completion of that quest based on the results you achieved. Thanks for taking the time to post and good luck with your Paladin, -Bobby53
