Fix AbyssalCraft world data capability applying to all objects, not just worlds #244
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Turns out using
AttachCapabilitiesEvent
in a mixin caused the<World>
generic to be stripped, causing the world data capability to be attached to ALL objects from this event (ItemStack, Entity, etc.). This caused the tweak to take up a lot more memory than necessary, especially as the game ran on (oops).Moved the AbyssalCraft events to its own class to be registered by UT.