Sever stuck on: [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created.

The Aternos forums are now deprecated

Learn more about this change here.

For help regarding Aternos, we recommend you to visit our support center.

  • Playing on Forge 1.16.5 v36.2.0. Was on the server this week and everything was fine, decided to go in today and suddenly the server stays stuck at this message while turning on: [Worker-Main-6/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=4202, y=12, z=3167}


    Here's the link to the log: https://mclo.gs/qupRqbH

    Server-side mods are: Ferrite core, falling tree and morpheus

    Attached a pic of the mods on client and sever

  • Playing on Forge 1.16.5 v36.2.0. Was on the server this week and everything was fine, decided to go in today and suddenly the server stays stuck at this message while turning on: [Worker-Main-6/WARN] [net.minecraft.world.gen.WorldGenRegion/]: Tried to access a block entity before it was created. BlockPos{x=4202, y=12, z=3167}


    Here's the link to the log: https://mclo.gs/qupRqbH

    Server-side mods are: Ferrite core, falling tree and morpheus

    Attached a pic of the mods on client and sever

    Have you tried regenerating the world? Regenerating the world will delete your current world so do keep a backup incase anything happens.

  • Tried regenerating, it till gets stuck. Also tried playing the world on single player, the loading screen gets stuck. Is there any way to save the world? A mod that's maybe causing this? Or is there a program which could maybe delete those specific chunks?

  • Tried regenerating, it till gets stuck. Also tried playing the world on single player, the loading screen gets stuck. Is there any way to save the world? A mod that's maybe causing this? Or is there a program which could maybe delete those specific chunks?

    can you share your updated log

  • Maybe your can try removing all the mods one by one to identify which mod was causing the issue.