If you run a Java plugin server you no longer have an excuse to stay on 26.2. PaperMC has moved 26.3 into the stable channel and is already on build 181 after a burst of daily updates. The official page at papermc.io/downloads/paper lists the newest JAR with the note Lazy initialization of formattedDisplayName from just 18 hours ago.
What actually changed in the last few builds
- Build 181: Lazy initialization of formattedDisplayName
- Build 180: Fix player removal from maps
- Build 179: Fix fire immune entities being lightning immune
- Build 178: Add Entity#isInvulnerableTo method
- Build 177: Improve EntityAirChangeEvent calls
- Build 176: Reset client world load status on respawn or cross-dimension teleport
These are not headline features. They are the kind of quiet polish that keeps large public servers from exploding under load or leaking memory. The real news is that the stable tag finally applies to 26.3 after weeks in experimental and the team is not slowing down.
Plugin authors have had months to prepare yet several staples including certain versions of WorldEdit and CoreProtect are still shipping beta builds for 26.3. Geyser support is listed under 26.2 on some trackers as of this week. If your server depends on cross-play or heavy protection plugins you will be the one stress-testing the edge cases.
The 26.3 release post also flags a coming config merge that will finally consolidate Bukkit Spigot and Paper settings into one file. That lands in 26.4 so anyone upgrading now gets to do the migration dance twice if they stay current. Nice.
Bottom line for server owners
Download the JAR, run a test copy of your world, verify every plugin loads without errors, then decide. The stable channel exists because enough people demanded it. Whether it actually feels stable on your specific setup is still up to you to prove in the next 48 hours.
Other
Other
Other
