Bug fix

• Fixed missing permission checks for riding players. Thanks to @AnttiMK for the pull (#45).

Changes

• Fixed NullPointerException
• Added support for Bukkit 1.13+
• Updated shadow for Gradle
• Bumped plugin version to 1.7.1
• Changed Java version to 21
• More cleanup

Updates

• Added bStats (Metrics).
• Code cleanup.
• Rewrote the hook handler for expansion.
• Added support for Residence.
• Changed effect to be compatible with Minecraft 1.21.
  
• Bumped to version 1.7.0.

This version will only work with Minecraft 1.21+

What's Changed

• Fixed so that players riding other players cannot move inside a claim they are banned from.
• Code cleanup.

I'm not entirely sure what happened here, but the file I uploaded for v1.6.6 is corrupt. Use this one instead.

BUG

• Fixed a ConcurrentModificationException bug when combat mode is activated.

BUGS

• If a new player was banned from a claim and the player had not previously been on the server, the player would not be recognized. This has now been fixed.

Fixed bugs

• Better combat handling
• Fixed IllegalArgumentException
• Better implements for hooks
• Fixed stuck-in-claim issue

Added support

• Added support for RegionDefence

Bug Fix

• Another ClassNotFoundException bug fixed for GriefPrevention users.
  

Bug fix

• A fix for the /kfc command for GriefPrevention that provided ClassNotFoundException in the console.

In version 1.6.0, major improvements have been made.

• Gamemode spectate will no longer be banned from claims. Everyone in the spectate mode will bypass any bans.
• Major improvements have been made for eviction of players. Now they will no longer be stuck in claims or end up in the exact same place every time. A big thanks to @Mithrandir who gave away his algorithm for me to use.
• Following a popular request, I have given in to create /kickfromclaim [player] command function.

The Kick command is optional and can be turned off in the configuration file if you prefer an another KickFromClaim plugin.

New entry in the configuration file

Bug Fix

• Fixed a NullPointerException for GriefPrevention users.

Feature Update

• Added the ability to exclude all players from your claim with a command. Use /bfcall in your claim and no one else will be able to enter your area. If you have given trust to a player, they will not be banned.
• To use the command, the player must have the bfc.banall permission.

BUG FIX

• Fixed a ConcurrentModificationException bug triggered when in combatmode. Thanks to CrispyDairy for reporting!

Improvements

• This release is aimed at GriefDefender 2.0.0. As of this release, BanFromClaim will not work with GriefDefender below version 2.0.0.

As of Minecraft 1.17 support, BanFromClaim is already ready for 1.17.

Bugs

• Fixed bugs relating to GriefPrevention. Version 1.5.4 will not work with GriefPrevention!

Improvements

• #5 This suggestion have been addressed. Added checks for void and the possibility to add a safespot.
• New methods for teleportation from claim and the way to deny entrance to claim when banned.

Features

• When a player tries to enter a claim when banned, a particle effect will be visable.
• Added new command /bfcsafespot for a second teleportation spot if a player teleports to void after being banned from claim.

EDIT: For GriefPrevention users BanFromClaim is broken on this version. Please use version 1.5.3 until fixed. Estimated fix date: 27.04 EST

Fixed bugs

• #4 Could not pass event PlayerMoveEvent to BanFromClaim

Features

• Combat Mode has been added so that the players can not use their claims for sanctuary. If you hit a player who is banned from your claim, he/she will be able to enter the area. Combat Mode are optional in the config file.
  
• You can now ban offline players.

Bug fixes

• Some performance issues has been solved, thanks to HexedHero for pointing out some obvious issues.
• Players who were banned from a GriefDefender claim ended up one block down in the ground. This is now fixed.
  
• message.yml file has changed due to offline players.

New config file
message.yml

I'm sorry, but in the previous update I discovered that I made a mistake that could cause players to be banned from the world.

This only applies to those who use GriefDefender. The bug has been fixed in this update.

Bug fixes

• For some reason I forgot to secure the owner from getting banished from his own claim. This is now fixed. Thanks to @Amadeus for letting me know!
• Added new locale to the messages.yml.

First release