FIXES

• Fixed a bug where the FREEZE death cause did not work.

ADDITIONS

• Added the KILL death cause for death by the /kill command.
• Added the SONIC_BOOM death cause for death by warden by its sonic boom.
• Added the WORLD_BORDER death cause for death by being outside of the world border.

REMOVALS

• Removed banlist patch to fix mistake from older versions (this will no longer be supported from this version onwards).

MISC

• Updated the plugin to support Minecraft version 1.20.x.

FIXES

• Update the AnvilGUI dependency to keep click events from throwing errors.

FIXES

• Combat tagging from entities that are not included in vanilla Minecraft will no longer throw nullpointer exceptions in the console.

FIXES

• Moved world check from on load to on runtime so worlds after plugin has loaded can also be used in config.

Updated the plugin to support Minecraft 1.19, also made use of the build in resource manager of Spigot to significantly reduce the jar size. On top of that I have also updated all dependencies to their latest version which fixes the revive through GUI action.

FIXES

• Config updating will no longer throw an error on startup.
• All messages will now correctly show color codes.
• The MaxLifeParts configuration can now be set to -1 for an unlimited amount.
• Reloading the plugin and executing a command will no longer throw a NPE for players.

UPDATES
- Old configuration files are now added to the "old" folder.
- Messages.yml will now auto update.

ADDITIONS
- Support for Minecraft 1.18 added.
- Support for Java 8 and up added.
- All command messages are now fully customizable in the messages.yml file.

FIXES
- Ban message will now correctly show combat tagger.
- BantimeType by BanCount will now correctly ban players according the amount of bans they have.

FIXES:
- Playerdata will now use the correct player object to do it's functions with, resulting in more accurate outcomes.
- Reviving a player and going below 1 life will now actually kill & ban you correctly.

ADDITIONS:
- Added last death to the player data. Previously statistics were used to determine this.
- Added the FREEZING death cause & ban time.

CHANGES:
- Death ban time-outs will no longer always run the reset spectator death ban method.

FIXES:
- Fixed the "Player has not played on the server before." even tho he definitely did on command execution bug.
- Fixed a bug where permanent deaths would not actually ban players on death.
- Fixed a bug where unbanning a spectator banned player would throw an IllegalStateException error.
- Fixed a bug where losing max health on death would kill the player over and over again until death banned.

FIXES:
- Fixed a message issue with the /nextlifepart showing the time till next max health instead.
- Fixed a possible NPE in the ban deserialization when a none valid UUID was used.
- Fixed NPE in the saving of a ban when killer or incombatwith was a block and type was null.
- Removed debug messages from the CombatLogX hook.
- DeathBans GUI will now show the bans in correct order.
- Commands will now have their description correctly displayed in the vanilla /help command.

CHANGES:
- The plugin will now use its own custom ban system instead of the vanilla one.
- Due to the above, bans caused by the plugin will no longer apply when the plugin is uninstalled.
- Spectator death bans will now automatically end and change the players gamemode to survival and teleport the player to bed respawn location or configurable world spawn.
- Players IP banned due to a player on their network getting death banned will now be able to get custom ban messages.
- Ban expiration dates will now update accordingly when ban is ended pre-emptively.
- Permanent death bans will now actually be permanent and not just 4000 years.
- 'TotalBans' in server.yml has been changed to 'TotalDeathBans' to reflect the actual data better.
- %augmentedhardcore_server_ongoing_bans% and %augmentedhardcore_server_total_bans% will now longer require the player to be logged in to be used.

ADDITIONS:
- Added 2 new bstats charts (ongoing and total death bans).
- Added the commands /addmaxhealth and /setmaxhealth for adding and setting max health to/of the player.

FIXES:
- Fixed an NPE in AH commands when executing them from the console.
- Fixed a possible bug in the 'time till next' commands where it didn't show the correct message when executing for another player.
- Fixed a bug in the deserialization of bans where the killer config was being deserialized as the in combat with variable.
- Fixed a bug where the environment while in combat ban message was showing the environment ban message.
- Fixed an NPE while adding a ban to the server data async while player was already logged out.
- Fixed an NPE in the death event listener.
- Fixed a bug in the death bans GUI where only the last death ban was shown instead of all.

CHANGES:
- The deathbanreset command can now be executed for other players and from the console.
- Got rid of duplicate code in some commands.
- Expiration date of ban messages will now default to 00.00.0000 00:00:00 when not found.
- Having no death message will now show as '-' in the ban message instead of nothing.
- Added a fail safe for spectator death bans on join when players aren't in spectator mode.
- Un death banning a player through the server death bans GUI will now close the confirmation screen upon confirmation.

ADDITIONS:
- AH will now hook into CombatLogX when found and leave all combat tagging related stuff up to it. AH will ban accordingly.

