You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug, attach relevant log files, and describe what environment the issue occurs in
This is what the item component is supposed to look like. It's just a Holder<Gene>, where Gene is a data pack registry entry.
If I quit the world and rejoin (or rather, if I join any world/server after quitting one), it looks like this instead.
If I try to spawn this in, I get kicked with this disconnect log. I also can't see any recipes that use that item. Note that this only happens to the items in EMI. Items in the creative menu or inventory work fine, and the recipes still work.
However, if I run /reload or F3+T, it goes back to working fine, looking like the first image. I can spawn it in and see it in recipes again.
I asked a friend of mine to check their in their own dev environment for their mod, and they also had the same issue, they just hadn't noticed due to how obscure the problem is.
The text was updated successfully, but these errors were encountered:
Describe the bug, attach relevant log files, and describe what environment the issue occurs in
This is what the item component is supposed to look like. It's just a
Holder<Gene>
, where Gene is a data pack registry entry.If I quit the world and rejoin (or rather, if I join any world/server after quitting one), it looks like this instead.
If I try to spawn this in, I get kicked with this disconnect log. I also can't see any recipes that use that item. Note that this only happens to the items in EMI. Items in the creative menu or inventory work fine, and the recipes still work.
However, if I run
/reload
orF3+T
, it goes back to working fine, looking like the first image. I can spawn it in and see it in recipes again.I asked a friend of mine to check their in their own dev environment for their mod, and they also had the same issue, they just hadn't noticed due to how obscure the problem is.
The text was updated successfully, but these errors were encountered: