Plugins
Servers → Plugins (/p/<projectId>/servers/plugins)
Why this page exists
This page shows what is actually installed on each game server, as reported by PlayerAtlas. Use it to audit mod and plugin lists, catch mismatches between machines (one server on an old WorldEdit, another on the latest), and spot outdated PlayerAtlas before players hit bugs. It supports support triage (“which server is missing the fix?”) and change control after updates.
How to use it
Choose a server from the dropdown. Use the URL
?server=<id>if you share a link with your team so it opens the right box.Search by plugin name, description, or author when the list is long.
Switch to the outdated filter when you want to focus on plugins whose version string looks older than the newest seen in your project (helps find stragglers).
For PlayerAtlas itself, compare the shown version to the latest hint in the UI when present, then grab the right JAR from Download Plugins and follow Plugin Installation.
What to do with the insights
Same plugin, different versions on two servers: expect different behavior or bugs; align versions after a test.
Missing plugin on one server: features that depend on it will fail only there; fix deploys or sync your build pipeline.
Outdated PlayerAtlas: update for fixes, metrics, and security; this page is the fastest way to see who is behind.
If the list is empty
The server must send its plugin inventory at least once (typically when PlayerAtlas connects). If nothing appears, confirm PlayerAtlas is running and the server has checked in.
Not the developer API
This screen is inventory on your servers. For embedding custom events in your own plugin JAR, use Using Java API (Maven playeratlas-api), not this page.
Last updated