FAQ
On this page(11)
How do I update SnUserTransfer?
Download the newer release and replace the jar. config.yml and the lang file auto-merge on
restart; profiles.yml is never touched.
Does it support Folia?
No, SnUserTransfer is not Folia-compatible. It targets Paper 1.20.x and 1.21.x.
The plugin disabled itself with [Sn] License: FAIL
Either the key in plugins/.Sn-License/license.yml is still the placeholder, or the server cannot
reach the license backend over HTTPS while booting. Paste the key and restart.
Do the two players have to be offline?
They are kicked automatically when the transfer starts and cannot join until it ends. Both see a screen explaining that their data is being migrated.
We run a network that shares one MySQL database
SnUserTransfer only kicks and blocks the accounts on the server where the command runs. Make sure
both accounts are offline on every server of the network before running apply, or another server
may write their data again while the transfer runs.
A plugin's data was not moved
Read reports/<id>.txt: it lists every store and file that was found, and every omission with its
reason (a file over the size limit, an unreachable database, an excluded folder). If the plugin
keeps its data somewhere discovery cannot see, declare it in profiles.yml.
Some stores say Queued
Those are H2 databases and shared files that their plugin keeps open while the server runs. They
are written on the next restart, before any plugin enables. Check them with /sntransfer pending.
Can I undo a transfer?
Yes, with /sntransfer undo <id>, where <id> is the one shown when the transfer finished (also
listed by /sntransfer backups). Transfers applied at a restart get their own backup id. Backups
are kept for backups.retention-days.
Are the backup files sensitive?
Yes. backups/ holds copies of player data, and backups/ and queue/ also hold the MySQL
connection details needed to reconnect for an undo or a queued run, password included. Treat
both folders like your server's config files and do not share them publicly. The report files
under reports/ never contain passwords.
An H2 database is reported as unreadable
Files written by H2 1.x (including every .h2.db file) cannot be opened. SnUserTransfer reads H2
2.1 and H2 2.2 or later files.
A player's name is the same as a plugin file name
A file such as config.yml is never renamed as if it belonged to a player called Config. The
report lists it as an omission so you can check it by hand. Its content is still checked like any
shared file, so run preview first for such a player.