Plugin Installation
Install the PlayerAtlas build for your platform. Download the JAR from the dashboard (Download Plugins), then follow the section for your server software.
Hytale
Copy the PlayerAtlas Hytale
.jarinto your Hytale server’smods/folder (alongside other mods).Start or restart the server. Plugin data (including
config.yml) lives undermods/PlayerAtlas_Analytics/.If you used older metrics builds, existing data may be picked up automatically from legacy folders (for example
HytaleMetricsor paths underGM_HytaleMetrics). When in doubt, check the server log for migration messages.
After you change config.yml, run /playeratlas reload or restart the server.
Paper / Spigot / Purpur (and other Bukkit forks)
Put the PlayerAtlas
.jarin theplugins/directory.Restart the server (or load the plugin). The plugin data folder is
plugins/PlayerAtlas/, and configuration lives inplugins/PlayerAtlas/config.yml.If you still have data under the old
mcStats-Analyticsfolder andplugins/PlayerAtlas/config.ymldoes not exist yet, the plugin can migrateconfig.ymland related files intoplugins/PlayerAtlas/automatically.
Reload configuration with /playeratlas reload (permission playeratlas.reload, default: operators).
Velocity (ingress companion only)
The Velocity JAR is not a full PlayerAtlas install. It is an ingress companion: it captures how players connect to your proxy (virtual host, IP, session id) and forwards that context to backend servers over the plugin channel so the backend PlayerAtlas plugin can attribute joins correctly.
No
config.ymlon the proxy. No API key on Velocity. Nothing to edit for analytics settings there.Drop the JAR into Velocity’s
plugins/folder and restart the proxy.Run the full PlayerAtlas plugin on each backend Paper/Spigot (or other supported) server that should send analytics. The companion and backend plugins are meant to work together.
For API keys, chat logging, and other options, configure PlayerAtlas on the game servers (Configure our Plugin).
Last updated