Abyssion, I went through tests on two different Shaman and engaged the DB team and we were not able to recreate using the same versions of software indicated by your log file. So after approximately 12 hours additional cumulative testing time of Resto Shaman across 3 accounts in dungeons (one mid-level Shaman and two 90's running heroics) we were not able to encounter the symptoms you described. This does not appear to be a systemic problem that occurs frequently for everyone, but at the same time I am going to keep looking into this as I definitely don't want it happening to anyone regardless of the cause.@bobby53 Thanks for the reply and thanks for giving the info to Dungeonbuddy. However it seems the problem is solved when using TuanHA Shaman. He won't stop walking, for no reason, like he used to do when using Singular
Can there be an option to disable the use of "Flying Serpent Kick" for monks? So I don't go flying off cliffs.
Demo Warlock while Lvling
My Toon try to kill another Player, but this is a non-PVP Server. But still endless try to kill.
Start here: [16:29:50.411 D] Changed POI to: Type: Kill, Name: Lucky
This. Shaohao rep grind has turned into a nightmare for monks![]()
You should try using Glyph of Flying Serpent Kick for now. It will stop the character from going past the mob(s).
Can there be an option to disable the use of "Flying Serpent Kick" for monks? So I don't go flying off cliffs.
There is logic present to prevent flying off cliffs when using FSK so if it is occurring something is interfering with it or it is failing. There is also logic to cast second FSK when near target to cancel. If it is failing, will need your assistance by providing detailed information. Please be sure to follow the steps in Reporting Singular Bugs (click here)This. Shaohao rep grind has turned into a nightmare for monks![]()
Sorry, but there isn't enough info provided for me to look into this for you. Please see Reporting Singular Bugs (click here) for more details. Both of the spells mentioned are in the Mistweaver spell priority. -Bobby53Just wondering if it is possible to implement Healing Sphere and Expel Harm into the mistweaver rotation.
I have recently switched from windwalker and remember them being in that rotation if it's easy to add.
*new* - All Specs - improved Close Distance logic incorporating Roll, Tiger's Lust, and Flying Serpent Kick (glyphed and un-glpyhed)
Sorry, but there isn't enough info provided for me to look into this for you. Please see Reporting Singular Bugs (click here) for more details. Both of the spells mentioned are in the Mistweaver spell priority. -Bobby53
Ormazd, Thanks for the post. Dragon Roar had been such a staple for Fury awhile ago that the other abilities weren't noticed by members (it's been relatively unchanged for all of MoP.) Have added all Tier 4 abilities and Stormbolt. Look for it in the next release, -Bobby53Is there any way to get the Fury Warrior rotation to include Bladestorm? Thanks and here's my logs.
What Class+Spec are you?: Warrior+Fury
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? N/A
What happened (be specific)? Bladestorm is not included in the rotation for Fury Warriors.
Did you attach a complete debug log? (choose one: YES or YES) YES
View attachment 140717
stuartroad, You are absolutely correct! My apologies for the bug. Fixed in next release, -Bobby53singular wont use pullmore on my mage, even if set to always- as i was reading notes it says
WoWSpec.MageArcane:
WoWSpec.MageFire:
WoWSpec.MageFrost:
needSpell = "Death Strike";
i can only assume that it wont work unless mage has spell death strike, which is a dk spell not mage. the mobs are trivial and it is very unlikely that they will ever kill me, is this bugged, am i doing something wrong
@tumbum, Lucky should not have been set as a Kill POI. This was done by another component (plugin, profile, or botbase.) Ultimately if something is set as a KillPOI, it is the combat routines responsibility to do whatever it can to kill it. The proper place to resolve this is in whatever component set the Kill POI but shouldn't have. -Bobby53Demo Warlock while Lvling
My Toon try to kill another Player, but this is a non-PVP Server. But still endless try to kill.
Start here: [16:29:50.411 D] Changed POI to: Type: Kill, Name: Lucky
@Deathsmind, That is a good suggestion, however that option won't have an effect in tumbum's case. That option enables 'ganker' detection logic such that if you are attacked while Solo and [Target World PVP Regardless] is true, it will immediately switch to that player regardless of whatever else is occurring. That won't occur in the situation described by tumbum. I have updated the description for that setting to:I just found this feature as well when searching for something else. At the very bottom under targeting. Its called target world pvp.
Solo Only. True: when attacked by player, ignore everything else and fight back; False: attack based upon Targeting priority list.