How it works

Client

1. Client is connecting to the server

   Mod sends protocol version and token (if exists)

2. Packet received

   Mod puts it into it’s config

Server

1. Player is logging in

   1. Adding player nick to outdated list

   2. Server schedules next operations

      if Player still online:

      Player nick still in outdated list
      Kick player with kick.outdated message
      tokengen.enabled is "true" and there is no db and player nick not in tokens.yml file
      1. Generate random token 2. Send token to player 3. Save player’s token in tokens.yml file
      tokengen.enabled is "true" and there is db and player nick not in storage.mysql.tableName table
      1. Generate random token 2. Send token to player 3. Save player’s token in storage.mysql.tableName table
      Player nick not in verified list
      - Kick player with kick.message message
      tokenDisabling.enabled is "true" and there is no db and player nick in disabled_tokens.yml file
      • Kick player with message from disabled_tokens.yml file (if specified)
      tokenDisabling.enabled is "true" and there is db and player nick in tokenDisabling.tableName table
      • Kick player with message from tokenDisabling.tableName table (if specified)
      Else
      - Pass player
      • Parse all placeholders
   3. • Remove player nick from outdated and verified lists

2. Packet received

   1. Parse client protocol version and player’s token from packet
      Protocol version is compatible
      - Remove player nick from outdated list
      There's no db
      • If name in tokens.yml file and token is valid: - Add player nick to verified list
      Else
      • If name in storage.mysql.tableName table and token is valid: - Add player nick to verified list