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
In both GregTech: Modern and in KubeJS, recipes are/can be defined that require items to be placed in specific locations of the Crafting Table - shifting the recipes horizontally or vertically will not produce the same result.
Despite this, EMI centers the recipes before displaying them, misinforming the player.
In both GregTech: Modern and in KubeJS, recipes are/can be defined that require items to be placed in specific locations of the Crafting Table - shifting the recipes horizontally or vertically will not produce the same result.
Despite this, EMI centers the recipes before displaying them, misinforming the player.
Versions:
Minecraft version: 1.20.1
Forge version: 47.3.12
EMI version: 1.1.18
Gregtech: Modern 1.5.4
Architectury 9.2.14
KubeJS 2001.6.5-build.16
Rhino 2001.2.3-build.6
GregTech: Modern
For an example from GregTech: Modern, we have the recipes for unpacking normal dust piles into small and tiny dust piles.
The recipes are defined in lines 245-293 of MaterialRecipeHandler.java:
https://github.com/GregTechCEu/GregTech-Modern/blob/3d6074670e3723c19736909e924b4719c6ffbf6f/src/main/java/com/gregtechceu/gtceu/data/recipe/generated/MaterialRecipeHandler.java#L245
EMI displays the recipe as requiring the normal dust in the very center of the table:
However, there are no such recipes:
Instead, the normal dust should be placed in one of the first two slots of the grid:
KubeJS
For an example from KubeJS, we have a custom recipe that converts some Cobblestone into Diamonds. The recipe is defined in
this server script
EMI displays the recipe as requiring the Cobblestone on the center line:
However, there is no such recipe:
Instead, the cobblestone must be placed in the top-left corner:
Cross-reports
GregTech Modern: GregTechCEu/GregTech-Modern#2513
KubeJS: KubeJS-Mods/KubeJS#930
The text was updated successfully, but these errors were encountered: