< Back to news index

26.3

2 min read426 words
Paper Team

The 26.3 Update

As always, backups are absolutely mandatory. After upgrading your world to 26.3, you cannot downgrade back to a lower version!

We would like to thank everyone that worked on this update:

  • Doc94's avatar
    @Doc94
    Sponsor:
  • jpenilla's avatar
    @jpenilla
    Sponsor:
  • Lulu13022002's avatar
  • lynxplay's avatar
  • NonSwag's avatar
    @NonSwag
    Sponsor:
  • Owen1212055's avatar
    @Owen1212055
    Sponsor:
  • spottedleaf's avatar
    @spottedleaf
    Sponsor:
  • kennytv's avatar

If you’d like to support PaperMC as a whole, you can find more information at https://papermc.io/sponsors.

Upcoming changes for server owners

We are currently in the process of preparing a config merge, so that almost all of the config options currently split across the various Bukkit, Spigot, and Paper files finally go together. Our current plan is for this to land in the next major release, aka 26.4. You can track the current progress and changes here: https://github.com/PaperMC/Paper/issues/14304


Faster CI build times and deployment

Namespace are now sponsoring our CI runners! A lot of waiting time on Minecraft releases and commits in general came down to slow CI, and TeamCity configuration editing was also a fairly slow process whenever we moved or created version branches. With the switch, deployment of builds, API, and dev bundles has become significantly faster, and with our own efforts in parallel, has simplified internal processes around updating to new Minecraft versions.

In the future, we also plan on making produced JAR files more tamper-proof, e.g. by signing them. The pull request workflows will also be made faster later.

Next to the above, we have also decreased the distributed JAR file size by about 10mb!


For developers

A lot of API that was previous marked as experimental, including most of the data component API, have had their experimental annotations removed!

Events for working with cushions

We introduced EntityBreakEvent and EntityBreakByEntityEvent, similar to the existing hanging break events. Next to that, you can use the pre-existing EntityPlaceEvent.

Other changes and additions

Here is a selection of other notable additions since the last major update post:

API

Deprecations

Reminder: Versioning change

We have replaced the old -R0.1-SNAPSHOT suffix with a much more informative versioning scheme. See the 26.1 announcement for more information.


Download Paper