FIXES
- On first join the plugin will now correctly set the revive cooldown according to the settings configured.
- Commands executed on death ban will not throw an NPE anymore and actually execute the commands.
- Lightning on death ban will not throw an NPE anymore and actually spawn a lightning strike.
- Fixed a couple of MySQL errors (weren't being used until now) for deleting players and servers in the database.
- Fixed a couple of spelling errors in the config.
- Commands will no longer be auto completed by minecraft/spigot if the player doesn't have the permission for it.

CHANGES
- The success messages of the /ah commands will no longer show twice if used on yourself.
- The /ah help command will now only show the commands the player has permission for.
- Opening the death bans GUI through the mystats GUI will no longer throw a not allowed error if the player has no death bans yet and will now open an empty GUI.
- You'll now be able to configure the head display of the revive confirmation GUI.
- The plugin will no longer log in the console when a playerdata/serverdata file has been created (YAML).
- The plugin will no longer log in the console when a playerdata/serverdata file has been removed (YAML).
- Moved some configuration items around in the config.
- Changed a placeholder in PlayerDisplay from %player_name% to %player% to be more inline with all other placeholders.

ADDITIONS
- Added an update checker for the plugin to check if a new version is available.
- Added the /ah reset <player> command which will reset a player to it's initial state (lives/life parts/cooldowns/bans). This will also unban the player if death banned.
- Added a new command (/serverdeathbans) which will show the currently ongoing death bans on the server. Players also having the permission to undeathban will be able to do that through this GUI.
- Added the possibility to disable the death screen and respawn directly.
- Added a new permission (augmentedhardcore.bypass.revivecooldown) which will allow the player to bypass the revive cooldown.

FIXES
- Fixed an NPE in the /ah commands if being executed from the console.
- Fixed a major bug with a Pair class being imported from the wrong place.
- Fixed an NPE in the death ban saving.
- Fixed the IP saving of players.
- Fixed the IP column in the database not being large enough.

WARNING
LiteDeathBan has been rebranded to AugmentedHardcore. The plugin has also been rewritten completely from scratch and will NOT use the old LiteDeathBan config.yml, messages.yml and userdata. You will be forced to configure the plugin from scratch and start over with new playerdata (or give the lives/life parts manually).

That being said, I'm proud to announce the complete overhaul of AugmentedHardcore. It has been a long term goal of mine to redo this plugin from scratch and add many many many new features and fix broken/buggy/sloppy code. I strongly recommend updating to this version even if it loses your current userdata. The benefits, new features, performance improvements and many more things will definitely out way the user-data you'll lose.

It would be fairly impossible to list all changes that have been made to the plugin here so for a better understanding what has changed to the plugin or what has been added/removed, please read the home page of the plugin here. In addition to that, a new wiki page has been created here where you'll find an extensive list of documentation and help in regards to the plugin.

Fixes

• Fixed NullPointerException when executing a command on an offline player.

This will be the last hotfix for a while, sorry for the continuous small updates, no more errors from now on!

Fixes

• Fixed data lookup for players on command executions. (Yes, again, sorry!)
• Added an API version to get rid of the "No API version found for LiteDeathBan" console warning.

Fixes

• Fixed data lookup for players on command executions.

Fixes

• Fixed memory leak on player kick.

Changes

• Plugin will now check for older version on OP join (and if enabled) instead of on server start.
• Added comments to code.

Fixes

• Fixed bug where players wouldn't get a data file on first join.

LiteDeathBan is now also compatible with Spigot 1.13.

Features

• Old config file detection warning.
• Old messages file detection warning.
• Tab menu message may now also show life parts.
• Players who haven't logged on since installation of plugin may now receive data file + data if needed (and if played before).

Fixes

• Fixed wrong resource ID in the plugin update checker.
  
• Fixed/implemented the "none" warning option for combat tagging.
• Fixed bug where the revive command would check the revive cooldown of player getting revived instead of player reviving.
• Fixed tiny memory leak when trying to revive someone.
• Fixed not getting error message when trying /lives [player] | /lifeparts [player] without having the permission for it.

Changes

• Complete config class overhaul.
• Complete command class overhaul.
• Tab menu message must now be disbaled in messages.yml.
  
• Changed some placeholder names + default values in the messages.yml.

Fixes

• Data lookup check in commands has been fixed.

New Features

• Update checker.
• /addlives <player> <amount> - Add an amount of lives to a player. + permission.
• /lifeparts [player] - Check your current amount of life parts [or that of another]. + permission.
  
• litedeathban.bypass.loselives - players with this permission will not lose lives on death.
• Disable per world option for losing lives, bans, combat tag, revive, getting life parts, losing life parts, loggin deaths and logging death bans.
• Option to not die in worlds which are disabled for losing lives.
• Option to have players start with multiple lives on first join.

Fixes

• Fixed bug where notification and broadcast messages on receiving a new life was not showing the correct amount.
• Fixed bug where console wasn't allowed to use any of the commands.
• Fixed bug where commands were checking if player already played on the server instead of player already having data on the plugin resulting in errors.
• Fixed capitalizing on some error messages.
• Fixed bug where players would not lose lives if having the bypass.ban permission.
• Fixed bug if player had too high of a playtime it would exceed the integer max value for bantime. The maximum bantime is now max integer value (2,147,483,647 minutes).

Changes

• Redid the whole permission system.
• All broadcasting messages are now disabled by default.
• OP's now have all permissions by default.
• Command usage description changes.