VERSION 2.2.3 - MAXSTAFF

• Duration format will now be validated before applying sanctions. There was a bug that caused applying 0 to result in applying days or hours when it shouldn't.
• Real staff have been included in freeze events sent to Discord.
• Several issues with sanctions such as IP ban, IP unban, mute, etc., have been fixed.
• A new section has been added to the MySQL section of config.yml.

database:
  enabled: false 
  host: "localhost"
  port: 3306
  database: "maxstaff_db"
  username: "root"
  password: ""
  use-ssl: false #RECOMENDADO PONERLO EN TRUE
  server-id: "server-1" #ESTO ES DE SUMA IMPORTACIA, PONGALE UNA ID A SUS BACKENDS
  status-servers: #ESTO ES OPCIONAL, SOLO ES DECORACIÓN
    survival:
      name: "Survival"
      host: "127.0.0.1"
      port: 3306
    lobby:
      name: "Lobby"
      host: "127.0.0.1"
      port: 3306

VERSION 2.2.2 - MAXSTAFF

• A new freezing system has been added. Now, when a player is frozen and disconnects, they will be banned for a number of days. This number of days can be customized in the config.yml file.

#Material Configuration for Staff Mode
staff-mode:
  items:
    punish:
      material: "NETHERITE_HOE"
    freeze:
      material: "PACKED_ICE"
      helmet-material: "PACKED_ICE"
      ban-on-disconnect: #NUEVA SECCIÓN
        enabled: true
        days: 7
        reason: "Disconnected while frozen"
    players:
      material: "CLOCK"
    inspect:
      material: "CHEST"
    vanish:
      material: "NETHER_STAR"

• MySQL connections have been improved so that sanctions are applied simultaneously across all servers.
• The /invsee command can now check the inventories of Disconnected players. These inventories can be The files are visible but cannot be modified. A new folder called invsee-cache was also created where player data is stored. IMPORTANT: Deleting this folder and its files will not cause players to lose data.

VERSION 2.2.1 - MAXSTAFF

• A problem with the backends was fixed, specifically a problem with the Mute function in Networks.
• A new section was added to the config.yml file. This section is entirely optional, but it allows you to track the servers connected within MySQL.

status-servers:
survival:
name: "Survival"
host: "127.0.0.1"
port: 3306
lobby:
name: "Lobby"
host: "127.0.0.1"
port: 3306

• A new command was added: /maxstaff debugperm <player> <type>. This command allows you to check the player's permissions and whether they are enabled or disabled.

VERSION 2.2.0 - MAXSTAFF

• The permissions problem has been fixed, they now work like this:

It blocks if the target has:
maxstaff.admin or
maxstaff.punish.protected
And the staff that imposes sanctions doesn't have maxstaff.punish.override.

• A new /invsee command was added with the permission maxstaff.invsee

VERSION 2.1.3 - MAXSTAFF

• The MySQL issues have been fixed; the backends now connect without problems.