Mineforgian
Disconnect Packet Fix
Works around the MC-271325 bug on Fabric and NeoForge servers (fixes "error sending packet clientbound/minecraft:disconnect")
Обновлён 5 июля 2026 г. · опубликован 3 июля 2024 г.
A mod for Fabric and NeoForge-based Minecraft servers that works around the MC-271325 bug. This bug frequently causes the console to be spammed with exception stacktraces, e.g.:
[22:35:52] [Netty Epoll Server IO #5/ERROR]: Error sending packet clientbound/minecraft:disconnect
io.netty.handler.codec.EncoderException: Sending unknown packet 'clientbound/minecraft:disconnect'
at MC/net.minecraft.network.handler.PacketCodecDispatcher.encode(PacketCodecDispatcher.java:47) ~[server-intermediary.jar:?]
at MC/net.minecraft.network.handler.PacketCodecDispatcher.encode(PacketCodecDispatcher.java:14) ~[server-intermediary.jar:?]
at MC/net.minecraft.network.handler.EncoderHandler.encode(EncoderHandler.java:26) ~[server-intermediary.jar:?]
at MC/net.minecraft.network.handler.EncoderHandler.encode(EncoderHandler.java:12) ~[server-intermediary.jar:?]
at io.netty.handler.codec.MessageToByteEncoder.write(MessageToByteEncoder.java:107) ~[netty-codec-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:881) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:863) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:968) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:856) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.ChannelOutboundHandlerAdapter.write(ChannelOutboundHandlerAdapter.java:113) ~[netty-transport-4.1.97.Final.jar:?]
at MC/net.minecraft.network.ClientConnection$2.write(ClientConnection.java:530) ~[server-intermediary.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:881) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:940) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:966) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:934) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:984) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.DefaultChannelPipeline.writeAndFlush(DefaultChannelPipeline.java:1025) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannel.writeAndFlush(AbstractChannel.java:306) ~[netty-transport-4.1.97.Final.jar:?]
at MC/net.minecraft.network.ClientConnection.sendInternal(ClientConnection.java:350) ~[server-intermediary.jar:?]
at MC/net.minecraft.network.ClientConnection.sendImmediately(ClientConnection.java:343) ~[server-intermediary.jar:?]
at MC/net.minecraft.network.ClientConnection.send(ClientConnection.java:325) ~[server-intermediary.jar:?]
at MC/net.minecraft.network.ClientConnection.send(ClientConnection.java:319) ~[server-intermediary.jar:?]
at MC/net.minecraft.network.ClientConnection.exceptionCaught(ClientConnection.java:170) ~[server-intermediary.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:346) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:325) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.fireExceptionCaught(AbstractChannelHandlerContext.java:317) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.DefaultChannelPipeline$HeadContext.exceptionCaught(DefaultChannelPipeline.java:1377) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:346) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:325) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.DefaultChannelPipeline.fireExceptionCaught(DefaultChannelPipeline.java:907) ~[netty-transport-4.1.97.Final.jar:?]
at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.handleReadException(AbstractEpollStreamChannel.java:728) ~[netty-transport-classes-epoll-4.1.97.Final.jar:?]
at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:826) ~[netty-transport-classes-epoll-4.1.97.Final.jar:?]
at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:509) ~[netty-transport-classes-epoll-4.1.97.Final.jar:?]
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:407) ~[netty-transport-classes-epoll-4.1.97.Final.jar:?]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.97.Final.jar:?]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.97.Final.jar:?]
at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
This mod serves to fix that until Mojang fixes this bug. The mod itself is extremely minimal, only using a single mixin to inject code to one method.
Версии
| Версия | Канал | Игра | Загрузчики | Дата | Скачать |
|---|---|---|---|---|---|
| 2.2.0-fabric | Релиз | 26.2 | fabric | 5 июля 2026 г. | .jar (7 КБ) |
| 2.2.0-neoforge | Релиз | 26.2 | neoforge | 5 июля 2026 г. | .jar (6 КБ) |
| 2.1.1-neoforge | Релиз | 26.1, 26.1.1, 26.1.2 | neoforge | 31 мая 2026 г. | .jar (6 КБ) |
| 2.1.0-fabric | Релиз | 26.1, 26.1.1, 26.1.2 | fabric | 30 марта 2026 г. | .jar (7 КБ) |
| 2.1.0-neoforge | Релиз | 26.1 | neoforge | 30 марта 2026 г. | .jar (6 КБ) |
| 2.0.1-neoforge | Релиз | 1.21.8, 1.21.9, 1.21.10, 1.21.11 | neoforge | 25 ноября 2024 г. | .jar (8 КБ) |
| 2.0.0-neoforge | Релиз | 1.21, 1.21.1, 1.21.2, 1.21.3 | neoforge | 23 ноября 2024 г. | .jar (8 КБ) |
| 2.0.0-fabric | Релиз | 1.21.8, 1.21.9, 1.21.10, 1.21.11 | fabric | 23 ноября 2024 г. | .jar (8 КБ) |
| 1.0.0 | Релиз | 1.21 | fabric | 3 июля 2024 г. | .jar (10 КБ) |
Ченджлог
2.2.0-fabricРелиз26.2 · 5 июля 2026 г.
This update adds compatibility with Minecraft 26.2!
2.2.0-neoforgeРелиз26.2 · 5 июля 2026 г.
This update adds compatibility with Minecraft 26.2!
2.1.1-neoforgeРелиз26.1, 26.1.1, 26.1.2 · 31 мая 2026 г.
This release only bumps the allowed Minecraft versions for the NeoForge release, so that you can use it with Minecraft 26.1.1 and up.
An update is only needed on NeoForge! The 2.1.0 release of Disconnect Packet Fix will still work with Minecraft 26.1.1 and up on Fabric.
2.1.0-fabricРелиз26.1, 26.1.1, 26.1.2 · 30 марта 2026 г.
This release will only work for Minecraft 26.1 and higher!
2.1.0-neoforgeРелиз26.1 · 30 марта 2026 г.
This release will only work for Minecraft 26.1 and higher!
2.0.1-neoforgeРелиз1.21.9, 1.21.10, 1.21.11 · 25 ноября 2024 г.
This is a hot-fix release - in 2.0.0, NeoForge refused to load the mod because its ID contained disallowed characters (dashes) - woops!
The only change between 2.0.0 and 2.0.1 is the change of the NeoForge mod ID from disconnect-packet-fix to disconnect_packet_fix.
2.0.0-neoforgeРелиз1.21.1, 1.21.2, 1.21.3 · 23 ноября 2024 г.
This release makes changes to the codebase that allows to build the mod for multiple different modloaders via Architectury - starting with Fabric and NeoForge!
There are no additional dependencies that are needed for the mod to function.
Functionality is largely unchanged. This update only concerns multi-modloader support.
NOTE: This version will fail to load. 2.0.1 fixes this issue. Sorry!
2.0.0-fabricРелиз1.21.9, 1.21.10, 1.21.11 · 23 ноября 2024 г.
This release makes changes to the codebase that allows to build the mod for multiple different modloaders via Architectury - starting with Fabric and NeoForge!
There are no additional dependencies that are needed for the mod to function.
Functionality is largely unchanged. This update only concerns multi-modloader support.
NOTE: Fabric does not have an official 2.0.1 build, as the changes between 2.0.0 and 2.0.1 only concern NeoForge.
Полная история изменений — на Modrinth.
Комментарии
Загружаем…