Limits how many tool cupboards each player can authorize to

Supported Games
GameServerKingsGameServerKings

Rewrite

  • Completely rewritten the plugin.
  • Removal of datafile system.
  • Players can auth to a max of x tc's defined in the cfg and with their permissions assigned.
  • Toolcupboards can have x max players authed on each individual Toolcupboard.
  • Removed chat commands since they are obsolete.
  • Reworked the new permissions.
  • Do a clean install of the plugin and delete cfg/data/language files

Permissions

  • maxcupboardauths.restrict - Restricts authing limit for every tc
  • maxcupboardauths.tcrestrict - Restricts players personal max authing limit
  • maxcupboardauths.tcdefault - Default perm max TC to auth on
  • maxcupboardauths.tcvip - Vip perm max TC to auth on
  • maxcupboardauths.bypass - Perm to bypass restrictions

Note : : tcrestrict should always be assigned before assigning tcdefault or tcvip.this is used in several parts of the code and starts as a main permission

Configuration

{
  "Put Debug to console": false,
  "Settings ToolCupboard": {
    "Max total Auths for each TC": 2
  },
  "Settings Players": {
    "Max Auths for default Player": 2,
    "Max Auths for vip Player": 3
  }
}

Put Debug to console - Debug mode true/false

Max total Auths for each TC - Restricts the Amount of players to auth on each TC

Max Auths for default default/vip player - Restricts the amount of TC's to get authed on

Localization

{
{
  "Denied": "You cannot authorise to this cupboard! there are already the maximum amount of people authed to it!",
  "DeniedPlacement": "You cannot place a tc u have reached your limit of Toolcupboards to auth to!",
  "DeniedPlayer": "You reached your personal Tc auth limit"
}
}

Credits

  • Requested by Bezz 2
  • Thx to redBDGR the original author of the old version
This plugin is unlicensed and the original author reserves all rights to it.

The original author may request that this plugin be removed and there is a risk that the plugin may be unavailable in the future.

Note that the current maintainer may not have permission to assign a license to the plugin if they are not the original author, so explicit permission would need to be obtained from the original author in order for the plugin to remain openly available and guarantee that it will be around for all to enjoy going forward.