Advanced Botany Board of Fate crash when you get 6+6
DevTimur opened this issue ยท 0 comments
Your GTNH Discord Username
No response
Your Pack Version
not a gtnh
Your Server
SP
Java Version
Java 8
Type of Server
Single Player
Your Actions
Uh, hi!
I noticed you using changed version of Advanced Botany. But did you fix bug with Dice of Fate Board?
I can't see in your code changes about this issue.
This happens mostly because "src/main/java/ab/common/item/relic/ItemWildHuntWhip.java" is basically empty, so you have 5 extra relics from Adv. Botany mod, instead of 6. So when ever you get 12 on dice board, game just crash. It happes once. After that you just get message "dice disapear".
Maybe adress this issuem and add check for 6+6?
Crash Report
You get this wnen ever you get 6+6 on fate dice board
java.lang.ArrayIndexOutOfBoundsException: 11
at ab.common.block.tile.TileBoardFate.spawnRelic(TileBoardFate.java:71)
at ab.common.block.BlockBoardFate.onBlockActivated(BlockBoardFate.java:124)
at net.minecraft.server.management.ItemInWorldManager.activateBlockOrUseItem(ItemInWorldManager.java:376)
at net.minecraft.network.NetHandlerPlayServer.processPlayerBlockPlacement(NetHandlerPlayServer.java:556)
at net.minecraft.network.play.client.C08PacketPlayerBlockPlacement.processPacket(SourceFile:60)
at net.minecraft.network.play.client.C08PacketPlayerBlockPlacement.processPacket(SourceFile:9)
at net.minecraft.network.NetworkManager.processReceivedPackets(NetworkManager.java:212)
at net.minecraft.network.NetworkSystem.networkTick(NetworkSystem.java:165)
at net.minecraft.server.MinecraftServer.updateTimeLightAndEntities(MinecraftServer.java:659)
at net.minecraft.server.MinecraftServer.tick(MinecraftServer.java:547)
at net.minecraft.server.integrated.IntegratedServer.tick(IntegratedServer.java:111)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:427)
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685)
Final Checklist
- 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.