The crash was occurring due to the recipe registries always adding recipes without ever clearing.
This was causing behavior where recipes would be loaded with serialized itemids that were not valid in the world they were being deserialized in along side the same recipes with the correct ids for the world.
This was especially noticeable if a player had two different worlds with different modsets, loading into the one with a higher max range of itemIds, then loading into the one with a lower max range of itemIds, would cause two sets of all the recipe ingredients in the registry (mainly focusing on those for DoughIngredient), with one set having the former worlds IDs, and the other with the latter worlds IDs. These then get serialized by the server and sent to the client. When trying to deserialize them on the client, it would attempt to get an itemstack of one of those former ids and crash.
(untested) In instances where a crash would not happen this perhaps would also create wrong outputs as an item would be created with the wrong id than expected.
The crash was occurring due to the recipe registries always
addingrecipes without ever clearing.This was causing behavior where recipes would be loaded with
serialized itemidsthat were not valid in the world they were beingdeserializedin along side the same recipes with the correct ids for the world.This was especially noticeable if a player had two different worlds with different modsets, loading into the one with a higher max range of itemIds, then loading into the one with a lower max range of itemIds, would cause two sets of all the recipe ingredients in the registry (mainly focusing on those for DoughIngredient), with one set having the former worlds IDs, and the other with the latter worlds IDs. These then get serialized by the server and sent to the client. When trying to deserialize them on the client, it would attempt to get an itemstack of one of those former ids and crash.
(untested) In instances where a crash would not happen this perhaps would also create wrong outputs as an item would be created with the wrong id than expected.