Expected Behavior

launch normally

Actual Behavior

crash on loading

Steps to Reproduce

start up mc

Version of Minecraft, Bewitchment, Forge, Patchouli, LLibrary and Baubles used

latest version of all requirements for bewitchment 1.12.2-0.0.17.7

Screenshots encouraged

Logs, in the event of a crash

crash-2019-01-20_20.08.42-client.txt

If this is a question, developer commentary, or a suggestion, ignore this template

This shouldn't be happening. I'm at a loss at this point.

@OreCruncher The issue is back, but I don't see where in the code this should be happening

Are the using the latest DS BETA? If so the crash should not occur. If DS detects and inconsistent metadata on the stack it would log the info.

line 37 of com.bewitchment.common.item.block.ItemGemOre, you're using stack.getMetadata(). You need to check if that is in the enum range before accessing the array, otherwise this crash happens.
Not sure why a metadata of 9 is on the stack, that should never happen given that the subtypes are 0 to 8, but there are other cases where a legit index is outside the range (like the ore dictionary metadata wildcard value, or something spawned by command by a user accidentally).

I have no clue WTF is even happening in the code, regarding this issue. It should be fine, and also, this user isn't even using dynamic surroundings, and yet is running into it anyways.

@Rynlwar If you are on the discord channel, you should be able to access a build that hopefully resolves this.

Seems to have been resolved in dev.

@aidancbrady

Anything you spot that's wrong? I legitimately can't figure out what's wrong. There are 9 ores registered as gems (0 - 8, via metadata)