Updating
On this page2 sections
- Download the new
AdvancedNametags-<version>.jarand read its changelog. - Replace the old jar in
plugins/(keep only one AdvancedNametags jar there). - Restart the server. Paper does not support
/reloador plugin managers for any plugin, and packet-based plugins are the first to break with them.
What happens to your files:
| File | On update |
|---|---|
config.yml | New options are added with their explanation; none of your values change. The previous file is kept as config.yml.old. The console lists what was added. |
nametags.yml, templates/, badges.yml, animations.yml | Never touched. New bundled templates or badges are not added to an existing install (they would change the nametags of your players); copy them from the jar or the guide if you want them. |
lang/<language>.yml | Messages you edited are kept. Messages you never changed are updated to the new version's text (the previous file is kept as <language>.yml.old, and the console says how many). Messages added in the new version show the bundled text until you add them. |
data/ | Player customisations and the badge texture cache, kept as they are. |
A version that needs manual changes is always a new major version (2.0.0) and its changelog says exactly what to change.
Reloading
/nametag reload re-reads every file. If one has a YAML syntax error (a missing quote, a tab, a
wrong indentation), nothing changes: the working configuration stays active and the error is
shown with its file, line and column. Other problems (an unknown motion, a bad colour) only skip
that option and are listed after the reload.
Moving to MySQL/MariaDB
Set storage.type: mysql and the connection in config.yml, then restart (the storage cannot
change on a reload). Then /nametag import yaml copies the customisations stored in
data/players/ into the database (it shows how many first; the YAML files are kept). Details in
MySQL and MariaDB.
Coming from UnlimitedNametags instead? See migrating.