Issue with watterlogged state of custom samples
DragonPHD opened this issue ยท 1 comments
Versions:
- Minecraft Forge: 36.1.0
- Geolosys: 5.1.5
- JourneyMap (optional): x
- ImmersiveEngineering (optional): 5.0.0-135
What happens:
Seems to crash on generation of the samples, due to trying to waterlog a block that doesnt have that as a state
What should happen:
Use the block as a sample
Logs (if necessary):
Additional Comments:
I'm using a modded block (inferium ingot block)
However it seems to be cause from trying to waterlog whatever block is used as a sample (read over some closed issues similar to this)
The structure seems to be correct as well, but I can send the whole datapack if necessary
The custom JSON file
mystical_deposit.txt