*new* Singular v3.0.0.3554 available for download! This release contains a lot of changes: - Singular Debug output can be directed to log file only (bypassing HB log window) - Rewrite of Monk Mistweaver Healing support. The default health% in Class Config -> Group Healing may need revision so be sure to review them before using - Several fixes that have been pending to Rogue and Demonology Warlock For full details read the Change History below. A complete Change History is always provided. 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: --- Release 3.0.0.3554 --- General change- Debug Output: the default is to write debug output to the Log File only. This will assist new users that encounter a problem as their log will include the info, but it will not spam the Log Window with that detail. Advanced users encountering no problems should change this to None change- Class Config: new Debug Output dropdown list replaces the previous Debug Enabled checkbox. You can now choose from None, File Only, or Window+File as the destination for debug statements. change- Class Config: the Class Specific tab label will now have the name of the class instead *new* - Use Soulwell behavior: if a soulwell created by a group member is within 25 yds and toon does not have any Healthstones, Singular will move towards the Soulwell and interact. A setting is added to Class Config - General to turn this off (on by default) fixed - Movement: stop at range logic was not checking if target was in line of spell sight. this logic was primarily used by ranged healers change- Spell Cast messages: will use a different color to indicate if spell is a heal fixed - Spell Cast logic: revised some checks and handling for recognition of when spell cast just initiated actually begins. Previously was returning prior to cast commencing which caused problems for some spell priorities *new* - Added Asaad i Vortex Pinnacle to list of bosses we should not move behind due to its quick facing changes fixed - Racial spell not available log spam change- Heal Targets: increased priority/weight of Me as a heal target if in a Healer Role *new* - Healer Movement: will now support use of gap closer ability when following Tank (currently only Roll implemented for Mistweaver.) Druid fixed - Resto - will now target any Tank for spells favoring that role rather than only Leader. This fixes problems where used with a botbase that does not set a Leader Mage fixed - Lowbie - will no longer cast Frost Nova if in range of neutral mobs that are not attacking us Monk fixed - All Specs - added AOE permitted check to use of Spinning Crane Kick and Rushing Jade Wind change- Brewmaster - Zen Meditation now cast if hostile in range is casting and not targeting Monk *new* - Mistweaver - will cast Life Cocoon while stunned if glyphed fixed - All Specs - Grapple Weapon used only on Humanoids and targets within range fixed - Mistweaver - cast in progress logic during behaviors that broke Mistweavers use of Soothing Mist combinations. *new* - Mistweaver - movement logic to close on Heal or DPS target revised to support use of Roll when sufficient distance away *new* - Mistweaver - rewrite of healing logic. Settings for context specific healing (Battlegrounds, Instances, Raids) now available from Class Config. *new* - Mistweaver - rewrite of DPS logic. Will now favor Melee combat until *****ling Jade Lightning learned, where it switches to ranged combat fixed - Mistweaver - conflict between DPS target facing and Soothing Mist auto-facing heal target fixed - Windwalker - distance check used for Roll now factors in hitbox, so will see improved use of Roll against large mobs (so primarily dungeons/raids) Rogue fixed - All Specs - exception occurring if debug logic was enabled fixed - All Specs - Sap target validation logic bug Shaman fixed - Resto - incorrect heal target was being displayed in some debug messages Warlock *new* - All Specs - support for Create Soulwell. Will create during prep phase of Battlegrounds if none exists. Will also cast when in a group and Warlock is out of stones and a group member is nearby. May be disabled via Class Config in the Warlock section fixed - Demonology - Felstorm/Wrathstorm bug preventing cast in some cases. Additional logic to not cast this cooldown if only one mob and it will die soon *new* - Demonology - Felstorm Mob Count setting in Class Config to control # of mobs required (Default=1) fixed - Demonology - bug preveting back to back casts of Soul Fire when two stacks of Molten Core exist fixed - Demonology - was casting two (2) Hand of Gul'dan after Pull due to lag in time from cast to when missle travels and debuff applied. fixed - Demonology - bug causing it to remain in Demon form after Fury drops below the Switch to Caster config amount 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.
[03:54:38.550 N] (Singular) Verified behaviors can be created! [03:54:38.550 N] [Singular] Initialization complete! [03:54:38.569 D] Activity: Initialization complete [03:54:38.569 N] Initialization complete. [03:54:38.570 D] Activity: Honorbuddy Startup Complete [03:54:43.636 D] Activity: Loading Profile... [03:55:00.091 D] Loading profile from C:\Users\xxxxxx\Desktop\chad\buddy-profiles.honorbuddy\1-90 Questing Profile Pack\MoP\[H - Quest] 85-86 The Jade Forest [Kick].xml [03:55:04.931 N] XML Error: Unknown tag "AvoidMobs" (Input: "<AvoidMobs> <Mob Name="Strongarm Gyrocopter" Id="65843" /> </AvoidMobs>") in "SetAvoidMobs"! Valid tags are: Name, Entry - On line 1252 [03:55:04.932 N] XML Error: Unknown tag "AvoidMobs" (Input: "<AvoidMobs> <Mob Name="Jack Arrow" Id="63809" /> <Mob Name="Sha Tendrils" Id="66688" /> <Mob Name="Bamboo Python" Id="59769" /> <Mob Name="Thunder Hold Cannon" Id="66394" /> <Mob Name="Monkey" Id="59560" /> </AvoidMobs>") in "SetAvoidMobs"! Valid tags are: Name, Entry - On line 1307 Not sure if its a profile problem or a singular problem. The profile still runs without problems..just getting this error before I hit the start button. View attachment 2124 2014-07-31 23.54.txt EDIT: Happens as soon as I select the profile.
Frost Death Knight 1. Also worth mentioning, trinkets dont work while leveling. I have them set to use on cooldown in combat, but they never get used. EDIT: A simple restart of HB and they now are being used. 2. One more thing, I have path of frost set to true. It buffs it, but when it goes into combat it cancels it. When combat is over, it re-buffs path of frost. Strange. Tell me what you need from me to help you fix it. Thanks alot, bobby53.
That is a Quest Profile issue. Based on the message the AvoidMobs statement in that profile needs to be updated. -Bobby53
Some changes made awhile ago to make the trinket behavior more efficient has introduced the side-effect of the Trinket settings that are in effect when Singular is first loaded are kept (so you if you change the trinket settings you would need to exit HonorBuddy and restart as you described.) Thanks for passing this along. Fixed in next release, -Bobby53 It isn't easy to anticipate when Path of Frost will be needed and cast only then, as there is not an API to ask the question "Am I almost about to enter onto water?" You can only check if you are already swimming, at which point your character has already been slowed down and doesn't fully benefit from Path of Frost. You could have it detect that the character is swimming then cast Path of Frost and have the character jump to get on top of the water, but that would interfere with aquatic quests. Path of Frost can also interfere with other botbases/profiles, which is why that setting defaults to false. Happy to look at suggestions for alternative behavior for that. -Bobby53
Thanks alot bobby53. Im not worried about the path of frost issue. Just thought it was worth mentioning. I cant think of any way to make it work. Just make it buff, and when the buff falls off after its 10 min duration, re-buff? Instead of de-buffing upon entering combat. Thanks for looking into the trinket issue. Its been an issue ive noticed for a long time! But I think a restart of HB makes it work. But do your fix anyway.
Uh, there isn't a Path of Frost issue and Singular doesn't remove the buff. Check the tooltip for that ability which describes "... being attacked or receiving damage will cancel the effect." I'm assuming whatever you entered combat with hit you back. If it was cancelled by some other means you will need to provide a log file so I can identify what component other than Singular cancelled it (botbase, plugin, quest profile, quest behavior, etc.) If you have any other questions or issues, be sure to follow the steps in Reporting Bugs (click here) so the details regarding your usage are available. -Bobby53
Here is a diagnostic level log. Logmarked when it activated path of frost, then logmarked again when it entered combat and canceled the buff. View attachment 3784 2014-08-01 09.10.txt
User0828, Thanks for the post, but only a partial log file is attached so am not completely sure what I am looking at. Reviewing the entries near the second LogMark there is no indication that another component dropped the buff. Singular does not contain logic to dismiss Path of Frost (and if it did, it would have emitted a message notifying you of the action.) The best explanation is that you are seeing Path of Frost work as Blizzard intended which they described in the tooltip as "Path of Frost ... being attacked or receiving damage will cancel the effect."
Hey! I'm leveling up a windwalker monk at the moment, haven't seen any problems, but got one question tho. It learned from the talents, tier 2, Chi Burst, but haven't seen my pandzor using it in any fight. So wondering, is it implented and if so which "rules" does it follow? I hope you understand what I'm trying to say :]
No, Chi Wave is still the best general choice for WW so not sure why Chi Burst is setup as the default in HB. I'll add support for Chi Burst in next release. -Bobby53
ponemka, No, but that was an unintentional oversight and will be added in the next release. For now your best choice for Level 15 is Celerity as it will use consecutive roll casts if possible. -Bobby53
Hey bobby. Im still having the issue of my hunter not using her glove enchant. I have it set to use on cooldown. I have this enchant on her if it helps. http://www.wowhead.com/spell=126731/synapse-springs Log is attached. View attachment 4824 2014-08-06 16.34.txt
all following issues are when using QuestBot to solo old dungeons and raids: issue 1: Shadow priest does not use mind seer for AOE - when using runLikeHell to gather mobs in questing profile - or after disableBehaviour "combat", gather mobs, and than enableBehaviour "Combat" instead it does standard multi doting which drains its mana very fast for example when using RunLikeHell to gather a lot of mobs in Naxx10 (frostweave cloth farming) after RunLikeHell is complete and combat enabled there is literally 50+ mobs meleing shadow priest, but priest just does multi doting and mana goes in like 30 seconds (plus mobs die slowly) issue 2: also while combat is disabled with "DisableBehaviour" Combat there is no healing (renew/shield) and no speed boost (feathers) but i assume that since CC is not in control you cant do anything here issue 3: feathers sometimes "miss" when shadow priest puts down feather on itself (with normal lag (200ms) and FPS/lock set to 15 it tries to put feather on its own position and passes over it without triggering it, this sometimes happens in manual play, solution seems to be to put feather in position where you will pass in 1 second and not on your current position before you say "attach log" sorry i disable logging for performance reasons but i think you have ore than enough data to reproduce issues for anybody writing their own profiles, or modifying 3rd party profiles themselves this is what i put before enableBehaviour "Combat" to mind sear targets that have low HP (it should help until this bug is fixed): <CustomBehavior File="InteractWith" FactionId="16" NumOfTimes="1000" CollectionDistance="39" MobState="Alive" InteractByCastingSpellId="48045" IgnoreCombat="true" InteractBlacklistTimeInSeconds="1" KeepTargetSelected="true" ProactiveCombatStrategy="NoClear" WaitForNpcs="false" /> only thing that should be changed is FactionId="16" to match your mobs (you can use multiple factions or mobIDs of course) it will mindsear any alive target up to 39 yards away (in range) and when all targets around it are dead proceed to next command in your profile note: you need to enable combat after this AND add wait of at least 1 seconds so that bot loots/skins mobs, another advantage is that it reduces CPU usage a lot compared to standard singular multi doting, but i assume its because of singular "claster finder" PS same issue happens for holy priest but it uses smite and SW another issue that happens to holy is that it does not use DPS chakra when soloing old content, obviously when doing questing or soloing old content there really is no point in using heal chakra since healing needed is minimal and 90% less mana for DPS spells means a lot
bloodmarks, Thanks for the nice write-up! Please attach log files from your use which corresponds to these and I will research for you. That will be critical for issues pertaining to soloing dungeons which is a specific niche and was not part of the original design objective of Singular (I am sure you will find a lot of inconsistancies as you put various Singular specs through that usage context.) The only spec which has gotten much attention in that area is Blood Death Knight due to user posts similar to yours. A good example is the Chakra issue you mentioned with the Holy Priest. As for feather behavior, I have noticed an increase miss rate and my system has much less latency than what you described so don't believe it is due solely to that. Anyway, happy to look into these for you and refine for that use for you. Good luck with your Singular toons, Bobby53
Hi Bobby, as i said because of my specific setup i don't have logging enabled, but especially since you do have priest yourself it should be easy to reproduce (one of issues you already noticed yourself) simple solution for chakra is, if priest is alone/not in party/raid/LFG/LFR group (in dungeon/outside in world/anywhere) use DPS chakra, it should cover questing/dailies/leveling as holy too so does seem like useful thing to have for many people i am not personally in a hurry since i have alternative solution already, so you can take your time fixing this issues, i can understand that this job must be hard when your working alone on such big project so i dont expect realtime bugfixes
bloodmarks, Happy to make the change on the Chakra based on the original info. The Angelic Feather issue is one I saw so no additional info needed on that. The other behavior described will require a log file. The user interface for Debug mode was changed in a recent release of Singular supporting the following Debug Output choices: None, File Only, Window & File. Singular Debug output is no longer directly tied to the HonorBuddy Log Level setting. It also defaults to File Only so unless you explicitly turned it off a diagnostic log is being created, just without all the Log Window spam being displayed. Regardless, choosing File Only does not have as much of a performance impact as Window + File (which was the only mode supported previously.) I recommend giving it a try and adding a logmark at points of behavior you would like me to research (other than the Chakra and AF lag.) Otherwise I won't be able to research any other behavior described. The time consuming portion of issue reports is attempting to duplicate the behavior described, especially when insufficient detail is available. A good description such as yours goes a long way, but doesn't sufficiently describe all the settings and logging of decisions Singular made to allow me to research. So in summary, without a log file the other behaviors described will be at a low enough priority relative to other items they won't be looked at. Thanks for the post and good luck with your Priest, Bobby53 Edit: for Raiding or End Game PVP I would recommend making sure Debug Output = None unless you are encountering a problem and are gathering info for a post.
