Stratum FAQ
Install problems, features that seem to do nothing, billing, crashes, player statistics and other questions about Stratum.
Buying and licence
$25 on BuiltByBit. You get both packages (stratum and stratum-pages) and the install notes.
No. Stratum is an extension for Pterodactyl 2, which brought the extension system. Pterodactyl 1 and forks such as Pelican are not supported.
No. Billing, crash detection, tickets, roles, the Discord bot, splits, expiry and almost everything else work with any egg. Player statistics support Steam/Source games, FiveM and SA-MP too. Only the Minecraft tools are Minecraft-only, and they hide on other servers.
Yes. Install stratum-pages as well, and the Stratum pages (tickets, billing, crashes and the rest) keep working under any theme. The Stratum theme only changes the look.
Install and update
Run php artisan p:extension:doctor stratum-1.0.0.pteroext in the panel folder. It tells you whether the manifest, the panel version or the build is the problem. Make sure the panel is on Pterodactyl 2 and PHP 8.3 or newer.
No. Install the new files with --replace (or confirm the replace in the panel). Settings, tickets, invoices, statistics and crash records stay. New tables are added on the way.
Check that both packages are installed and enabled: php artisan p:extension:list. Then pick Stratum as the theme. Most features are off at first; turn them on under Stratum → System → Features.
Features
These run in the background through the panel's queue worker and cron job. Open Stratum → System → Status: if the scheduler or the queue is marked as stopped, start them again (they are part of every Pterodactyl install). Also check that the feature itself is turned on.
Look at the crash on the server's Crashes page. It says why:
- Needs a fix: the cause is one a restart cannot fix, such as an EULA that was not accepted or a wrong Java version. Fix it and start the server.
- Crash loop: it crashed too often in a row. Start it once by hand and the count starts over.
- Not restarted: auto-restart is off for that server, by the owner or by an admin.
Under Servers → Player statistics → Games (eggs), check the detected protocol for its egg. Set it by hand if it is empty, and set the query port if the game answers on another port. Test a server shows the exact error. Behind NAT, set Address to ask to Node.
The normal server list ping only sends a sample of up to 12 names. Set enable-query=true in server.properties and keep Full player list over Query on. Then every name is known.
Upgrades need a working Billing connection, the feature turned on, and at least one product for that server's egg. A user who is not linked to a billing account sees a note to sign in to the billing area once with the same email.
The order shows Failed with the reason, often a node without enough room. Fix that and press Apply on the order under Billing → Upgrades → Orders.
The bot runs on the panel server and needs Node.js there. Check the token and that the bot was invited to your Discord server. The Discord page shows whether the bot is online; the panel starts it again within a minute after a crash.
Send a test email from Communication → Email. If it fails, the error comes from the provider (wrong key, sender domain not verified). If it arrives in spam, set up SPF and DKIM for the sender domain at your provider.
Staff
Their role is missing the permission. Open the role under Users & Security → Roles; the Permissions page lists what each one allows. Staff can only give permissions they have themselves.
That is Staff requests. The owner approves on the server's Staff Requests page. Give access.bypass to staff who may work on any server without asking.
Suggestions
Still stuck? Follow the Stratum steps on FAQ and open a ticket on St3ix Support.