Licences and servers
How your Scala licence counts the IP addresses of running servers, the default limits, and how to request an IP reset from your dashboard.
Your licence
Your store account has one licence. Every product you buy is added to it, and every loader you download from Downloads is tied to it. Licences in your dashboard shows what it includes.
A licence belongs to the account that bought it. Sharing a licence or a loader is against the terms of service.
How servers are counted
Your licence counts IP addresses, not installs. Every server, container or pod on the same IP address shares one slot.
There are two limits:
| Limit | Default | What counts |
|---|---|---|
| Licence | 10 IP addresses | The different IP addresses of all your running servers. |
| Each product | 3 IP addresses | The different IP addresses of running servers that load that product. |
These are the minimums. Some purchases raise them, and each owned product in your dashboard shows its own limit.
Only running servers count. When a server stops, its IP address stops counting, at the latest about five minutes later.
When a server would add an IP address over a limit, its products don't start and the console shows your license has reached its server limit, or Aegis is busy; try again in a minute.
See your usage
Servers in your dashboard shows:
- how many IP addresses your licence is using, out of its limit
- the same for each product
- each IP address with its servers, when they were first activated and when they were last seen
A server appears there after it first starts with your loader.
Request a reset
When the licence or a product is at its limit, a Request reset button appears next to it on the Servers page. Staff review each request.
If staff approve a reset, servers in that scope stop and must activate again:
- a licence reset covers every activated server on the licence
- a product reset covers the running servers that load that product
To bring a stopped server back, delete installation. in its Aegis folder and restart it with your newest Aegis.jar.
Activations
The first time a server starts with your loader, Aegis activates it and saves installation. in the Aegis folder (.aegis/ on standalone). Keep this file when you update, move or rebuild the server.
If the file is lost, the server activates again as a new installation. A licence holds up to 100 active installations. In containers and pods, keep the Aegis folder on persistent storage so a restart doesn't activate a new installation each time.