How to change startup settings and variables on Schokr

Your server's Startup settings control how it boots: the startup command, the software version and template variables such as the main file for a bot or the jar file for Minecraft. Change them, then restart the server.

What you will find in Startup#

• Startup command: the command run when the server starts. It is built from the template and uses variables.
• Variables: settings defined by the template. Each one has a description explaining what it does. Some are editable, some are read-only.
• Runtime image: some templates let you pick between versions of the runtime, such as different Java, Node.js or Python versions.

How variables work#

The startup command contains placeholders that are filled in from variables. For example, a Minecraft template's command looks roughly like this:

java -Xms128M -Xmx{{SERVER_MEMORY}}M -jar {{SERVER_JARFILE}}

SERVER_MEMORY comes from your server's memory limit, and SERVER_JARFILE is a variable you can edit. Change the variable and the command changes with it.

Common changes#

Change the Minecraft or software version

Many templates have a version variable. Set it to the version you want, save, then reinstall or restart as the variable's description says. Check that your plugins or mods support the new version first, and take a snapshot before changing versions on an existing world.

Set the main file for a bot or app

Node.js, Bun and Python templates have a variable for the file to run, for example index.js, src/index.ts or main.py. Point it at your entry file, relative to the server's root folder.

Install dependencies on start

Runtime templates usually install dependencies from package.json or requirements.txt on startup, and may offer variables for extra packages. Read each variable's description to see what your template supports.

Choose a runtime version

If your code needs a newer Node.js, Python or Java version, switch the runtime image (if your template offers several), then restart. For example, recent Minecraft versions need a recent Java version.

Environment variables and secrets#

Template variables are passed to your server as environment variables. Bots often read their own settings too:

const token = process.env.DISCORD_TOKEN

import os
token = os.environ["DISCORD_TOKEN"]

If your template has no variable for your setting, put it in a .env file in the server's root folder and load it with a library such as dotenv (Node.js) or python-dotenv (Python). Bun loads .env files automatically.

Keep tokens secret. Anyone with Startup or file access can read them, so limit those permissions in your team.

After changing settings#

1. Save your changes.
2. Restart the server.
3. Watch the console for errors. A typo in a file name is the most common reason a server will not start after a change.

Permissions#

Startup access is a separate team permission. Most helpers do not need it. See team roles and permissions.