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

Received invalid biome id: -1 - looped warning message causing game to freeze

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 21w15a
    • None
    • Put your operating system (Windows 7, Windows XP, OSX) and Java version if you know it here
      Well since you asked for it, there it is:
      Windows 10 bug edition.... I mean Pro edition.
      Java 8 update 241 (build 1.8.0_241-b07)
    • Unconfirmed

      Put the summary of the bug you're having here
      OK I will do it .

      What I expected to happen was...:
      Describe what you thought should happen here

      I should have been moving left and backward after respawning, but froze instead and received a looooot of warning messages Sorry

      What actually happened was...:
      Describe what happened here

      Well I will attach some logs [Praise the logs!]

      Steps to Reproduce:
      1. Use the data pack provided in newest snapshot with the 21w15a version
      2. View distance: 12 chunks
      3. difficulty hard - Seed: [-530866723]
      [checked it in game, before crash, entered before friends nicknames]
      4. After spawning - explore that mountains [on the left it looks like some kind of blown up mountain]
      5. On top of mountain change view distance settings to 31 chunks.
      6. Jump and die from fall damage [IN GAME! DON'T DO IT IN REAL LIFE. IF YOU ARE THINKING ABOUT IT THEN CONSULT THE NEAREST PSYCHOLOGIST]
      7. After respawing go left and back simultaneously. After taking like 5 steps got a freeze with:
      Can't keep up! Is the server overloaded? Running 4826ms or 96 ticks behind
      Received invalid biome id: -1
      [looped message spamming in console until you crash the game, or it will get shutdown for not responding]

            Unassigned Unassigned
            _jastrzab_ Radek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: