JEI Integration problem

[noremac09]

Hello, sorry for not following the issue template, but I believe it's acceptable since you're aware of the problem based on the Wiki: "Currently, you must go into a single player world before joining multiplayer to see these. This will be fixed in a future PixelTweaks update."

When do you plan to fix the integration with JEI so that it doesn't require entering a single-player game? It would be great to address this because loading into single player every time is inconvenient :(

[StrangeOne101]

Hi there,

With 1.20 being the focus for Pixelmon now, and because JEI redid their API in 1.20, I was planning on waiting until it was reimplemented in the 1.20 version of PixelTweaks. Because JEI changed so much, it has to be completely reimplemented anyway, so doing it in 1.16 when it might not even work the same way in 1.20 could be a big waste of time.

For some background, here is the reason it requires going into Single player. When you join a world, JEI registers all of it's recipes based on the recipes in that world. Drops and Pokeloot aren't real recipes (according to the game, since they aren't registered), so PixelTweaks quickly reads all the data from Pixelmon to make them when JEI requests it.

However, the data to create the recipes only exists when you join single player. When you join Multiplayer, Pixelmon doesn't load that data since it is up to the server to decide what drops and Pokeloot are. The server, however, does not communicate this to the client. This means that when JEI asks for the recipes, PixelTweaks can't provide them, because the data for them is not there.

Joining single player first seems to just cache the data or something. Not too sure on this.

Regardless, to fix the issue, I have to either

1. Make PixelTweaks on the server send all the proper JEI recipes for drops and Pokeloot to the client
   1a. However, if PixelTweaks isn't on the server, this won't work. So see 2. as a backup
   1b. Make sure PixelTweaks doesn't send this to clients who don't have PixelTweaks. Sending this to clients who don't have PixelTweaks may disconnect them, after all
2. Since Pixelmon won't load the data in MP, PixelTweaks will have to forcefully load it. This is much more complicated

Hopefully that gives some insight into why it's such a complex issue

[StrangeOne101]

Note, it is possible for me to backport the solution from 1.20 to 1.16 after it is done. But I just can't do it on the 1.16 version first when the 1.16 version of Pixelmon is no longer getting major updates