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

Powering a beacon disconnects player from server

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • 22w15a
    • 22w14a
    • None
    • Confirmed
    • Beacon, Crash, Dedicated Server
    • Very Important

      When powering a beacon with an ingot, the user is disconnected.

      The Bug:

      Upon powering the beacon, the use is disconnected with an io.netty.handler.codec.EncoderException. This behavior is observed in a server environment, but not in singleplayer. Base blocks, ingot used to power beacon, level of beacon, and effect chosen does not seem to matter. Upon joining, beacon does not gain its chosen effect, and user is refunded their ingot. See the video attached for process, and screenshot for full disconnect message.

      Steps to Reproduce:

      1. Join a Vanilla server in 22w14a
      2. Place a beacon (with at least 3x3 of a refined ore block underneath)
      3. Grab an ore of your choice and open beacon UI
      4. Place ingot of choice in beacon UI slot, select an effect, and push the "check" button

      Observed Result:

      User is disconnected from server with an error. Beacon remains effect-less upon rejoining.

      Expected Result:

      Beacon gains its effect and user does not crash.

      Stack trace

      Error receiving packet 36
      java.lang.IllegalArgumentException: Can't find id for 'null' in map Registry[ResourceKey[minecraft:root / minecraft:mob_effect] (Experimental)]
      	at ql.a(SourceFile:115)
      	at xc.a(SourceFile:25)
      	at qn.a(SourceFile:45)
      	at qn.encode(SourceFile:14)
      	at io.netty.handler.codec.MessageToByteEncoder.write(MessageToByteEncoder.java:107)
      	at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:717)
      	at io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:764)
      	at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:790)
      	at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:758)
      	at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:808)
      	at io.netty.channel.DefaultChannelPipeline.writeAndFlush(DefaultChannelPipeline.java:1025)
      	at io.netty.channel.AbstractChannel.writeAndFlush(AbstractChannel.java:306)
      	at qj.a(SourceFile:214)
      	at qj.b(SourceFile:206)
      	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
      	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
      	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
      	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
      	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
      	at java.base/java.lang.Thread.run(Thread.java:833)

        1. 2022-04-07_01-35.png
          13 kB
          catter1
        2. 2022-04-07 01-13-35.mp4
          452 kB
          catter1
        3. MC-249968.mp4
          3.06 MB
          [Mod] Avoma
        4. MC-249968.png
          292 kB
          [Mod] Avoma

            boq [Mojang] Bartosz Bok
            catter1 catter1
            Votes:
            21 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: