#NML 1.3 freezes upon worldgen

1 messages · Page 1 of 1 (latest)

violet holly
#

No crash report is generated, although this part from the log seems to describe the cause (feature order cycle)

Caused by: java.lang.IllegalStateException: A feature cycle was found.

Cycle:
At step 9
Feature 'minecraft:brown_mushroom_taiga'
  must be before 'minecraft:red_mushroom_taiga' (defined in 'minecraft:taiga' at index 4, 5 and 2 others)
  must be before 'nomansland:patch_field_mushroom_normal' (defined in 'minecraft:taiga' at index 5, 12 and 1 others)
  must be before 'nomansland:patch_roots' (defined in 'minecraft:birch_forest' at index 13, 16 and 26 others)
  must be before 'nomansland:patch_cattail' (defined in 'minecraft:birch_forest' at index 16, 17 and 42 others)
  must be before 'nomansland:patch_reeds' (defined in 'minecraft:birch_forest' at index 17, 18 and 42 others)
  must be before 'nomansland:patch_waterlily_common' (defined in 'minecraft:birch_forest' at index 18, 19 and 42 others)
  must be before 'minecraft:patch_dead_bush' (defined in 'minecraft:mushroom_fields' at index 8, 9)
  must be before 'nomansland:patch_dried_grass_mycelium' (defined in 'minecraft:mushroom_fields' at index 9, 10)
  must be before 'nomansland:patch_duckweed_sparse' (defined in 'minecraft:mushroom_fields' at index 10, 11)
  must be before 'nomansland:patch_hearty_succulent' (defined in 'minecraft:jungle' at index 20, 21)
  must be before 'minecraft:patch_large_fern' (defined in 'minecraft:jungle' at index 21, 22)
  must be before 'minecraft:brown_mushroom_taiga' (defined in 'minecraft:taiga' at index 1, 4 and 1 others)

I've tried removing blueprint, although the issue still persists. Reverting to NML 1.2.3 fixes it

image.png
simple rapids
#

@vagrant bluff feature order cycle error, this shouldn't be possible

#

what's going on?

vagrant bluff
#

I have no clue. Need a full log for further investigation. This looks like a regular old feature order cycle (which shouldn’t happen) but doesn’t have much other information

violet holly
#

There does seem to be a crash report in the log itself, yet a file for it isn't generated for some reason

#

Wait a sec

simple rapids
#

just need full log

violet holly
#

Disabling Noisium also didn't solve it btw

vagrant bluff
#

Thanks, I’ll pore over this later when I have the time.

#

The other mod that immediately makes me think “this might conflict with our mixins” is Sinytra. Maybe try removing it and everything that depends on it and see if that fixes the issue.

#

(I’d like to be compatible with Sinytra since lots of people use it but if that is the cause it’ll give me a good first spot to start debugging at least.)

nimble roost
#

ive had the same issue, it seems to be caused by cyanide of all things

#

took me so long to figure out what was causing it

vagrant bluff
#

Oh, huh. That’d make sense actually. I wouldn’t be surprised if they mixin into the feature sorter too.
I’ll have to see if I can find their code to fix ours and make it not crash. That being said Cyanide is kinda pointless with NML as we get rid of the stuff it tries to help you solve lol

violet holly
violet holly
#

Will check

vagrant bluff
#

OK I took a glance at the code and yeah they replace the exact same function call we do, but rather than remove the error they have it error with a better message. I should be able to set the mixin priority of ours to make it run after Cyanide’s, so hopefully should end up being fixed in the next patch lol

#

(I’ll write a fix when I have time today prolly)

violet holly
#

Ah alr

#

Ty 👍