I was doing some miscellaneous testing related to using /reload for how my recipe lookup works/is implemented in Mekanism and noticed that JEI does not properly update on a dedicated server from /reload being called. I believe this was introduced by #2227 (cc: @Alwinfy ) due to the slightly incomplete implementation compared to what I described here: #2217 (comment) which from my understanding is what #2227 was based on. The issue has to do with the fact that on connecting to a server for the first time the server sends the packets in this order:

• Recipes
• Tags (vanilla, then custom types)

BUT on /reload it sends the packets in this order:

• Tags (vanilla, then custom types)
• Recipes

The issue with the implementation of #2227 was that while it did address the fact that JEI was doing the updates in the wrong event when connecting to servers, it doesn't have any form of check to validate if the player was already connected and it should be using the other event this time. This causes it to "update" the recipes too early and be stuck with the old outdated copy.

I am not really sure of a good way to implement said fix/change (hence why I am opening it as an issue).

JEI version: 7.6.1.75
Forge version: 36.1.4

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.