Almost everything about how your server runs — short of the files themselves — lives on the Settings page, split across six tabs. Here's what each one holds, and which parts need a premium plan. Open it from your server menu.
| Tab | What lives there | Plan |
|---|---|---|
| General | Server name and icon, crash notifications, offline MOTD, Discord webhook | All plans |
| Startup | Startup command, stop command, done message, Docker image | All plans; premium to edit the command |
| Crash Detection | Auto-restart and health monitoring after a crash | Premium only |
| Environment | Variables, timezone, Java version | Every plan |
| Operations | Upgrade, auto-stop, transfer, clone, switch application | All plans |
| Danger | Reinstall server, delete server | All plans |
General
Your server's name and identity, plus how it keeps you in the loop. All plans:
- Server name and icon — what the server is called across the panel.
- Crash notifications — get an email when this server crashes. You pick per server: Use global setting (follow your account default), Always notify me, or Never. The global default emails you whenever any of your servers crash, capped at five emails per server per hour so a crash loop can't flood your inbox.
- Discord webhook — paste a Discord webhook URL and this server posts events straight to that channel: player joined or left, server online or offline, timer started / warning / expired, shutdown scheduled or cancelled, and server shutdown. Tick the events you care about and use the Test button to confirm it works. (This is the server's own webhook; the separate Schedules webhook fires on schedule events instead.)
- Offline MOTD — for a free Minecraft server on a Falix subdomain, a custom message players see when they ping your address while the server is asleep, with color codes, an icon, and a kick message.
Startup
How your server launches. The startup command itself is editable on premium; on the free plan you can see it but not change it — and you rarely need to, because the pieces you'd tweak live in variables (see the Environment tab). Everyone can set the stop command, the done message the panel watches for to mark the server online, and — when the application offers alternatives — pick a Docker image.
Crash Detection
Premium's automatic babysitter: settings for auto-restart after a crash and ongoing health monitoring, so a server that falls over comes back on its own. This tab is premium-only.
Environment
Your application's variables — the Main file, requirements file, tokens and everything else your app reads — editable on every plan. This is also where you set the server timezone and, on Java servers, pick a Java version (with a built-in guide to the Standard, OpenJ9 and GraalVM flavours).
💡 Tip: Not sure what a variable like Main file means for your language? Your language guide explains it — for example Node.js or Python. See also Environment variables & secrets.
Operations
The big moves: upgrade your resources, set the server to auto-stop when it's been inactive, transfer it to another node, clone it into a brand-new server, or switch application to run something else entirely. That last one reinstalls the server and wipes its files — the panel warns you first.
Danger
Exactly what it says. Reinstall server can replace files with fresh copies, and Delete server is final — there's no undo. Neither is something you do casually.
⚠️ Heads up: Take a backup before either, and read the confirmation prompts rather than clicking through them.
Most days you'll touch General and Environment and leave the rest alone — but it's worth knowing where the powerful switches are before you need them. Next: Backups, to make anything here safely reversible.