As the title says. Apparently, whenever you revoke a resource power type, it loses its "start value", and when it is regranted, it appears to be at 0. This is incredibly disruptive to compatibility with Origins designed for Origins Fabric, and I would love it if parity could be achieved in this regard. Here is a video illustrating the problem: https://streamable.com/9yas8r

The iron golem is given a power which does the following things:

• Makes it black.
• Has a resource in it that starts at 1.
• Deals damage to it once and reduces the resource by 1.
• When the resource hits 0, the power is revoked (I checked with commands, they do not have the power after this).

It works fine on first use.

• On second use, it makes it black, but the resource is 0, not 1, which causes it to not deal damage and not trigger the revoke.
• Adding a callback action that modifies the resource to its supposed start value is a workaround for this issue.

Conclusion:

• The second application skipped the "start value" of the resource (should have been 1 in both occasions, it is instead 0).