YAPS-0.8.jar
Details
-
FilenameYAPS-0.8.jar
-
Uploaded by
-
UploadedMay 1, 2026
-
Size64.40 KB
-
Downloads20
-
MD59a99e202a9a7b695a49d55028eff0d25
Supported Bukkit Versions
- 26.1.2
Changelog
1. 🏷️ Title
YAPS 0.8 — Maintenance, Compatibility & Internal Cleanup Update
2. 📝 Short Summary
This update brings Yet Another Protection System to version 0.8.
Most of the work in this release is internal. It focuses on cleaning up the codebase, improving configuration reload behavior, updating project dependencies, and preparing the plugin for better long-term maintenance.
This is not a major feature update, but it helps make the plugin cleaner and more reliable for future improvements.
Version changed: 0.7 → 0.8.
3. 🔧 What Changed
- Updated plugin version from 0.7 to 0.8.
- Updated the Spigot API dependency from 1.20.4-R0.1 to 26.1.2.
- Refactored
Config.javaby moving configuration value loading into a separateloadValues()method. - Improved config reload behavior so configuration values are loaded again when reload is called.
- Added plugin permissions for:
yaps.infowandyaps.setexit
- Changed the save queue from
LinkedListtoConcurrentLinkedQueue. - Changed the loaded areas list to use
CopyOnWriteArrayList. - Simplified item handling logic inside
YAPSItemHandler. - Removed the old embedded
Metrics.java/ bStats class. - Removed the old metrics startup code from plugin enable.
- Removed some plugin disable/re-enable calls during shutdown/reload flow.
4. 🎯 Why This Matters
For server owners, this update is mainly about maintenance and stability preparation.
The plugin now has cleaner configuration loading, better internal handling for saved protection data, and improved handling of area lists in memory. These changes are especially useful for a protection plugin, because it needs to keep block and area data consistent while the server is running.
The removal of the old embedded metrics class also makes the project cleaner and reduces unnecessary internal code.
5. 👥 Who This Update Is Useful For
- Server owners using YAPS for block and area protection.
- Servers that want a cleaner maintained version of the plugin.
- Users who rely on config reloads.
- Server setups using newer Spigot-based environments.
- Developers or maintainers continuing the plugin.