AOE Status Fixer

Overview

Many pieces of equipment that apply status effects have an internal cooldown of "once per attack", likely to prevent damage rider sources from inflicting debuffs more times than intended. However, this has a pretty serious problem: it makes these items completely incompatible with area-of-effect (AOE) attacks. For example, if you're wearing the Gloves of Belligerent Skies, and you drop a fat Thunderwave on a cluster of three enemies, only one of them will receive any Reverberation stacks.

This mod reworks the internal cooldowns for these items to instead be "once per attack per enemy". This significantly improves the viability of this gear for AOE builds, letting your Tiger Heart Barbarian spread Reverberation onto three enemies in a single cleave, and your Wizard disperse Poison onto an entire battlefield with one array of Magic Missiles.

Methodology

The way this all works is pretty simple. Basically, this mod removes the `OncePerAttack` property from each equipment passive, but instead of applying the desired status effect on each proc, it applies a custom, invisible placeholder status. This placeholder status has an `Ignore` stack type, meaning subsequent applications of the same status are ignored instead of stacking or re-applying.

In the Script Extender, we subscribe to all status applications, listening for any of our placeholder statuses. When a placeholder status is applied, we swap it out with the real status. Since the placeholder status cannot stack on top of itself, this means that we've successfully applied our desired statuses onto each enemy.

To emulate the `OncePerAttack` interaction, though, this placeholder needs to be removed so that the status can proc again on future attacks. To achieve this, we want to wait until all of the effects of the attack have resolved. There isn't a super easy way to do this, so I went for a naive approach: we simply wait for a few ticks of the game loop to pass, then remove the status. In my local testing, 10 ticks (~330 ms) was long enough for any damage and statuses to resolve, but not so long that the placeholder would still be blocking the next attack (I used dual-wielded daggers to time this).

Lastly, some attacks, like upcasted Magic Missile, could have a duration between the first and last damage applications considerably longer than 10 ticks. To work around this, I set up an additional, lightweight subscription for all spell casts. If the latest spell cast is one of these long-running spells, the placeholder will not be removed until 30 ticks (a full second) have passed.

While the tick subscription logic is a bit superficial, the risk of getting that timeout wrong is quite low. In the worst case, a max cast Magic Missile could potentially proc the same status twice, or