Import from other plugins

Old punishments come across with their dates, reasons, staff names and active/removed state. Imported players can be looked up by name right away. Run the import once; running it twice creates duplicates.

Set the source under import: in config, then:

/finexbans import <source>

The import runs in the background and reports how many records were added and skipped.

From a LiteBans-style database

import:
  litebans:
    type: h2              # h2 (default file storage) | mysql | mariadb | sqlite
    file: plugins/LiteBans/litebans
    host: localhost
    port: 3306
    database: litebans
    username: root
    password: ''
    table-prefix: 'litebans_'

/finexbans import litebans reads bans, mutes, warnings and kicks. Names come from the history table.

TIP

If the source plugin still runs its own H2 file, stop it first — H2 allows only one process on the file at a time.

From an AdvancedBan-style database

MySQL only — its default HSQLDB file needs a driver we do not ship; switch it to MySQL first.

import:
  advancedban:
    type: mysql
    host: localhost
    port: 3306
    database: advancedban
    username: root
    password: ''

/finexbans import advancedban

From vanilla

import:
  vanilla:
    folder: '.'          # server root with banned-players.json and banned-ips.json

/finexbans import vanilla. After that you can clear the vanilla ban list — FinExBans handles logins itself.