Issue with watterlogged state of custom samples #276

Open
opened 2021-06-09 01:32:44 +00:00 by import_user_oitsjustjose_95mQ · 1 comment
import_user_oitsjustjose_95mQ commented 2021-06-09 01:32:44 +00:00 (Migrated from git.oitsjustjose.com)

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):

crash log.txt

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

## 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): [crash log.txt](/uploads/3571aa32481fcf4e5a00c89100a3d295/crash.log.txt) ## 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](/uploads/df8500230de4ab9ba56d18fca9e28c28/mystical_deposit.txt)
import_user_oitsjustjose_95mQ commented 2022-02-01 02:38:43 +00:00 (Migrated from git.oitsjustjose.com)

I'm so sorry, this issue is so old because I've been insanely busy. Can you confirm if this still happens in the latest Geolosys for 1.16?

I'm so sorry, this issue is so old because I've been insanely busy. Can you confirm if this still happens in the latest Geolosys for 1.16?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
oitsjustjose/Geolosys#276
No description provided.