Oops... looks like the spiders padded through here
Add products to your cart and remove them from here Lets buy🪪 Licensing
On this page, you will find everything you need to know about activating your license and what to do when the validation fails.
#Your License Key
Every jar downloaded from our website is stamped with the license of the account that downloaded it, so in almost every case there is nothing for you to fill in. The key lives in config.yml under product-license.
product-license: 'your-license-key'
If you ever need to set it by hand, the key is on your account page on phoenixplugins.com. Paste it exactly as it appears, save the file and restart the server.
Only the lobby servers validate. The same jar on BungeeCord or Velocity has no product-license option and never contacts our servers, so there is nothing to activate on the proxy side.
#What Happens on Startup
On every start the plugin prints Validating license... and contacts our servers. Once the check passes you will see:
Great news! Your license is valid and active.
Plugin loaded successfully!
The same check is renewed periodically while the server runs, so a license that is revoked mid-session is noticed without a restart.
The server needs outbound internet access to phoenixplugins.com. A permanently offline machine cannot run the plugin.
#When Validation Fails
A failed validation does not shut the server down. The jar stays enabled, but the plugin never finishes loading: none of the modules, NPCs, holograms or hotbar items are registered, and a protection listener takes over instead. While it is active:
- Breaking, placing and damaging blocks is cancelled for everyone, so an unprotected lobby cannot be griefed while the plugin is down.
- /phoenixlobby, /spawn, /setspawn, /servers and /lobbies are blocked, and any player who runs one is told why.
Fix the cause and restart to restore the plugin.
If the license stops validating while the server is already running, the plugin unloads itself at the next renewal check and behaves the same way from there.
#"It appears that it does not exist for this product"
The key was not recognised for PhoenixLobby. Check for a typo, a stray space or a newline in product-license, and make sure the key belongs to this plugin rather than another one of ours.
#"Maximum concurrent sessions allowed reached"
The same license is already active on more servers than your plan allows. This is the usual one to hit when you run Multiple Lobbies, since every lobby server counts as its own session — the proxy does not, as it never validates.
Stop the extra instances and restart. If you have a genuine reason to run more sessions at once, contact us on Discord and we can raise the limit for your account.
A server that crashes without shutting down cleanly can leave a session registered for a short while. If you are certain nothing else is running, wait a few minutes and start again before contacting us.
#Grace Period
If our servers cannot be reached at all — your host blocks the connection, or we are down for maintenance — the plugin does not shut you out. A grace period is activated and the console tells you how long is left:
Oh no! Apparently there was an error contacting our server.
But don't worry, the grace period has been activated.
Grace period will expire in 23h 41m, so contact us before that happens!
Everything keeps working normally until the grace period expires. If you see this message and your server does have internet access, check your firewall before contacting us.
#Version Notices
The same check tells the plugin which version is current, so the console reports whether a newer build is available. Players holding phoenixlobby.admin are also told on join, which can be turned off with notify-if-new-version in config.yml.