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

Impossible to play SkyWars, BedWars, or bridging in servers

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.16.5
    • Windows 10, Multiplayer servers, Average of 120ms on both versions, spam clicking right click
    • Unconfirmed
    • (Unassigned)

      Well, a LOT of people is really excited for this Combat Update V2, I think that the mechanics that Jeb has been adding are really fun and they add a lot of gameplay and interesting stuff, but there is a HUGE problem, What's the point of changing combat (so it's great again) when a lot of servers won't update to this new combat system, the reason they maybe won't update is simple, the most popular games in Minecraft are Skywars and Bedwars, the community really loves those games.

      But I've been testing BedWars in 1.16.5, and bridging in Combat Snapshot 8c servers, and it's almost impossible to bridge, some blocks just disappear, sometimes a block is placed shortly after right-clicking, causing it to be placed when your hitbox is where the block should be, so you go through it, and it pushes you to a side, causing you to fall into the void.

      This makes most games unplayable, since most popular games require to bridge or to place blocks quickly, this bug will be more frequent when servers update to the new combat system, I'm sure players won't like this, causing servers to stay in old 1.8.9

      No, this is not MY problem, this problem also happens to friends of mine when they bridge in modern versions, but when we bridge in 1.8.9 everything is fine, of course this only happens on servers, I ran some tests using similar conditions.

      I really hope Mojang fixes this problem when the new combat sysem is released, so servers can update to that version.

            Unassigned Unassigned
            ElAdrip Adrian Garcia
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: