Brennan Ravenscroft

`ItemStack` will now invalidate / revive as necessary as the empty cache flag changes. As of now, stacks, entities, and block entities will now properly manage invalidations / revivals. Chunks...

Upon further discussion, it has been deemed not useful for `ItemStack` to invalidate/revive, since there is no meaning to "when" a stack becomes invalid. Instead, stacks will just stop returning...

Forgot to genPatches before that last commit, will fix tomorrow

Fixed up and ran the capabilities test, was able to verify that comparing, copying, stacking, and all functions of dispatcher/provider/attach work as intended. With that, I think this is ready...

The latest changeset re-adds the `CapabilityType` param to `IAttachedCapabilityProvider#getCapability` and allows the same provider object to be attached to multiple capability types. The type passed into `getCapability` will only be...

The latest commit adds a much simpler modder-facing API for attaching capabilities to objects through a builder system. Usage of this system would be like such ```java event.builder(() -> new...

Will do. A lot has been buried in this and the previous PR, as well as in the discord channel. I'll try my best to summarize.

@OrionDevelopment The main post of this PR has been updated to reflect the current state in detail.

Marking this PR as RFC again as the target for the cap changes has been set to 1.20. Hopefully this can serve as a discussion board for what people want...

Given that the condition context is now available from the `AddReloadListenerEvent`, does this issue have any merit (i.e. would this event solve any real issues?)