This release avoids removing armor with the Curse of Binding enchantment (by default).

Users can opt for still removing such armor by changing the following config option:

Thanks to @Gropinou for pointing out this oversight.

Updating default config to work with older versions of MC out of the box.

Due to the default cuffs in the default config having been populated a while ago (before 1.13), the server identified them as a legacy item.

And because of that, legacy material support was implemented on the server side. However, this was completely unnecessary.

Thanks to @Sohqil for the report!

Thanks to @Sohqil for the report

This change (when enabled, it is disabled by default) will allow players to craft and/or rename their items such that they are identified as cuffs by the plugin.

The new config entry:

Now showing an empty line (instead of the default English message) when a message is removed from the config.

No longer allowing player A that is cuffed by player B to cuff player B as well.
This would previously introduce issues.

Thanks to @ElgerElg for bringing this to my attention.

Thanks to @The_osher for the suggestion.

The feature can be enabled by setting the (new) config entry:
There are 3 modes:

• GROUND
  • The items are dropped (like before)
• DESPAWN
  • The items are despawned
• STORE
  • The items in the inventory are stored on file
  • When the player is uncuffed, the items are given back to the player

When saving the inventory, slots corresponding to items is also stored.
For any of this to work, you'll obviously need drop-items-upon-cuff: true.

Alongside that, added a new command:
/cuffemclearstoredinv <player> - allows clearing the stored inventory of a player (i.e one can do so when they leave by using the cuffed-player-leave-commands commands).

There are also a number of new messages that go along this new feature.

Showing a message when target is immune as well as when cuffing player does not have permission.

New message in config.yml:

Thanks to @Willyema to bringing the issue to my attention.

Fixed config handling and reload issue.

Previously the config was overwritten way too often making it difficult to reload the actual contents of it.

Added possibility of specifying console commands to be executed upon right clicking on a player in order to cuff them.
These commands can be specified here in the config as follows:
Each command can parse {player} or {dragee} to the name of the player being dragged and {dragger} to the name of the playe doing the dragging.
You can specify as many commands as you wish.

Now able to ignore Citizens NPCs when cuffing a player.
This behaviour can be changed with the config entry ( allow-cuff-NPCs: false).

Now able to cuff a player without cuffs using the /cuff <target> command. Permission required: cuffem.cuffcommand (it's different from the cuff permission used with cuffs).
You can (optionally) limit this to within the same world or even within a certain radius.
New config section:
New messages in config:
Thanks to @_ItsLinus_ for the suggestion!

Added command:
/setcuffitem - needs permissions cuffem.setcuffitem (default: OP) - sets the item in your main hand as the cuffs.

This also introduces a new config entry:
PS: The old config entries for cuff-type and cuff-name are still used if (and only if) nothing is specified for cuff-item.

Added Bstats:
https://bstats.org/plugin/bukkit/CuffEm/10785

Added /cuffemreload command to reload the config (messages, as well as all other settings).

Fixed issue where the default item (in the new cuff-item section) would always overwrite the previously specified item type and name (issue introduced in 1.4.0).

Includes a new config entry whether or not to add bStats.
Incldues new message for reloading.

New config entry:
New message:
Thanks to @MOLONxd for the wonderful suggestion.

The uncuff sign system does not work on Minecraft versions before 1.14.1.
As such, I've now disabled it if a lower version of Minecraft is detected.

Added uncuff signs.

These are signs which will uncuff all the players you have cuffed at the time.
Additionally (optional), commands ( uncuff-sign-commands in config) may be run by the cuffing player when the sign is clicked. These commands have the {cuffed} placeholder for the cuffed player.
If multiple players were cuffed, then the commands will be executed for each cuffed player.

One can set an uncuff sign using the /setuncuffsign command ( cuffem.setuncuffsign permission node, defaults to OP).
The data for this sign is saved within the sign. So removing/breaking the sign will remove this data.


Improvements to commands

Some internal changes and slight improvements to tab-completion.

You are now unable to uncuff players that were cuffed by somebody else (previously possible) unless you have the cuffem.uncuff.other permission node (defaults to OP).

Now supports the Vehicles plugin.

Works similarly to the QAV support.
EDIT:
Since there's only ever (up to) 1 extra seat in vehicles within this plugin, only one dragged player can be put in the vehicle.

PS:
If anyone finds an issue, don't hesitate to let me know.

Players with the following permission will not be able to be cuffed:
cuffem.immune

New config entry:
Defaults to false (previous behaviour).

New message:
Shoutout to @Cedric2205 for the suggestion.

New config entry:
Defaults to false (previous behaviour).

Shoutout to @Cedric2205 for the suggestion.

Added /uncuff command. You'll need the cuffem.uncuff perms (defaults to OP).

Added 1.14.3 support

A fix for updated QualityArmoryVehicles
No other changes were made.

Thanks to @Francisc for help with testing.

Not all messages were listed in the config and one was misnamed.

Added a permission node that is needed for commands to be dispatched when "prisoner" leaves.
Permission node: cuffem.dccommand

Suggested by @LexionGVC

Special thanks to @LexionGVC for the feature suggestion!

There is a new config entry that defaults as follows:
If you want to disable the feature, just use