HBfanboy1980
Active Member
- Joined
- Jan 16, 2012
- Messages
- 1,137
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.
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.
Uploading yet another log where it's just taking a beat without fighting back. Hoping for a fix soon.
Look for this timestamp: [08:50:05.212 N] from that timestamp and until the end of the log, it's just standing still and not fighting back.
@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:I have gotten this issue while using grind/quest bot, and I only get it while using singular. So yeah, it's singular.
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, Bobby53Bobby, 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.![]()
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.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.
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, Bobby53Hi,
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.
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, Bobby53What Class+Spec are you?: Hunter SV
What 'context' is the bot in? (Instance, BG, Normal): Instance
What level are you?: 90
Have you made any modifications to Singular?: No
What time (HH:MM:SS) or LogMark did your issue occur? Everytime
What happened (be specific)?CC just keep casting misdirect all the time if the CDis cooldown,even is not cool down,it will try to cast it,some UI will alert hunter?s misdirection, so the whole screen is metioning im casting misdirection on tank, that is very strange and lower dps.
Did you attach a complete debug log? (choose one: YES or YES)
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, Bobby53Could you make it cancel *****ling Jade Lightning if to close?
@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
Please see the Standard Response to Incomplete Posts [CLICK HERE].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.
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, Bobby53This 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.