Releases: YouHaveTrouble/PreventStabby
2.1.3
- prevent null players being forwarded to events and message sending logic edge case
Download available on modrinth
Full Changelog: 2.1.2...2.1.3
2.1.2
- fixed combat log announcement being sent regardless if player was in combat or not
- fixed broken pvp state check
Download available on modrinth
Full Changelog: 2.1.1...2.1.2
2.1.1
- fixed inverted config option for announcement of combat logout
2.1.0
- logout punishment can now not kill the player, but still announce the message
- fixed an exception raised when using the plugin without worldguard installed
2.0.0
Warning
This is a breaking change if you're upgrading from 1.x, you will need to reset/remove your database file!
Changes:
- rewrote most of the code
- plugin is now using one unified check for all combat events to prevent inconsistencies
- plugin is now using more modern checks, resulting in requirement of paper api and minecraft version of 1.21+
- most of the bugs plagueing 1.x have been resolved thanks to simpler system
2.0.0-rc3
2.0.0-pre-5
Caution
THIS IS NOT YET READY TO USE IN PRODUCTION!
- fixed dangerous block blocker not having a list of blocks to block
2.0.0-pre-4
Caution
THIS IS NOT YET READY TO USE IN PRODUCTION!
- updated everything to 1.21
- fix potential npe when checking potion effect cloud's effects
Full Changelog: 2.0.0-pre-3...2.0.0-pre-4
2.0.0-pre-2
Caution
THIS IS NOT YET READY TO USE IN PRODUCTION!
- Fixed NPE on player teleportation of player entity NPCs
See the previous release description for more information about 2.x
2.0.0-pre-1
Caution
THIS IS NOT YET READY TO USE IN PRODUCTION!
Rewritten the majority of the plugin.
- This build requires paper (or forks) to run
- This build requires minecraft 1.20+ to run
Currently working features:
- pvp toggling
- pvp protections
- bucket stoppers
- combat timer (including placeholder for it)
- combat logout punishment
If you decide to run this plugin, do not do so on a server that previously ran version 1.x. It will convert data to a state likely unusable for 1.x. You will also not be able to switch between 1.x to 2.x and back without possible data loss.