Closed Jerphf closed 8 months ago
I'm new to how github works and how to submit this kinda stuff, so tell me if anythings wrong
Hey. Just to be sure I understand correctly, are you saying that you can only reproduce this with serverutils installed?
I can't reproduce with a fresh 2.5.1 instance and just server utils 2.0.11 added. Have you manually added/updated any other mods?
Correct, it happens only if I add server utilities. Without it installed it works correctly. The instance was downloaded from the wiki, I haven’t added any other mods.
When I get home from work, I’ll try a different version of server utilities and see if the issue persists. I’ll also do another fresh install of GTNH 2.5.1
That's really odd, it looks like something is causing a CME. To my knowledge SU isn't touching anything that NEI cares about.
Was it all recipes or just a particular one? Did you change anything in SU or NEI config? Did you do anything special before checking the recipe?
All recipes, I haven’t touched any configs and followed the migration/installation guide as close as possible. The only NEI setting I changed was the mode to test in creative.
After reading a post from 2013, I decided to try deleting the NEI save folder. I loaded in my survival world, opened my inventory, and tried searching for a recipe. It loaded a recipe with no textchat error. This was also the case with server utilities loaded.
I'm guessing the file didn't migrate properly, but would work fine until I added server utilities. By deleting the migrated file, the game had to make a fresh one thus solving the issue.
I honestly don't know why this worked, but it did for me.
Your GTNH Discord Username
jerphf
Your Pack Version
2.5.1_java17-21
Your Server
SP
Java Version
Java 17
Type of Server
Single Player
Your Expectation
I tried to check a recipe in NEI and through the questbook.
The Reality
I was instead met with an error saying to check logs, This shows up in the textchat.
Your Proposal
I'm not sure. The error says to check logs, so here's the latest log I have on hand fml-client-latest.log
Final Checklist