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

Extreme network lag causes portal death

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Invalid
    • None
    • Minecraft 1.7.10
    • None
    • Porting while enduring extreme network lag, (1 signal bar strength)
    • Unconfirmed

      All Hail, Minecraft testers/developers!

      The details are: Win XP, Java 7, MC launcher 1.5.2, MC server 1.7.4 <== (not 1.7.10!)

      Please refer to supporting evidence: http://youtu.be/8Bq1oBFhqbo, (uploading now!)

      Severe MC server lag causes:

      • portal delay, (keeps resetting play to the port moment: can result in death if the player jumps from level 230 in the overworld, say, to level 65, when the player has not completed the teleport as far as the server has been updated. Causes player's belongings to be dropped at the source portal, the destination portal and at all points below the destination portal
      • mining blocks, e.g. sand or nether blocks, movement is reset because the server "believes" an impeding block has not actually been mined.
      • makes navigating doors problematic, (continuous reset)

      Upshot is that Mojang testing methodology is executed with close proximity of servers to client testers and minimal lag.

      In the case of the bug report, the server is located in Tempe, AZ, and I, koan911, am located in Perth, Western Australia, a crow flight of 8,418.77 nautical miles. So we suffer chronic lag problems.

      As a computer engineer, I know it is difficult to deal with – and MC does well – but it could do better!

      Losing Silk Touch was, in any case, the straw that broke the camel's back. At the very least, please hack into my server, Dudes' World, and give me back Silk Touch.

      All Hail, Minecraft engineers!
      We who are about to die, (again), salute you.

            Unassigned Unassigned
            koan911 Keith Knowles
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: