Versions

• Silent Gear: 4.0.27
• Silent's Gems: 5.1.2
• Silent Lib: 10.5.1
• Forge: NEOFORGE 21.1.200
• Modpack: ATM10 4.5 Extended
• Optifine Installed: No

Expected Behavior

(Description here)

Actual Behavior

(Description here)

Links/Images

• (Link)

Steps to Reproduce the Problem

1.Place netherite chest from sophisticated storage in a world using the mod version 4.0.26.
2.Exit the world and update to 4.0.27, then launch game and load world
3.Simply right click chest and watch the logfile

Post of copy of the log file or a crash report please

I cannot do that because of personal info, perhaps you can enlighten me on how to purge info?
The bug should be simple to see on your own end, i understand everyone wants logs, but for my own sake, does it not occur on your end? Or do you just read the log files

Doing a find and replace in a text editor should work. If you aren't comfortable with that, I can test it myself when I have time.

https://mclo.gs/BsduoG1

Youre welcome. happens anytime, well, any gui comes up for inventory, pressing E, opening a chest, etc

I know for a fact it is the JEI search function you introduced, just not sure what branch of the code is wonked

What leads you to believe that? It looks like the same issue as #828, which I believe to be related to an attempted fix for another issue. The stacktrace points to the same line in PartMaterialIngredient.

it literally activates JEI

as soon as you open the inventory. how can it not be JEI related. you revert it to before the implementation of search function and its gone. its kinda simple

Either way, the issue resides in whatEVER recipe registry system that activates, and if you're correct in that particular phase of the recipe registry building. Still, it resides IN recipe registry, TMK

just trying to help. I know what i know and im stubborn lol

this isnt fixed?

How so? Is the crash identical?

dude yes, I cannot update your mod. that is a big problem in a modpack. I sent you the logfile, as a consumer in the nicest way possible i expected a patch for this. This is no other mod's problem as they are all updated and have been checked.

I cannot update 4.0.26 > 4.0.27, your mod is the only one that triggers the crash. How can it not be yours. When every other mod functions fine as a whole

I have to play on 4.0.26 until it gets fixed, hopefully. otherwise i got to break down the code to figure out where its going wrong. I dont wanna have to do that

Make sure you have updated to 4.0.27.1, which contains the fix I made to close this issue. I just tested the exact steps you outlined and it did not crash for me. If you think my code is still broken, the changes made are in this commit: ea15e91

I did not mean to offend, I just wanted to state what i believed clearly, I dont think your code was wrong. nothing ever is 100% and that is what i live by. Cant expect something to work forever. It appears to have been fixed on my end, So thank you.

Have a blessed day