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

Custom Dimension Loading is Now Broken No Matter The Settings

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.16 Pre-release 1
    • None
    • Unconfirmed
    • (Unassigned)

      The error message that occurs every time I try to create/load a world with a custom dimension is:

      ---- Minecraft Crash Report ----
      // This doesn't make any sense!
      
      
      Time: 6/5/20, 6:35 AM
      Description: Exception in server tick loop
      
      
      java.lang.IllegalStateException: Unregistered dimension type: cic@702a2c6e
      	at net.minecraft.server.MinecraftServer.a(SourceFile:407)
      	at java.base/java.util.Optional.orElseThrow(Optional.java:408)
      	at net.minecraft.server.MinecraftServer.a(SourceFile:407)
      	at net.minecraft.server.MinecraftServer.l_(SourceFile:334)
      	at eov.d(SourceFile:69)
      	at net.minecraft.server.MinecraftServer.v(SourceFile:646)
      	at net.minecraft.server.MinecraftServer.a(SourceFile:256)
      	at java.base/java.lang.Thread.run(Thread.java:834)
      

      The files test1.txt and test2.txt were used to test world creation after loading 1.16 pre1. worldgen_settings_export.json is the file I used to create my Redstone Testing world. I had to manually remove the dimension using an nbt editor in order to be able to get back into that world. I also had to remove the extra dimension's nbt for my survival world too.

       

      The survival world had a caves dimension generation which I used to simulate a cave update for the time being.

        1. test1.txt
          2 kB
          Alexis Evelyn
        2. test2.txt
          2 kB
          Alexis Evelyn
        3. worldgen_settings_export.json
          2 kB
          Alexis Evelyn

            Unassigned Unassigned
            alexis.a.evelyn+minecraft Alexis Evelyn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: