ВЕРСИИ (8)

# What's changed - *v0.7.1* - fix: Channels to send messages to, can now be any channel, that can receive text messages. - Checked compatibility for the Paper-1.20.x-API - Fixed some grammatical errors. One in the copyright header in the source files and one in the embedded chat message resource. Take a look at a freshly generated one to spot the change in the default death-ban message. **Full Changelog**: https://github.com/eingruenesbeb/Yolo/compare/v0.7.0...v0.7.2 --- *Note regarding future versions:* This plugin/mod is currently being reworked, to work with other modding APIs, which requires a significant amount of work. So please be patient for the full release and snapshots for v2.0 (this current version is feature complete in regards to my initial plans aka. v1.0).

## What's Changed - New features: - Text placeholder for death-messages - Reviving a player can now trigger a chat and discord message. - Instead of giving the player effects upon teleportation, they are now set into a ghost-like state, which is removed upon hostile actions. It lasts 600 ticks (30s@20TPS) - The death-ban and the revival process can now be monitored and influenced by using Bukkit's Event-API. - Fixes: - Fixed an issue with player related replacements in case of a `PlayerDeathEvent`. - The `/revive` command now only gives out a success status, if the `isToRevive` flag has actually been set. - Deferred the ban on a player's death by a tick, because some stuff (like death messages being sent) broke when the player was banned in the same tick. - Updated documentation and some messages. **Full Changelog**: https://github.com/eingruenesbeb/Yolo/compare/v0.6.1...v0.7.0

## What's Changed * fix(PlayerManager): Fixed players being revived, before they respawned. * feat: Player-data is now periodically saved (every 5min @20TPS), to limit potential data-loss upon server crashes. **Full Changelog**: https://github.com/eingruenesbeb/Yolo/compare/v0.6.0...v0.6.1

## What's Changed * Kotlin migration and 0.6.0 features by @eingruenesbeb in https://github.com/eingruenesbeb/Yolo/pull/5: - feat: Added `/revive` command. - feat: Added command `/checkout_death_location` for admins to look for potentially duplicate items. - feat: Added features requested in https://github.com/eingruenesbeb/Yolo/issues/4 - feat: Ability to disable inventory restoring and teleportation on revive - refactor: Migrated to Kotlin - refactor: Completely removed AdvancedBan functionality and dependency. **Full Changelog**: https://github.com/eingruenesbeb/Yolo/compare/v0.5.0...v0.6.0

New features: - Ability to send customizable messages in chat upon: - death - totem use - Ability to send a discord message upon totem usage. - Improved text-placeholder system. The new universal placeholders provided are: - `%player_name%` will be replaced with the player's name - `%totem_uses%` will be replaced with the amount of totems of undying the player used. [**Full Changelog**](https://github.com/eingruenesbeb/Yolo/compare/v0.4.0...v0.5.0)

- feature: Added the possibility to specify a custom resource pack and the ability to turn off forcing it on hardcore players. [**All changes**](https://github.com/eingruenesbeb/Yolo/compare/v0.3.1...v0.4.0)

fix: Fixed an issue, where the plugin wouldn't load, without Spicord installed.

This is the first public release of the plugin. For details about the features, please check out the README. Here is a short overview of the features: - Bans players, if they die and the server is on hardcore mode, regardless of when the world was generated. - Sends a resource pack, that exchanges the default hearts for their hardcore counterparts. - Players can be exempt from this, by having the yolo.exempt permission. - If AdvancedBan is installed, it will be used for player bans and the default ban reason can be adjusted via a message template called @Hardcore_death. - If Spicord is installed, a configurable message can be sent to a Discord text-channel of your choosing upon a non-exempt player dying.