fabric-loader
fabric-loader copied to clipboard
Order in which jar resources are read is inconsistent with unmodified jar
In MC 1.12.2 recipes are registered in the order in which they are read from disk. This causes issues when a Fabric modified client connects to a Vanilla server, 'cause it seems the recipes are read in a different order, leading to the client and server assigning different id's to the recipes.
Here is a link to a repo that can be used to reproduce our observations. Something to add to the previous message, it can be reproduced by a fabric client connecting to a vanilla server or by a vanilla client connecting to a fabric server.
Here both clients are connecting to a fabric server (see the repo), the left is a vanilla client and the right is a fabric client (see repo). The order of the recipes for the vanilla client is different on the server than on the client resulting in the client unable to use the recipebook.