You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
all removeEntries calls happen after all addEntries calls, which prevents, for instance, removing a very broad ingredient then re-adding a few special cases, or replacing an item with a modified version of itself, at least not without some worryingly janky alternatives. it also outright prevents the use-case of inserting things into an index in a custom order.
//expected behavior: only one gold ingot entry visible, the filter having removed the original one.//actual behavior: none are presentRecipeViewerEvents.removeEntries("item",event=>{event.remove(Ingredient.of("gold_ingot"))})RecipeViewerEvents.addEntries("item",event=>{event.add(Item.of("gold_ingot"))})
Crash report/logs
No response
The text was updated successfully, but these errors were encountered:
Minecraft Version
1.21
KubeJS Version
2101.7.1-build.181
Rhino Version
2101.2.5-build.54
Architectury Version
13.0.6
Forge/Fabric Version
NeoForge 21.0.167
Describe your issue
all removeEntries calls happen after all addEntries calls, which prevents, for instance, removing a very broad ingredient then re-adding a few special cases, or replacing an item with a modified version of itself, at least not without some worryingly janky alternatives. it also outright prevents the use-case of inserting things into an index in a custom order.
Crash report/logs
No response
The text was updated successfully, but these errors were encountered: