Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-241560

Game Crashing when loading certain chunks in pre release

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • 1.18 Pre-release 1
    • None
    • OS: Windows 10
      Graphics card #0 name: NVIDIA GeForce GTX 1650
      Java Version: 16.0.1
    • Unconfirmed
    • (Unassigned)

      I made a copy of my main survival world to see what it will look like in 1.18 and started to fly around the border of explored and unexplored chunks. After loading a specific 1.18 chunk my game crashed every time. I was able to load chunks in other places and was able to load into the -64 y coordinate but this chunk made my game crash every time. 

      The Launcher says: 
      The game crashed whilst feature placement
      Error: java.lang.NullPointerException: Cannot invoke "ddm.a(cao, cps, java.util.Random, gh)" because the return value of "java.util.function.Supplier.get()" is null
      Exit Code: -1
      In the crash report it says "Description: Feature placement" - I'm assuming that means it is trying to load a structure, like a desert temple or mineshaft, but no new structures have been added in 1.18 so that doesn't make sense to me.

      Aditional:

      1. The name of the crash report ends with -server and not -client, why is that?
      2. I've already played 1.18 snapshots with no problems.
      3. After the crash I have loaded this same chunks in another copy of the world and a village generates there without crashing
      4. World seed 3195115
      5. The chunk that crashes the game can be found by going in a straight line from spawn to these coordinates: 352 68 -1335(coordinates of a desert village) after a village just continue about 200 blocks in the same line and the crash happens.

      I hope that's all the info needed to resolve the issue, thanks in advance.

       

            Unassigned Unassigned
            xtxl Simon
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: