PkLogin
Migration

Importing from AuthMe

Move every AuthMe account into PkLogin with one command.

Place the AuthMe database

Put authme.db at plugins/AuthMe/authme.db, or point PkLogin at it:

config.yml
authme-import:
  # Absolute path to authme.db. Empty uses plugins/AuthMe/authme.db.
  database-path: ""

Run the import

/pklogin authme-import

The import runs asynchronously and reports progress every 100 accounts.

Remove AuthMe

Once the import reports finished, stop the server and delete the AuthMe jar. Two authentication plugins competing for the same login events will not end well.

What is preserved

FieldNotes
PasswordImported as an AuthMe SHA256 hash, read-only. Auto-migrated to your configured algorithm on the player's first successful login.
IP addressKept, so the per-IP limit and /pklogin dupeip work from day one.
Registration dateKept.

Safe to re-run

Accounts already imported are skipped, so running the command a second time costs time and nothing else.

Passwords after the import

AuthMe SHA256 is supported for reading only. PkLogin never writes a new hash in that format: the first time an imported player logs in successfully, the password is silently re-hashed with whatever Security.hash-algorithm says. Nobody has to reset anything.

See Password security for the algorithm list.

On this page