leveling as a mistwaever monk is quite effective as soon as you get *****eling jade lightning, but its not supported.. maybe someone could make a 1 botten CC with *****eling jade lightning
Thanks Chinajade! That's a great catch. I had never even considered that since I always right click the folder and just use svn update. Does anyone know why this could happen even when I try to force an update to HEAD? And thanks Bobby for taking time to analyze this. I will check that I am on the correct questing revision before reporting next time
@23051602: No worries. It can be difficult at times from an external perspective to see which component is doing what. Even being familiar with it I can't do it based upon user descriptions alone, which is why we always need a debug log file. Thanks for providing one with your post! As for the questing profile / quest behaviors casting spells directly rather than invoking the Combat Routine, there are times due to the mechanics of a quest mob or the circumstances surrounding quest completion being atypical that the quest profile author has to do something unexpected or less than optimal (like a Feral casting Wrath) to facilitate completing the quest. In those cases the quest profile author would be the only one that could say why the approach was taken. @chinajade: Thank you for the follow up and confirmation on that one!
yizo, Thanks for the post with complete log file! It appears you are using: Code: [01:05:22.132 D] Singular v3.0.0.2048 v3.0.0.2048 which was 18 releases ago of Singular. That issue was fixed in 3.0.0.2182 which was also a number of releases ago. You will want to update to the latest version of Singular (since that is required for 5.3 support anyway), which can always be found at Post #1 of this thread in this thread. Be sure when extracting from the .ZIP to an existing installation that you overwrite existing files. Thanks for the post and good luck with your Pally, Bobby53
Lautaro, Thanks for the post. If you encounter any issues, please be sure to follow the steps in Reporting Bugs [CLICK HERE]. In general, Disc is being reworked and an update should be released in the next release or two. In the meantime, you should get good results from both Holy and Shadow specs which were previously revised. Thanks for the post and good luck with your Priest, Bobby53
Singular - Archive DO NOT DELETE kennybob, Thanks for the post. I wouldn't classify leveling Solo as a Mistweaver Monk effective, but is supported since it allows use of the Mixed Bot to perform some solo activity while waiting on a dungeon or battleground queue. CJL is already in the Pull spell priority, but I am raising it to the highest (above Provoke) for Mistweaver. Will look to users to provide feedback regarding the change to incorporate into future priority refinements, such as at what point you would want the knockback form CJL. Be sure to follow the steps in Reporting Bugs [CLICK HERE] when posting. Thanks for the post, Bobby53
@Bobby how would you charactarize the Singular behavior for raiding (user assisted). I tried it on my elemental shammy. It seems to have a fair amount of problems compared to pure rotation. For instance it does not seem to correctly detect procs that makes your lava burst a instant cast. Which really kills dps. I always end up last on the dps list with Singular, with about 20-25 k dps. With PureRotation I ususally end up around 55K damage. I would just like your input on the utility of Singular. I am happy to help optimize it and provide logs etc. if it's something that is in the plan otherwise I just use singular for questing.
23051602, Thanks for the post, but not enough details to say what was occurring other than something was wrong with the test conditions. There should not be such a distinctive gap. For example, were you using Tyrael? The current version of that botbase does not call CombatBuffs, so the performance of any combat routine that implements that behavior will be impacted. For Elemental Shaman you will miss out on Ascendance, Elemental Mastery, Shamanistic Rage, Weapon Imbues and Lightning Shield among others, all of which would negatively impact your DPS. Were you testing solo on a training dummy? Then you were most likely using the Normal Context (Solo) behaviors which are optimized for questing/grinding and not the DPS associated with dungeons/raids. There are simply too many variables.Will gladly look at any logs you create. Be sure to set Debug Logging and Debug Spell.CanCast to true in the Class Config settings for initial tests so we can ensure your not encountering some other issue impacting spell priority. Once that is verified you will want to run with all Debug options set to false and the HonorBuddy Log Level set to Normal. Bobby53
I have a question for fury warrior - bot keeps using bursts on mob(not boss) , is there any possibility to add option to disable bursts?
Al3xwh1t3, Thanks for the post! Absolutely. See the Reporting Bugs [CLICK HERE] and post regarding a specific point in time where burst was used and explain why it would be preferable not to. If it is appropriate and of use to other users I'll add it, Bobby53
23051602, It isn't really a case of fair or not. It is simply looking at whether it is configured to perform optimally in the circumstances where you cited its performance lacking. So, in that light I am assuming you are still referring to Elemental Shaman. Simplest thing in terms of botbase selection (since it has the fewest options and you are looking at DPS and not Healing) is to run RaidBot. Configure your session as follows: 1. Settings & Tools --> Set Log Level to Normal 2. Class Config --> General --> Set all Debug options to false 3. Class Config --> General -> set Trinkets and Gloves correctly for your equipped items 4. Class Config --> Class Specific --> Off-Heal Allowed set to false 5. Class Config --> Debugging -> Check the Use Instance Behaviors While Solo 6. Class Config --> Hotkeys -> Set an AoE Hotkey if you need to disable for test Regarding the above: Step #1 & 2 reduce the log output. Singular is extremely verbose in debug mode and this can impose a noticeable degradation of performance. Step #3 ensures your trinkets are used if they need to be cast on cooldown. Step #4 is necessary as Off-Healing is not intended for raids. This won't have much of an impact on a solo training dummy test, but will on 25+ man raids. Step #5 is a temporary setting and is not saved in the settings file. It modifies the behavior loaded for the current session only and is reset once you close HonorBuddy Step #6 is to disable AoE if you doing a purely Single target test. Otherwise Chain Lightnings et al will skew the damage #'s I did a quick test and Elemental Shaman in Singular does have a dependency on a Tank being in group and being near its target before totems are refreshed (since this would indicate an established point for the boss fight --- at least for the immediate future.) Since there is nobody else in your group, that criteria isn't met an totems aren't refreshed. I have made a slight change that will be in the next release. Until then you'll need to refresh Searing Totem manually. Singular does not cast long cooldowns (5+ minutes) automatically as it is assumed the user knows better when to cast based upon the fight strategy. So if you compare to a combat routine that is casting those, you will want to cast manually most likely via a macro that begins with a /stopcasting command so you can interrupt a cast in progress. Singular is aware of totems cast by the user. For example, if you cast Magma, Fire Elemental, Earth Elemental, etc it will not overwrite those. Thanks for the post and let me know how you test works out with your Elemental Shaman, Bobby53
hello, it seems that dk blood dont use death pact when needed. If you can fix it it will be great. thx for the great work
Worked like a charm, I guess that was my bad I was assuming Singular updates came with HB updates bundled. Thanks for the help bobby!
yizo, Thanks for the follow up! When a new release of HonorBuddy is distributed, it bundles the latest version of Singular at that time. There will typically be one or more new releases of Singular prior to the next update to HonorBuddy however. The latest version of HonorBuddy packages Singular 3.0.0.2544, so not quite sure what was occurring for you if you updated HonorBuddy recently (possibly chose NO when asked about overwriting files?) Anyway, glad to know you are up and running. Thanks for the post and good luck with your Paladin, Bobby53
tukumi, Thanks for the post! Please see the Reporting Bugs [CLICK HERE] and post and follow those steps regarding your issue so I have enough detail to research it. Thanks and good luck with your DK, Bobby53
*NEW* Singular 3.0.0.2571 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. 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 This release was spent mostly testing. It includes a number of fixes, with the spec receiving the most attention being Destruction Warlocks. See the Change History (excerpt included in this post, complete history in the .ZIP) 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: [B]--- Release 3.0.0.2571 ---[/B] fixed - will now always update bot detected when bot starts. corrects infrequent but repeatable issue when switching bots fixed - uses a local function for checking cursor for a pending target spell cast while awaiting change to API in HonorBuddy. Should no longer spam message about /cancel spell cast Guild Tabard, etc. on every spell cast change- resized columns on General tab so setting names are less likely to be clipped fixed - infrequent exception occurring when casting spell and checking certain classes for ability to cast while moving [B]Hunter[/B] change- All Specs - will output message indicating status of Growl auto-cast when changing contexts (entering / exiting an instance for example.) fixed - All Specs - modified AoE priorites. added Explosive Trap to Beast Master and Marksman fixed - All Specs - Blink Strike was still found by HonorBuddy SpellManager so at times Singular was attempting to cast. reference within Singular removed [B]Monk[/B] change- Mistweaver - Pull behavior (when solo) now has *****ling Jade Lightning at the highest priority (previously was Provoke) so some ranged damage can be achieved. Continues to use Jab as Chi generator during Combat due to higher DPS (in general.) [B]Shaman[/B] fixed - Restoration - was previously setup for long range Pull behavior ( 35 - 40 yds ) which is out of range of spells. Corrected to medium range Pull ( 25 - 30 yds ). The reference to Pull here is regarding internal logic and has no relation to the Pull Distance setting in HonorBuddy fixed - Elem/Resto - issue with setting/refreshing totems in some circumstances (like solo testing on training dummy with instance behaviors....) [B]Warlock[/B] fixed - Destruction - bug in retrieving the number of stacks of Backdraft fixed - Destruction - added Rain of Fire to single target spell priority *new* - Destruction - implemented two spell priorities (Noxxic and Icy Veins) which can be selected by COnfig Setting 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.
Bobby, thanks for the warlock changes. I was wondering if there's an option, or setting i can alter to have the rogue just run up and auto-attack like most other melee classes? Currently it will attempt to stealth/go behind the target, I'm just wanting to disable this so it gets into fights quicker.
Here is a log of playing a LFR. DPS is absolutely pathetic and casting very sluggish. This is with logging on so that might have some effect. But without logging I couldn't see any difference. First part is using DungeonBuddy later I switch to raid bot without any real difference. Note: On the first part quite a few bugged mobs where there. So can't really look at that. Using latest version of Singular View attachment Raid 8596 2013-05-30 09.10.txt
