Revert to old recipe manager mixin now KubeJS doesn't break it #974
No reviewers
Labels
No labels
Area-Assets
Area-Backend
Area-Conduits
Area-Datapacks
Area-Lang
Area-Mod Compat
Area-Parity
Area-Rendering
Good first issue
MC-1.19.2
MC-1.20.1
MC-1.20.4
MC-1.20.6
MC-1.21
MC-1.21.1
Modtoberfest
P-0-High
P-1-Medium
P-2-Low
Status-Awaiting Response
Status-Behind-Flag
Status-Blocked
Status-Cannot Reproduce
Status-Duplicate
Status-Help Wanted
Status-Incomplete Report
Status-Invalid
Status-Needs LTS Backport
Status-Needs Updating
Status-Stale
Status-To Implement
Status-Triage
Status-Wontfix
Status-Wontmerge
Type-Backport
Type-Bug
Type-Documentation
Type-Enhancement
Type-Question
Type-RFC
Type-Suggestion
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Team-EnderIO/EnderIO#974
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/recipe-manager-mixin"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
This build has been tested in Enigmatica 10 (and resolves #972).
I would love some input from @rlnt as to whether this breaks Kube JS scripts for existing modpacks or not, as I'm unsure if this change will have an effect on the order of things, thanks!
Checklist
The old implementation is a much cleaner approach and the preferred way in my opinion. However, since KubeJS uses a head inject into the
RecipeManager#applymethod, it won't be possible to remove inherited recipes via KubeJS anymore. This is an unfortunate side effect, but it's still the best solution. We were aware of that when changing the KubeJS event logic.The only thing this will break in KubeJS scripts is anyone removing inherited recipes by IDs but I'd say this is fine.