Deny /back commands into WorldGuard regions and GriefPrevent

Previously I was using Spigot's serialization of locations into the last-locations.yml file. There would be an error deserializing if a world was changed. Now I'm using my own serialization in which I store the UUID of the world, and if the world is deleted, only a 1 line warning will be displayed. If you were having this problem, it will likely be fixed after the second restart.

· Fixed a bug where /back wouldn't do anything. To fix this I had to change the built-in /back command to /dback. All forms of /back in the config will still work for the built-in command, but only /dback will be tab-completed if no other back plugin is enabled. · Added a check to see if the back flag is registered.

This update is tested for 1.20 Also in this update, a built-in /back command was added. By default, it is disabled. You can customize the command settings with a new configuration section. Code (YAML): back-command : # register a back command for DenyBack - The command will show up in tab complete when the server restarts register : false # send player back to the last location that they are allowed to go use-last-available-location : true # how many seconds before player will be teleported teleport-delay : 0 # message sent to player when they use the command message : '&6Returning to previous location.' To enable the command, set register to true.

A whole bunch of random things this update · New config option: deny-nonmembers: this will not allow people to /back into regions that they aren't a member of · New config option to change the deny message · New config option to enable using GriefPrevention's deny message instead of DenyBack's message · Debug mode - You guys won't have to use this unless you are having problems · DenyBack now hooks into CMI's minimum teleport distance so it records teleportation more consistently Check the config notes for a little more information on each setting. Let me know if you want any new features.

It has definitely been a while since I last updated this plugin. I did a bit of optimization, but the main feature that effect you will be the new back-on-death check. There is 1 new option in the config called back-on-death-permission. This option allows you to enter a permission string to enable the plugin to check that permission when the player dies and stores that location. In summary, this makes the plugin more accurate in determining a player's last position. Config example option: Code (YAML): # the permission that allows players to /back to their death location back-on-death-permission : 'essentials.back.ondeath' # cmi.command.back.ondeath for cmi

Plugin works with 1.19

Plugin works with 1.18 now

Change Log: · Records teleportation and last location more similar to essentials (Will be more accurate in denying the correct locations) · If GriefPrevention is enabled, players will not be able to do /back to get back into another player's claim they do not have access too. This can be disabled in the config · /denyback reload command to reload the config

Now works with 1.17 & a few new features were added. · Added config so you can choose which commands are denied · Always has a back location stored for a player so it stops the teleport from happening instead of checking after the teleport · now works with cooldowns · Now records last location in a file so it works when server restarts