Direct answer

In Java Edition 26.4 Snapshot 5 (October 20, 2026), the server explicitly applies login encryption and compression settings using packets that are acknowledged by the client. Older behaviour applied these settings immediately, which could cause malformed packets at the transition. This is snapshot behavior under development, not a final compatibility declaration for stable 26.4.

What changed in the packet flow

  • The server sends either minecraft:login_finished or minecraft:apply_options with connection options.
  • The client acknowledges with the corresponding minecraft:login_acknowledged or minecraft:options_applied packet.
  • The negotiated settings take effect on subsequent packets after acknowledgement. A protocol implementation must preserve the transition boundary.

Which server owners are affected?

Ordinary owners using a supported server JAR may not need to edit configuration manually. Proxy and packet-protocol maintainers have more to test: Velocity, other proxies, version translators, network monitoring and packet interceptors must track the final protocol in their own supported builds. An open commit or experimental build is not confirmation of stable compatibility.

Safe testing checklist

  1. Create an isolated snapshot test server and proxy, never reuse your only production world.
  2. Record client, proxy, backend, ViaVersion/ProtocolLib/PacketEvents and Java versions before testing.
  3. Test online-mode login, first join, reconnect, server switching, login compression and disconnect behaviour in a controlled environment.
  4. Review authoritative project release notes before calling any combination “supported.” Re-test when Mojang publishes a new snapshot or stable release.

Common mistakes

  • Do not infer that a snapshot packet name will be final.
  • Do not “fix” failed login negotiations by turning off authentication.
  • Do not assume Paper, Folia, Forge or a Velocity proxy all ship the protocol change at the same time.

What should production admins do today?

Keep current stable releases, preserve working binaries and monitor the official 26.4 and proxy changelogs. Prepare staging tests, but do not change production settings solely because of a snapshot.

Official references

Official sources for version-sensitive details. Check the newest release notes before changing a production server.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000