Describe the bug
Eucalyptus sapling crashed the game (I think)
I quickly read through the crash report and noticed that ItemRenderer had trouble rendering an eucalyptus sapling

Crash Logs
crash-2024-01-09_17.23.05-client.txt

How To Reproduce
Steps to reproduce the bug:
I generated a new world and spawned in the eucalyptus forest and I'm assuming there was a dropped eucalyptus sapling that ended up crashing the game

Version
Minecraft Version:
1.20.1
Modloader Version:
Forge 47.2.0
Mod Version:
0.5.3.1
Screenshots
If applicable, add screenshots to help explain your problem.

[update] I think it had something to do with Oculus but I am not sure

yes, it seems like it was an oculus crash.. I tried loading the same world without oculus later and it was fine! just weird that it affected only this specific item
sorry for bothering you!

all good 👍 have a good day

Caused by: org.spongepowered.asm.mixin.throwables.MixinApplyError: Mixin [mixins.oculus.compat.sodium.json:vertex_format.entity.MixinModelVertex] from phase [DEFAULT] in config [mixins.oculus.compat.sodium.json] FAILED during APPLY
at org.spongepowered.asm.mixin.transformer.MixinProcessor.handleMixinError(MixinProcessor.java:636) ~[mixin-0.8.5.jar:0.8.5+Jenkins-b310.git-155314e6e91465dad727e621a569906a410cd6f4] {}
at org.spongepowered.asm.mixin.transformer.MixinProcessor.handleMixinApplyError(MixinProcessor.java:588) ~[mixin-0.8.5.jar:0.8.5+Jenkins-b310.git-155314e6e91465dad727e621a569906a410cd6f4] {}
at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:379) ~[mixin-0.8.5.jar:0.8.5+Jenkins-b310.git-155314e6e91465dad727e621a569906a410cd6f4] {}
... 45 more
Caused by: org.spongepowered.asm.mixin.transformer.throwables.InvalidMixinException: @shadow method mergeNormalAndMult in mixins.oculus.compat.sodium.json:vertex_format.entity.MixinModelVertex was not located in the target class me.jellysquid.mods.sodium.client.render.immediate.model.BakedModelEncoder. Using refmap sodiumCompatibility-oculus-mixins-refmap.json

I believe this is an oculus crash than a Regions Unexplored issue. Could you disable Oculus and verify this is a regions unexplored issue? Thank you very much!