Startup settings

Startup shows the command your server runs and the variables it reads. Some are fixed by your plan; the ones you can edit have a field. A change takes effect at the next start.

Common variables

Server	Variable	What it does
Minecraft	MINECRAFT_VERSION	the Paper version; latest by default
Minecraft	SERVER_JARFILE	the jar to run; server.jar
Node app, bot	MAIN_FILE	the file to start; index.js by default; .ts files run with ts-node
Node app, bot	NODE_ARGS	arguments passed to your app (after the start file)
Node app, bot	NODE_PACKAGES / UNNODE_PACKAGES	npm packages to install / remove at start, space separated
Node app, bot	GIT_ADDRESS, BRANCH, USERNAME, ACCESS_TOKEN	deploy from a Git repository — see Node apps
Node app, bot	USER_UPLOAD	1 (the default): you upload the files yourself; 0: install from Git
Node app, bot	AUTO_UPDATE	1: git pull on every start
TeamSpeak	TS_VERSION	the TeamSpeak server version; latest by default

The descriptions next to each field in the panel say what it accepts.

What the Node runtime does at start

For Node apps and bots, every start:

1. pulls from Git, if the folder is a Git checkout and AUTO_UPDATE is 1;
2. installs NODE_PACKAGES and removes UNNODE_PACKAGES;
3. runs npm install if there’s a package.json;
4. prints Fleeq runtime ready — the panel switches to Running here;
5. starts MAIN_FILE.