Importing punishments
Punishments → Import (needs punish.import, Owner by default) brings bans, mutes, warnings and kicks from
another plugin. The other plugin's data is only read, never changed. An active punishment comes in only when the
importing role could give it in the panel: its permission, its length within the role's limit and a player the role
may punish (ended and lifted ones always come in as history).
- The page shows which sources it found on this server.
- Preview counts what would come in by type, the duplicates and the records that cannot be imported, with a few samples. Nothing is written yet.
- Start imports in batches. You can leave the page; the report shows the result and the records that failed.
- Importing the same source again skips what is already here, so a stopped import can simply be run again.
Sources
| Source | Where it reads |
|---|---|
| LiteBans | Its MySQL/MariaDB database, with the connection from plugins/LiteBans/config.yml. The default H2 storage of LiteBans is not supported: switch LiteBans to MySQL first. |
| AdvancedBan | Its files (plugins/AdvancedBan/data/storage.script) or its MySQL database (plugins/AdvancedBan/MySQL.yml). |
| EssentialsX | plugins/Essentials/userdata/*.yml (mutes and bans of each player). |
| Vanilla | banned-players.json and banned-ips.json in the server folder. |
Imported punishments keep their reason, dates and who gave them, and show the source in the panel. Active ones are enforced right away.
An IP ban needs the player it belongs to: bans of a bare address (common in banned-ips.json) are counted as not
importable in the preview.
AdminControl's punishments hold on every server of the network. An active LiteBans ban or mute limited to some
servers (a server_scope other than *) is counted as not importable too, rather than widened to the whole network;
kicks, warnings and punishments that already ended are imported as history.
AdminControl's warnings do not end on their own. A temporary warning from another plugin that already ended comes in lifted at its end; one still running comes in as a lasting warning.
A player has at most one active ban and one active mute. An active ban or mute that comes in while the player already has one (from AdminControl or from earlier in the same import) is kept as history, ended by the console at the import, so one unban is always enough.