Hi, Justin. I found the source of the bug. Using the 'SetEnabled' lifecycle event was the root cause. Apparently, it doesn't trigger when the ability is initialized (which is fine, but could be made clear on the function summary), but it DOES trigger when the component is active in the...