sounds like you gotta fiddle with your combat log settings.
I intend to continue bringing attention to it until It’s fixed or there is a published list of intended interactions.
I could use some help with that.
From whom
The people who write the user stories deciding how abilities are intended to function.
right click the combat log tab and hit settings.
the damage of trick shots is likely just going to show up as trick shots. IDK if it will be flagged as ranged, periodic, or whatever.
I know how to do that, but I don’t see a setting to mess with that has anything to do with this. I have everything enabled.
It comes up as the ability that triggered trick shots, so either aimed shot or rapid fire.
Don’t think this really tells much of anything. If anything I really think the reason that blade flurry/trick shots bypass these immunities is because of the way they are coded to accommodate talents that increase their target cap, something I mentioned in the other thread.
Last season played a few games as hero cleave to meme my Dk went frost, the obliterate that hits 2 nearby targets hits the tranquility. So if a pet or teammate is nearby my Dk would hit the pet or teammate and it would kill the Druid during his go.
Interesting, thanks
Means that there isn’t a similarity to blade flurry linking the property it shares with flurry. Guess it’s just random bad code
Can you see if titanic throw can cleave through turtle/tranq?
Absolutely. It’s gonna be later on tonight though.
Looking at the raw spelldata, the other abilities that bypass the tranq/turtle are able to cleave via a talent that is using a dummy effect to alter the number of targets. Not sure if titanic throw will since its a replacement of heroic throw, but it might.
If we can narrow it down to this, I think it pretty well proves out that this is unintended/buggy interaction. Having “abilities with coded dummy variables used by talent modifiers” being the deciding factor of what goes through a deflection/immunity or not would be something I’d have a hard time describing in any other way than bugged.
Can you also post the metadata/code for warbringer like you did for the other abilities in the other thread? And where does a person actually go to find that?
warbringer is a pvp talent so simc doesn’t keep that in their data. Wowhead only shows the effect of warbringer as modifying the effect duration of charge, so theres definitely more to it than that.
Imagine if AOE went through bubble, bops, etc and things that are supposed to be immunities. But people will randomly defend whatever this is instead. It’s like the people that defend enhance one shots.
Honestly it’s more the pivot from “the mid-air chaos bolt only hit me because the turtle shell animation didn’t finish” to “there’s some obscure minor low damage cleaves that can sometimes go through”.
Well, oddly enough chaos bolts cast won’t hit through immunities too even if cast before they go off. It’s poor design. None of them should be hitting through. If you can SHADOWMELD such abilities meaning SHADOWMELD is honestly a better defensive in a lot of cases than Turtle… Tells of how poorly designed everything is in PvP.
if bubble/bop applied a 200% miss rate to the spell instead of making you immune to all damage, they would still get hit through
It is impossible to prove the situation with the animation because you do not have access to the information needed. You can only witness it, and you’ll always be able to assume that more things happened with latency or server handoffs than meet the eye. If the in-flight mechanic was all that ever worked strangely with it, that would be one thing. It’s hard to look at how many other inconsistencies exist and just trust that the in-flight thing works correctly. It feels like it doesn’t sometimes.