Rogue doesn't stealth in instance context. Fresh install, latest singular. OT. Any ETA on protection warrior fix ? If you want, i can make a 4th post about the many, many errors and bugs with it Its been broken for months with multiple bug reports that's been archived or ignored.....
WW monk dies alot more than it should because it uses Spinning Crane Kick as the primary AOE attack instead of Fists of Fury, or stands in one spot and tries to outheal 3+ NPC's with the now neutered Surging Mist. FoF does alot of AOE damage in proportion to NPC HP at least when leveling, plus it stuns for 4 seconds. Spinning Crane Kick is outclassed in every way by FoF and theres no use for it if you are the one who has aggro.
I extensively play rogue, and it works just fine for me. Same with druid. However mage does not, and I've no idea about priest. Not sure what's going on here - but it's something Bobby will have to definitely look into.
Here's a reminder of the protection bugs. There's more but I was lazy and just copy pasted my previous post. Line numbers might have changed... If you want log, dig it up from wherever you archived it. If you wanna follow the discussion, go back 3 months and find my PM. 1. * No detection for "sword and board" procs (Resets cooldown of shield slam and grants 25 rage instead of 20.) Both specs needs this and its a huge dps loss. Procs should be used instantly so you don't overwrite it by spamming devastate.) If you get a proc and reproc just before it falls off you can go forever without hitting shieldslam. Which is very much happening due to the devastate bug below. 2. * Excessive use of devastate. The cause is line: 111. Trying to apply a debuff that doesn't exist. (Line 116 is redundant ?) 3. * Using thunderclap on cooldown. The cause is line: 112. Trying to apply a debuff that doesn't exist. Line 373 could be deleted. It has the same effect for both specs 4. * Ravager is not implemented for protection. (Glad can't access the talent) Its 5% single target dps increase. 5. * 'Unyielding strikes' buff / stacks is not considered by protection. Debatable how it should be used but from a dps/middleground POV i would say: spam heroic strike =>3 stacks. (Optionally with rage => 60, for always having a shield block ready. But bit pointless i guess) 6. * Ultimatum is ignored for protection. The cause is line 298. If you have cleave glyph it ignores ultimatum. Not sure why that line is there. 7. * Uses berserker rage on cooldown. Need enrage, same as line 444 // wowhead is wrong. The only spec that lost enrage is arms. 8. * The rage capping issue i mentioned in singular thread could be caused by line 116. No offgcd tag for heroic strike ? Since wait time seems to be much shorter when i post here, i'll do exactly that from now on. Thanks
Is it possible to get a option to disable Cyclone for boomkins? i often find it casting harmful spells on a target with cyclone active.
izzy, If you encounter that please post w/log as it shouldn't be doing that. Steps available at Reporting Bugs in Singular (click here). Thanks for the post and good luck with your Druid, Bobby53
asrah, Thanks for the post. Attempting to heal through melee damage with healing spell that is non-instant is a problem I am aware of since heal amount (sometimes only in combat, others at all times) seen with WoD, but am aware of that opportunity for improvement with Monks specifically so look revision in an upcoming release (not the next one, which is about to post.) The issue mentioned regarding SCK being a higher priority than FoF does not match the results of my testing. It is possible the test for mob count it is facing (must be >= 2 in melee range) is too constrained due a change in a default parameter sometime ago (only looking at those within a 100 degree frontal cone rather than all mobs in front.) Anyway, to look into this for you I need a log file and post as described in Reporting Bugs in Singular (click here) where there is a LOGMARK in the log identifying the point in time where you saw SCK cast and had sufficient Chi and targets for FoF. I would need a specific occurrence of the issue that you observe along with your description of how many mobs appear to be within melee range that the WW is facing. Thanks for the post and good luck with your Windwalker, -Bobby53 Note: I have increased the conal check to 170 degrees so should include just about any mob in front of you in next release. Additionally Tiger Power was not being maintained at a lower priority than SCK so that is corrected as well.
tomten2, Thanks for the log. The attached log doesn't have an occurrence of using Instance Behaviors. Appears to be running Solo in Ashran. I still don't see Stealth cast which was also odd. On investigation there is bug in testing for use of Cloak and Dagger when Pick Pocket has been disabled. Fixed in the next release. Will verify with DB as well for instances. Fixes made in Singular 4.0.0.4603 for Heroic Strke and Ultimatum Procs. Please comment on those specifically and what you are seeing, -Bobby53
There's a facing issue with this mob Constrictor Tentacle - NPC - World of Warcraft from Ulduar. This issue mainly effects ranged dps, i've tested with an arcane mage and elemental shaman and have reports of other classes. Once the npc spawns and picks the player up, Me.InVehicle returns true causing singular not to face the target. This causes singular to just sit there wanting to face the target. Code: [05:44:32.869 N] (Singular) FaceTarget: facing since more than 70 degrees (moving=N) [05:44:32.869 N] (Singular) FaceTarget: waiting (waitForFacing=True) [05:44:32.869 N] (Singular) FaceTarget: don't wait to face Constrictor Tentacle.6FEE since we are in vehicle The log has a log mark of when the issue occurs.
Thanks Just curious, what defines instance ? Being in a group party or raid ? Ashran, while its being farmed "solo", it actually requires queueing up for and is infact an instance world pvp area with set number of people. (De Facto, Battleground.)
Sorry I need to do a rage post - as this drives me currently ABSOLUTELY crazy!!! What the f... is wrong with singular and hunter? Beastmaster - LVL100 - Trying to farm - and it releases every pet I have fighting with me????? Really? I mean... it doesnt matter what setting I do for the pets (1 to 5...) as it doesnt change anything. OMG this is so bad. Made some changes, so for everyone who else got this problem delete new Decorator(ctx => SingularSettings.Instance.DisablePetUsage && Me.GotAlivePet, new Sequence( // new Action( ctx => Logger.Write( "/dismiss Pet")), // Spell.Cast("Dismiss Pet", on => Me.Pet, req => true, cancel => false), // new Action(ctx => Spell.CastPrimative("Dismiss Pet")), // new WaitContinue(TimeSpan.FromMilliseconds(1500), ret => !Me.GotAlivePet, new ActionAlwaysSucceed()) ) ), from the common.cs in the hunter folder. quick and dirty patch to not release the pet - as otherwise this CC is garbage.
What exactly do you mean by "releases"? I'm just asking for clarification because I haven't noticed any issues yet on my BM.
zakanator, Thanks for the post with the succinct and well written post with logfile attached! Fixed in next release. Good luck with your efforts, Bobby53
tomten2, Good question that has not come up in awhile. Singular's behavior selection attempts to base the decision of what behaviors to use (solo, pvp, instance) on what you are trying to do rather than solely on where you are. Instance behaviors attempt to fulfill your role in the group and trust that other group members will fulfill their roles as tank, dps, and healer as expected keeping the group alive. The key there is Role. If you have a group role assigned to your character then Instance behaviors are selected. If you are in a group and inside an instance, it also assumes this was done with a group purpose in mind so uses Instance behaviors. If you are in a World group and do not have a role assigned, then it assumes the group was formed solely to be able to see location of group members on a map, share kills if you are coincidentally near each other, etc. but that you will not depend upon others in the group so will heal yourself, expect to take aggro and avoid abilities that could cause you to lose a mob kill, etc. Singular always indicates on a Context change how it chose the selected behaviors. Here is the entry from the Context change that occurred when your toon entered Ashran: There is more to it, but that is the basics of current context detection logic. As for battlegrounds and arena, those always use the PVP behaviors. In this case, Ashran is indicated as a World PVP zone and not a battleground, so not being in a group resulted in Solo behaviors being used. -Bobby53
Facing mobs is stil an issue it doesend face them straigh away but in a difference way and keep hitting them
Is it normal for Priests, Warlocks and Mages not to buff themselves? Stamina, Int and WL-buff whos name i have forgotten. i don't see any options to turn it on/off =/ or am i just blind? =)
Hi, Elyzol, Singular obviously arranges for toons to buff themselves, and their group members also (as appropriate). If this is not happening for you, you will need to follow the procedure in Post #4 to have the issue investigated. cheers, chinajade
