Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-158844

Nether "multiplayer" lag periods

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.19.20.20 Preview
    • None
    • Unconfirmed
    • Android

      Everytime that I go to the nether to do my stuff there, it constantly produces lag that is produced in multi-player, except that I am on a SINGLEPLAYER world.
      (Because of this, I lost my diamond tools and pretty much everything I've worked hard for, and I'm really upset about it) Here is what happens basically:
      The "lag period" happens every 10 seconds to 5 minutes and lasts for up to 40 SECONDS.
      Here is what happens during the period that the lag is present:
      1. No block breaking sounds are played
      1.1 There are no textures visualizing the progress of a block breaking
      2. All entities (besides the player) freeze and make their ambient sounds, but don't move, nor interact with anything.
      3. If you break and/or place blocks during the period, there is 1 chance that it all happens at once, or another chance for everything that you did canceling.
      4. You cannot open chests, furnaces and any other storage blocks until the period is over
      4.1 You can't open your inventory or throw out items until the period is over
      5. There is a chance you'll be able to eat something without actually losing 1 piece of the food (thus technically duping it)
      5.1 There is a VERY rare chance of you duping an item form your inventory (that happened to me once and I don't know why it happens)
      I am really upset about this happening and it has been going on for a while now. I tried everything; Disabling multi-player, reducing lag in video settings, clearing memory. BUT NOTHING WORKED! Mojang, please fix this bug. I've lost all my progress because of it

            MishaG4mer1337 MishaG4mer1337
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: