GT-New-Horizons-Modpack icon indicating copy to clipboard operation
GT-New-Horizons-Modpack copied to clipboard

Blood magic crashes game when I pick up my orb

Open jurrejelle opened this issue 9 months ago • 2 comments

Your GTNH Discord Username

jurrejelle

Your Pack Version

2.6.0

Your Server

Private server

Java Version

Java 21

Type of Server

Vanilla Forge

Your Actions

I tried to get my orb out of a chest. The orb has glitched before and said it was "unnamed", but I thought it was just a visual bug. But the error (java.lang.ArrayIndexOutOfBoundsException: Index 0 out of bounds for length 0 at WayofTime.alchemicalWizardry.api.soulNetwork.SoulNetworkHandler.getCurrentMaxOrb(SoulNetworkHandler.java:42)) implies I have 0 orbs in my network

Crash Report

crash-2024-05-06_11.25.36-client.txt

Final Checklist

  • [X] I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the crash still exists will prompt us to investigate and reopen it once we confirm your report.
  • [ ] I can reproduce this crash consistently by following the exact steps I described above.
  • [ ] I have asked other people and they confirm they also crash by following the exact steps I described above.

jurrejelle avatar May 06 '24 09:05 jurrejelle

jurrejelle.txt this is my playerdata file (should be .dat, I renamed it to .txt so github would allow it)

the orb in question is a Transparent Orb I think it might have something to do with this? 4a01b4fbb198129a61a47b412716e1f5

I deleted this item from my inventory and it seemed to fix it. Still, I'm not 100% sure what "corrupted" the orb

When I delete the item, my game will launch, and I can even check my LP with my divination sigil (even though I don't have an orb anymore), but cheating in a transparent orb and right-clicking crashes again. Cheating in a transcendant blood orb doesn't crash and links to me perfectly, so it seems to be an issue with the transparent blood orb specifically

jurrejelle avatar May 06 '24 09:05 jurrejelle

It's running out of bounds on MinecraftServer.getServer().worldServers[0] Which could indicate that it's running that client-side while connected to a server, adding a simple if(!world.isRemote) return check to the transparent orbs onUpdate method may fix it.

Lyfts avatar May 06 '24 10:05 Lyfts