Warlocks constantly resummoning pets... after dismounting and such. Like when it doesnt need to.. the pet is already summoned has just despawned and will return quickly.
Logfile or Bobby won't have the necessary details, if possible enable debug settings for Singular first
Bobby, where do you see priests (holy / disc) at right now for dungeons (90)? I'd be happy to help with what I can, but I didn't know how far a long you where in the rotation, abilities, etc. Seems to be a class that gets left out a lot... so I'd like fix that.
Any of these attachments will show when he is re-summoning pets when he shouldn't be. I've actually been called out on it twice now lol. I'm actually thinking about not using Kil'jaeden's Cunning so that I can cancel it with a movement... please have a look. View attachment 7980 2013-03-24 01.42.zip View attachment 2796 2013-03-21 08.35.zip View attachment 3000 2013-03-21 21.25.zip View attachment 3124 2013-03-23 17.00.zip View attachment 3136 2013-03-21 09.06.zip View attachment 3536 2013-03-23 00.39.zip View attachment 3960 2013-03-23 01.52.zip View attachment 4144 2013-03-23 12.17.zip View attachment 4192 2013-03-24 20.05.zip View attachment 4564 2013-03-23 20.18.zip View attachment 5820 2013-03-21 22.15.zip View attachment 6084 2013-03-23 03.00.zip View attachment 6316 2013-03-23 01.52.zip View attachment 6388 2013-03-23 18.58.zip View attachment 708 2013-03-24 19.49.zip
@Inrego: Thank you very much for your persistance in providing data relative to this issue. You are experiencing the same issue as in prior logs you have shared, which is Singular recognizing and responding to a SPELL_MISSED event with a Miss Type of EVADE by blacklisting the mob. Per recommendation, Singular was modified slightly to not target or attack Blacklisted mobs. However, Questing bot -OR- the Quest Behavior in use at that point do not ignore blacklisted mobs that you are already in combat with. What should happened is that status is detected and you continue moving towards the next objective ignoring any damage taken, the same as at points where it is mounted and moving to some POI (points of interest.) Since I cannot modify Questing bot's behavior through any of the API's provided, I will provide a setting that you can use to modify Singular's behavior in the next release. The setting will allow you to choose what Singular does in response to an Evade occurrence: - React to Evade - Ignore Evade React to Evade will be the default and represents the current behavior where Singular will response to an Evade event by blacklisting the mob, attempting to target ANY non-blacklisted mob in the area, and expect the Bot to recognize the mob generated an Evade message and ignore it. Ignore Evade will do just that and cause Singular to continue fighting the same as Combat Routines that do not contain any Evade bugged mob logic. In other words, it you are able to sustain your mana and health levels and nothing else interrupts combat with the mob, you will continue fighting a mob that while it remains Evade bugged will be impossible to kill. Thanks for the post and good luck with your Druid, Bobby53 @Tanner: Please see the Standard Response to Incomplete Posts [CLICK HERE]. Appreciate you taking the time to post, but need the detail as I explain on that post for your efforts to usable in pursuing any issue. "^ Me too ..." type messages don't escalate the priority of an issue as there is no way to know without a log file and detailed account whether you encountered the same exact problem or just one with similar issues. -Bobby53
Obliv, Resto Shaman was just the first healing spec done as I begin rewriting support for each. Healing Priest (Holy/Disc) is next in line and was begun last week just before I had to leave for a few days. I cannot commit to a specific time it will be released other than it is the next healing spec to get attention and will support config settings for each spec for each of the healing contexts (Battlegrounds, Instances, Raids.) Thanks for the post and good luck with your Priest, Bobby53
Hi, on some bosses in 5.1 instances my DK knock stacks on some bosses automatically. In new instance in 5.2 not... where I can find list of bosses spells that may knock and new spells there. Thx.
HBfanboy1980, Thanks for the post. The first two log files provided (7980 2013-03-24 01.42.zip and 2796 2013-03-21 08.35.zip) are for a Priest using a different Combat Routine. I stopped reviewing upon hitting ( 3000 2013-03-21 21.25.zip ) which appears to represent your issue. Unfortunately there doesn't appear to be any information in the log file for me to independently identify an occurrence of what you described as at no point is there an indication you were mounted. I was able to review every occurrence where an attempt to summon a pet was made, it correctly waited over a second for the Pet to appear to confirm it did not already exist before performing the summon. So based upon the description it seems in your case the Pet was unusually slow in appearing. Are all occurrences of the behavior you described occurring while running with a manual assist Bot like LazyRaider or are you seeing it with other Bots? Note: if you have further issues or additional detail of this occurring with an automated movement Bot (BGBuddy, Questing, Grinding, etc.) please post a single log file and describe the single occurrence you are reporting so analysis can focus on that specific moment. For details, see the Reporting Bugs [CLICK HERE] post that walks you through making an issue post. Thanks for the post and good luck with your Warlock, Bobby53
Rozman, Please see the Reporting Bugs [CLICK HERE] post for steps on posting a bug or question regarding behavior you observe. Most likely you are referring to behavior handled by DungeonBuddy, which is responsible for all the encounter specific behavior associated with dungeons, etc. It may simply be that dungeon scripts for the new 5.2 instances are not available yet, but for that information check in the DungeonBuddy Support Thread [CLICK HERE] which you can find in the Plugins / Featured & Botbases subforum. Thanks for the post, Bobby53
csl5707, Thanks for the post and complete log file! Not exactly sure what was occurring. In reviewing your logfile and the code it appears that for whatever reason it appears that HonorBuddy was returning false when asked if the Misdirection aura was present. I will need to do some additional testing. If I cannot duplicate this issue, I'll add additional debug logic to capture more info about your issue in the next release. Thanks for the post and good luck with your Hunter, Bobby53
dakota391, Thanks for the post. Please see the Reporting Bugs [CLICK HERE] post for the details needed on any bug report or change request regarding behavior you observe. Thanks for the post and good luck with your Monk, Bobby53
Hey Bobby. Thanks for your response. May I suggest that you keep a counter of "evades" and then blacklist the mob after x number of evades (for example 3 or 5)?
You can switch to my druid does not use the prowl? and pull with faery faire? im using for leveling..grind bot.. and spends too much time to reach the mobs, because prowl.
[Death Knight] DW Frost Rotation Requires Adjustment This is just a suggested change to the current Singular DW Frost DK rotation: Currently, Unholy Runes are not being used up in order to keep one Unholy Rune on cooldown so Blood Tap can turn it into a Death Rune for an additional Howling Blast or Soul Reaper application. This should be done so by using Death and Decay > Obliterate. Also, Frost Strikes with Killing Machine procs are being skipped by one or more GCD's although there is sufficient Runic Power available causing potential overlapping of Killing Machine procs. An option to use Synapse Springs should be added. I did a 5 minute run on the test dummy using Singular 2076 and ended up with 83-85k consistently. Another 5 minute run on the test dummy manually using the changes above showed 88-90k consistently.
daemon9, Thanks for taking the time to post! Appreciate the detailed insight and will look at that for the next release as well as incorporation of glove enchant for all specs. Thanks again for the feedback w/ log and good luck with your Death Knight, Bobby53 Note: if you have any other benchmark results in future, please set Debug Logging to true prior to generating log files. This will impact the DPS some, but the impact will be uniform in your before and after comparisons and will provide important info regarding the state or runes, runic power, etc. as well as decisions made in some circumstances by Singular. Thanks again for taking the time to post your results
Hi Bobby, I would like to take this opportunity to tell you that your work on singular is very much appreciated and thank you. I play a combat rogue as my main and there are very few good working routines out there that are currently maintained. That being said when I tried singular the other day and it turned out to be pretty solid I was pleasantly surprised. If I could ask for one change it would be the way the cc handles the aoe logic for the combat spec. I would like it to activate blade flurry for 2 or more targets while maintaining the single-target rotation without rupture as blade flurry won't copy it to the second target (5 combo point eviscerates at this time > 5 combo point ruptures). If there are 7 or more targets, activate fan of knives as a combo point generator and at 5 combo points use crimson tempest as your finishing move (the cc at this time seems to be activating fan of knives at less than 4 targets and this is bad for combat rogues). Thanks for your consideration and efforts and please keep up the good work
