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
- accounted for more edge cases with player data cache
- improved the check for protected pets
Complete plugin rewrite for efficiency and reduction of complexity.
Please report any bugs and missing features. Either in the issue tracker or on discord.
- Spigot support was dropped.
- Folia support was added.
- Legacy version support was dropped. Plugin MIGHT work on versions older than specified. There will be no support provided to those who try that.
- Plugin went from 2mB to 88kB.
- fix api errors by adding missing static handler getters
- if a message in config is an empty string (
""), the message will not be sent to the player
- fixed a bug where pets were not attackable when pvp was forced on and pets owner had personal pvp off
- tempting pets (horses) should not cause player to enter combat or display action denied message
- added placeholder for forced pvp state
- Huge API changes - consider yourself warned if you were using the plugin API
- Fix worldguard flag loading on 1.19.4
- added %preventstabby_pvp% placeholder that shows current pvp state
- placeholder parser no longer has an option to cause sync database query
- command with no arguments now defaults to toggling pvp state instead of help menu
- Fixed dependency issues on older server versions
- fixed flipped boolean on allow_fishing_rod_pull