The be-all, end-all of discipline.
This Leap Day release brings additional stabilization to the 1.1.0 series. Mostly, this consists of solving a few edge cases, making LibertyBans more correct, more accurate, and closer to perfection. We also have a few new features and improvements.
There are no breaking changes in this release compared to 1.1.0-RC1. However, if you are upgrading from 1.0.x, please read the relevant guide for compatibility considerations.
Bug-fixes:
New features:
Improvements:
Other:
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:
New features:
API improvements:
PostPunishEvent
and PostPardonEvent
(#76)Other:
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.
With this release comes compatibility improvements and bug-fixes for the most recent Minecraft versions. LibertyBans is now guaranteed to work on 1.20 and 1.20.1 despite changes to server libraries and Paper APIs.
It is again possible to run LibertyBans on the older MariaDB versions 10.3, 10.4, and 10.5. Many users shared hosts' do not yet provide newer MariaDB versions. However, we nonetheless strongly encourage users to pressure hosts to update their database servers. Operating a more recent database will make your server run smoother and be more responsive to gameplay. It will also enable plugin developers to write code more effectively -- and better code means fewer bugs, sleeker design, and high-quality features.
There are no breaking changes in this release compared to 1.1.0-M2. However, if you are upgrading from 1.0.x, please read the relevant guide for compatibility considerations.
Bug-fixes:
New features:
API improvements:
Other:
Attentive users will observe that I (A248) have returned from a personal hiatus due to travel purposes. However, I am very grateful to Simon, LibertyBans' co-maintainer, for providing hot-fixes and development builds when newer Spigot and Paper versions broke LibertyBans. Thanks to Simon, and also @potatoru for contributing a PR, the bugs were quashed within a couple weeks, at least in development builds. All praise and well-being due to whichever deity you worship, we have now reached a stable release wherein the compatibility bugs are eradicated for good. Therefore I am happy, and relieved, to present this release to you.
With this release, LibertyBans reaches the 400th commit and the 100th star, milestones of development and beacons of progress. Since the last release, a slew of features have arrived to LibertyBans, enabled by our magnificent addon system. In recent months a competitor has decided to add a partially-implemented importing feature from LibertyBans -- scandal! -- so the race is on. We intend to ride ahead on a powerful engine of free software fueled by a relentlessly organized codebase.
There are no breaking changes in this release compared to 1.1.0-M1. However, if you are upgrading from 1.0.x, please read the relevant guide for compatibility considerations.
Bug-fixes:
New features:
/libertybans extend
(#115)API improvements:
Other:
Welcome and Merry Christmas. This special and wonderful update constitutes a Christmas present. We bring you new APIs, the highly-demanded exemption feature, and automatic Geyser/Floodgate detection.
However, because it is Christmas, you have to be nice! So, you need to read the new requirements for LibertyBans 1.1.0 before installing it. If you're naughty, you install plugins without reading their documentation.
Please read the page on updating from 1.0.x to 1.1.0
This release, 1.1.0-M1, is a "milestone" release, meaning it contains many features intended for 1.1.0. However, the new features in 1.1.0-M1 are officially unstable and may be subject to change. All feature and API additions become officially stabilized in 1.1.0. This is in accordance with semver.
The Gifts of this Release
Bug-fixes:
STRICT
address-strictness and add setting for STERN
(#187)Improvements:
Other:
Roadmap to 1.1.0
Looking forward, we have:
The page on Upgrading from 1.0.x to 1.1.0 will continue to receive updates as we progress through the completion of version 1.1.0. The full changelog is also available.
Github "milestones", not to be confused with "milestone" releases, provide a rough outline of the plan to complete each feature. Note that milestones are used flexibly, strictly for convenience of planning. Placement on a milestone is no guarantee of a feature's completion.
Please remember that we follow no timelines as this is a free software project maintained primarily by a single obsessively-academic college student. It is an intellectual exercise, however, to deliver the highest quality of features with ambition, creativity, and tact as we aim to surpass all other punishment plugins.
Merry Christmas
Hereafter, LibertyBans supports the Sponge platform, API versions 8 and above. This development, we hope, will extend the usability of LibertyBans. Deployable in many varieties of environments yet utilizing common code, LibertyBans has always been designed to support multiple platforms. The Sponge API is the natural continuation of this impetus.
Moreover, we have solved, by a clever exploit, the longstanding issue which made LibertyBans vulnerable to bugs in other plugins. Specifically, unrelocated libraries in other plugins will no longer affect LibertyBans. We will continue to recommend you to fix these bugs, because your server's stability is our concern too. However, LibertyBans will be able to proceed despite these situations.
Bugs fixed:
/libertybans import banmanager
was not recognized (0d4369849dc029fbc35b06520e429abbe161e514)Feature additions:
/checkuser
command, thanks to @SnakeAmazing . This addon displays whether a user has an applicable ban or mute (#168)LibertyBans/internal/attachments
folder allows attaching driver jars, which is useful for importing from LiteBans H2 (0d4369849dc029fbc35b06520e429abbe161e514)Other:
hypersql/
and libraries/
folders are moved under LibertyBans/internal
. Existing directories will be migrated automatically (d6c7c218103ef59c16082f4ae3ec343f4bfcaf4c)In this release, we formally introduce the new addon system for extending LibertyBans. With the addon system, we can boldly engage ambitious feature requests. Addons require absolutely no performance overhead -- they interface directly with LibertyBans, exactly as if the addons were written into the main plugin.
I understand some users are not enthusiastic about having to install addons rather than configure features. We implemented an addon system to make the core plugin more approachable for beginners and more maintainable for developers. New users ought not to be confronted with a dizzying array of everything we have to offer. Also, the separation of additional features into addons significantly improves code quality through its imposition of clean organization. I have sung the benefits of code quality numerous times, and it is part of our development philosophy.
Velocity users: It is a known issue that LibertyBans cannot enforce mutes. Chat sent by 1.19.1 clients cannot be cancelled, and this is enforced by Velocity. See this Velocity issue for more information: https://github.com/PaperMC/Velocity/issues/804. For a workaround, install LibertyBans on the backend servers and configure multi-instance synchronization as documented on the wiki.
Bugs fixed:
Improvements:
Feature additions:
Addons released:
/libertybans checkpunish <id>
command (#93)/libertybans staffrollback
which rolls back punishments made by a staff member. Includes a confirmation message if configured (#86)The significance of the release date: I originally intended this release for yesterday, August the 16th, a famous birthday. Also, there are two existing LibertyBans releases on 16th's of other months.
Hello friends, and welcome to the two-year anniversary of LibertyBans' release on SpigotMC.
The first release on SpigotMC, on July 4 2020, was riddled with bugs and largely untested. The plugin acquired prime functionality starting in about December 2020. Therefore, it is appropriate and ironic that this release, 1.0.2, is mainly a bug-fix release. It is our stated philosophy to prioritize bug fixes over new feature requests.
Bugs fixed:
Features added:
Other:
Since July 4 2020, LibertyBans has made remarkable progress. We crossed the 1.0.0 milestone at the beginning of this year and thenceforth began to guarantee a stable API, with new ambitious features such as PostgreSQL support and multi-instance synchronization. To increase adoption and accessibility, we provided more importing features and approved new translations. We intend to continue this progress to meet the great volume of feature requests on the issue tracker.
None of this would be possible without you, the user. Individual contributions drive the search for perfection by finding unexpected behavior and identifying areas of improvement that may not be otherwise visible to primary authors. Almost all the changes in this release were motivated by user reports or direct contributions. Thus the /libertybans
command, without any arguments, displays all users who have contributed, in any fashion, to the development of LibertyBans.
This release, I have no sprawling sentences of extravaganza to entertain your mind. Nevertheless, significant happenings abound! It was recently announced on the associated community discord server that Simon and myself will be working to re-shape that discord server into a broader community. In that announcement, you will find many wonderful words and phrases.
In addition to the changes described below, the list of contributors and commended users in /libertybans about
was updated in this release.
Bug-fixes:
Features added:
Other:
Please note, if you are on 0.8.1 and waiting for the 0.8.2 release, rest assured that 0.8.2 with its promised 1.x compatibility mode will still be released at some point. Such a compatibility mode requires a non-trivial amount of development effort. Moreover, we re-affirm the long-term support policy that 0.8.x will remain supported until at least 4 months since the availability of 0.8.2.
Introducing the long-awaited, much-anticipated, rumored and reputed release of the times!
1.0.0 is officially released in stable form!
This New Year's special release brings a guaranteed stable API to LibertyBans, providing a solid basis for a healthy and long-lasting period of growth for the plugin and its community.
New features and improvements:
Improvements to usability, to make LibertyBans a more popular plugin (in the traditional sense of the word popular):
For existing users, a robust and easy (hopefully easy) migration path from 0.8.x is provided:
A reminder and some comments on the long-term support policy: