Skip to content

Closer to 1.1.0: Are we there yet?
Compare
Choose a tag to compare
@A248 A248 released this 12 Sep 04:03
· 18 commits to master since this release
1.1.0-RC1
4e24341
This commit was signed with the committer’s verified signature.
A248 A248 🇵🇸
GPG key ID: 8834507958FD2A31
Learn about vigilant mode.

Having accomplished a slew of exciting new features, this release prepares the way for the impending LibertyBans 1.1.0. The progress made since 1.0.x, in the form of 1.1.0-M1, 1.1.0-M2, and 1.1.0-M3 now enters the release candidate phase.

I would like to thank everyone who tested the layouts feature while it was in development builds. I don't remember who everyone is, but please feel free to remind me if you don't see yourself inside /libertybans about.

There are no breaking changes in this release compared to 1.1.0-M3. However, if you are upgrading from 1.0.x, please read the relevant guide for compatibility considerations.

Bug-fixes:

  • UUID mismatch on Sponge when player info forwarding is configured (#229))
  • The 'show-applicable-for-history' turned /warns into /history (fb14929)
  • Folia-specific deadlock on tab completion (#224)

New features:

  • Punishment layouts, based on a tiered system of escalation. Also known variously as templates, stacked punishments, escalation tracks, etc. (#180)
  • Kick player via plugin messaging (f7d228d and 235dace)
  • Scoped punishments applicable to a configured server or group of servers (#146)

API improvements:

  • Add method to get back a builder from a draft punishment by @MCMDEV and @KoxSosen (#211)
  • API for alt detection and management (fdf46d9)
  • Allow retrieving player name from PostPunishEvent and PostPardonEvent (#76)
  • Complete API for server scopes (#146)

Other:

  • Create a standalone implementation, currently intended for zxfq's web panel (ed6215b)
  • Faster unmute resolution when synchronizing across instances (19a6494)
  • Add warning to Sponge if newer listener registration API unavailable (19a6494)
  • Initialize the H2 driver if possible; improve driver initialization generally (fb14929)

In 1.1.0, all API additions since 1.0.x will become enshrined in our semantic versioning guarantee, a basic requirement for a stable API not provided by competing punishment plugins. This release candidate (RC) serves the purpose of easing the rollout of 1.1.0 in a gradual, stable fashion. Remember, our Versioning and Support Policy means that anyone, from individual servers to large networks running multiple instances, can enjoy the stability of a LibertyBans release and rest assured that they will receive critical bug-fixes.

Contributors

MCMDEV and KoxSosen
Assets 13