**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
"Crit me with your best shot" node is bugged
Magrailothos
Posts: 5,345 ★★★★★
This node (in UC EQ, 1.2) appears to be bugged; in that it doesn't appear to be affected by Ability Accuracy reduction.
Phone - Moto G4-Plus
Android, latest update
I've tried fighting against Ghulk and Red Skull with Sig65 Black Widow (65% AAR or 80% Vs Science) and she doesn't do damage on any of several dozen non-critical hits. She ought to be damaging on 80%, so I don't think this was a statistical fluke!
In case it was, I also used CapIW for his SP1 (-100% AAR when Kinetically charged), and that didn't do damage on non-critical hits either. I did check I was charged!
I don't need tips from the community, btw. Cap did a great job; and Corvus did an even better one. But surely AAR should be able to get around this protection, just like it can with Safeguard?
Also, while you're working on it, could you consider changing the node description? It appears that the fact no Damage over Time effects are effective is intentional; but the actual node description gives no clue to this at all; and DoT is an effective option around Safeguard, by comparison. Perhaps just changing it to "This champion only takes damage when struck by a critical hit."?
Thanks guys. Still loving the game, as always. 👍
Phone - Moto G4-Plus
Android, latest update
I've tried fighting against Ghulk and Red Skull with Sig65 Black Widow (65% AAR or 80% Vs Science) and she doesn't do damage on any of several dozen non-critical hits. She ought to be damaging on 80%, so I don't think this was a statistical fluke!
In case it was, I also used CapIW for his SP1 (-100% AAR when Kinetically charged), and that didn't do damage on non-critical hits either. I did check I was charged!
I don't need tips from the community, btw. Cap did a great job; and Corvus did an even better one. But surely AAR should be able to get around this protection, just like it can with Safeguard?
Also, while you're working on it, could you consider changing the node description? It appears that the fact no Damage over Time effects are effective is intentional; but the actual node description gives no clue to this at all; and DoT is an effective option around Safeguard, by comparison. Perhaps just changing it to "This champion only takes damage when struck by a critical hit."?
Thanks guys. Still loving the game, as always. 👍
0
Comments
To me, it's working as intended. Doesn't me I like it though.
Why wouldn't this protective mechanism be affected by Ability accuracy reduction?
Rage, Safeguard, Protection Shielding... all vulnerable to AAR.
This is an induced ability (one which is generated as a result of a hit) rather than something permanent like "+80% Physical Resistance".
Also, as a rule, if something isn't affected by Ability accuracy reduction, it will say so. Like Ronin switching stance, Darkhawk switching modes, and so on.
Name another inducible ability that isn't affected by AAR without stating explicitly that this is the case?
Some nodes/abilities were made in a way to not be affected by it, in order to create a new playstyle and "force" the player to play around it
Starburst?
Bane
Biohazzard
Spiked Armor
Physical Perfection
Crit me your best shot
I'm pulling these from memory as I use the Trinity a lot while questing. I'm not 100% on thorns and startburst but I am fairly certain they aren't affected as most responses are "bring a heal champ" when people ask. There are many nodes that are effected by AAR but they don't state that they are or aren't. We know they are because we have seen it happen.
Bane and Starburst aren't induced effects; they last the whole fight. Transferring Bane is an inducible effect; but I'm happy to concede this is probably immune to AAR. Good call.
Seeing it happen isn't the same as it being intended to happen, though, is it? Isn't it worth us questioning these things?
From my perspective and understanding of the game, this looks and feels as though it's unintentional, and therefore a bug; so I raised it as one.
Still, the total lack of any comment from the mods over the last couple of days is as good a sign as any that you guys are right, and that this node is "working as intended".
Why are you even reading the 'Bugs' section if you think everything always works the way it's supposed to?
I can understand if the text induces to error, but that's just it
Shall we just let the thread die now, folks?