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

Client always see overworld worldborder, even if its set differently in other dimmensions

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.16.5
    • None
    • Unconfirmed
    • Survival
    • (Unassigned)

      Hello

      So, we have a worldborder set command in vanilla, that should work per-dimmension.
      And it works. Sorta. 
      The problem is, that the server-side border process border normally. Spawns mobs etc. But the client still sees the border, that is set in overworld.

      For example: If you set border value to 8000 in overworld and 10000 in the end, you will still see in the end the border at around -4000, but also, you can see, that behind the border endermans spawns. You can glitch thru border via ender pearl and move freely without taking damage, until you get to -5000.

      We think its something with this code:

         public void sendWorldInfo(ServerPlayerEntity player, ServerWorld world) {
      WorldBorder worldBorder = this.server.getOverworld().getWorldBorder();
      player.networkHandler.sendPacket(new WorldBorderS2CPacket(worldBorder, WorldBorderS2CPacket.Type.INITIALIZE));
      player.networkHandler.sendPacket(new WorldTimeUpdateS2CPacket(world.getTime(), world.getTimeOfDay(), world.getGameRules().getBoolean(GameRules.DO_DAYLIGHT_CYCLE)));
      player.networkHandler.sendPacket(new PlayerSpawnPositionS2CPacket(world.getSpawnPos(), world.getSpawnAngle()));
      if (world.isRaining()) {
         player.networkHandler.sendPacket(new GameStateChangeS2CPacket(GameStateChangeS2CPacket.RAIN_STARTED, 0.0F));
         player.networkHandler.sendPacket(new GameStateChangeS2CPacket(GameStateChangeS2CPacket.RAIN_GRADIENT_CHANGED, world.getRainGradient(1.0F)));
         player.networkHandler.sendPacket(new GameStateChangeS2CPacket(GameStateChangeS2CPacket.THUNDER_GRADIENT_CHANGED, world.getThunderGradient(1.0F)));
      }

   }

      We hope Mojang will take a look at this, as we wanted to limit the overworld in 1.16, so we dont have massive map before 1.17 update.

      Have a nice day

            Unassigned Unassigned
            Salty4Daddy Zdeněk Pala
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: