Combat Mechanics: There's No Such Thing as Defensive Ability Accuracy
TL;DR: Offensive and Defensive ability accuracy debuffs do the same thing: they debuff ability accuracy. The difference between them is not what they affect, but *when* they take effect.
Every so often I wander around the Reddit, and every so often I reply to a post. Generally it is a technical question of some kind, and usually I get the answer right. However recently I saw a question about ability accuracy, and without thinking about it much I just parroted my basic understanding of how ability accuracy works. However, in this case I was wrong, not just in the details but also in a fundamental way that caused me to investigate further, and decide to try to settle the matter once and for all. To do that, I first did somet testing and then I decided to present a version of the question to the developers, and two Kabam designers (Kabam Niv and Kabam Broccoli) were willing to explain how this works exactly (and I have permission to source them for this post here).
I should point out that there are a lot of different ideas about how ability accuracy works, and it is possible there are a lot of players who have this completely correct, but their ideas just haven't been widely disseminated. For example, Redditor u/EmmaStore got this basically exactly right in the Reddit thread in question. Her description fits the facts, and it matches the description given to me by Kabam.
So to set the stage, here's the wrong version of ability accuracy that I believed, and I think many players believe some version of. Ability accuracy is the chance for an effect to trigger, Defensive abilities are those that are triggered when you're hit. Offensive abilities are triggered when you attack. Defensive ability accuracy reduction affects defensive abilities, and offensive ability accuracy reduction affects offensive abilities.
The problem with this description is that it doesn't fit all in-game observations. For example, in the thread I mention above, the discussion revolved around Magik's Limbo, specifically the Limbo she triggers when she gains a bar of power. Is that a defensive ability or an offensive ability? Or neither? Turns out, it depends. If you hit her and drive her to a bar of power, defensive ability accuracy reduction (say, from Falcon's Lock On) can prevent Limbo. So that sounds like this is a defensive ability. However, if she is hitting you and gains a bar of power, Lock On won't prevent Limbo. If it is a defensive ability, why doesn't Lock On work here?
One theory is that the game treats power gain from being hit as a defensive act, and thus the trigger of Limbo also a defensive act. But that seems to lead to potentially weird complications. If a defensive ability triggers another ability which triggers another ability, are they all defensive abilities? How far does that go?
As it turns out, according to Kabam Broccoli and Kabam Niv, the game doesn't care what triggered the ability at all. There is no such thing really as an offensive ability and no such thing really as a defensive ability (except colloquially). And thus there's no such thing as offensive ability accuracy or defensive ability accuracy. There's only "ability accuracy" and all abilities have it. Instead, it is the *debuffs only* that are offensive or defensive.
Offensive Ability Accuracy Debuffs only take effect on the first frame of the start of an attack.
Defensive Ability Accuracy Debuffs only take effect on a frame where the affected champion is being hit
[Note: this presumably works for both buffs and debuffs, but I'm going to refer to debuffs in the rest of the post for simplicity]
In other words Limbo is an ability with ability accuracy. When Falcon applies Lock On, he is applying an ability accuracy debuff. Because it is a defensive ability accuracy debuff, it "flickers off and on" depending on whether Magik is being struck at that instant or not. "Frame" in the above description refers to the fact that the game divides time into individual segments which generally also correspond to animation frames. The first frame of an attack is the first segment of time when the attack is triggered. The frames where the target is being hit generally correspond to when the target is visually being struck by a component of the attack. Attacks with multiple hits can have multiple frames that trigger defensive abililty accuracy reduction.
Again, it seems there are players that have either guessed or deduced this behavior, but this isn't obvious from observation. There are multiple ways to explain why ability accuracy works in the way most people have observed. This happens to be the correct one; kudos to anyone who figured this out. I'm posting this mainly because this differed from how I assumed it worked, and this explanation did not seem to be widely held by most players.
This means that offensive and defensive ability accuracy reduction work, in a sense, by coincidence. Since most abilities Kabam wants to work "defensively" are triggered upon being hit, they will trigger at the exact moment of a hit and thus be affected by defensive ability accuracy reduction. However, anything else that triggers at the same time will also be affected by DAAR, even if it is something we don't normally consider to be a defensive ability. In fact, if you hit something at the exact moment they initiate an attack (this requires special circumstances if it is possible at all, like the target is unstoppable say) any ability that they would normally trigger as an offensive ability would be suppressed by any defensive ability accuracy debuff that was present.
So we can now put ability accuracy to bed, in terms of how it works. Some players got there on their own, the rest of us now have an official statement on ability accuracy. There's no such thing as offensive ability accuracy or defensive ability accuracy. There's just ability accuracy. Defensive ability accuracy debuffs do not debuff defensive ability accuracy, there's no such thing. Instead, defensive ability accuracy debuffs reduce *all* ability accuracy at the moment the target is hit. Offensive ability accuracy debuffs reduce *all* ability accuracy at the moment the champion initiates an attack.
This does not, however, end this story. Because offensive and defensive ability accuracy reduction are *timing* based effects, then as I said in a sense they work by coincidence. Things just happen to take place at the right time for the effects to produce the changes we expect and the developers intend. But does everything happen exactly when it is supposed to happen, and can things happen coincidentally when they are not intended to happen in a way that causes issues? Probably yes. When players are observing oddities in the game and they think ability accuracy is not working the way they think it should, there's now a new question to ask: did something happen, or not happen, in the split second it was supposed to happen for ability accuracy modifiers to take effect when they were supposed to?
And I'm curious to know if anyone has seen something in game that contradicts this explanation. As it comes directly from game designers, the description is probably accurate, but the game itself is a complex thing. There could be bugs, there could be weird unexpected interactions, there could be additional implementation details that cause the game to behave differently than the designers expect it to. If anyone has evidence of a situation that doesn't seem to follow this explanation, please let me know.
Thanks to Kabam Broccoli and Kabam Niv for taking time to explain this to me, and in turn allowing me to write up the explanation for everyone else. And thanks to u/EmmaStore for being basically right, and setting me on the right path to discovering how this actually works.