Question 1

How do I set up a DarkRP server for the first time?

Accepted Answer

When your server first starts it will be running the default GMod sandbox gamemode. Switching to DarkRP and setting it up end to end happens across three panel pages: Config Editor, Addon Manager, and Admin Ranks. This guide walks through each step with the actual panel screens. ![File Manager for a DarkRP server, showing the garrysmod folder structure and Quick Configs shortcuts for server.cfg, jobs.lua, and the DarkRP config](/assets/help/game-setup-guides/darkrp-01-file-manager.webp "File Manager, with one-click shortcuts to the configs used below") The quickest way to switch to DarkRP is the Config Editor: open Config Editor in the sidebar (under GMod Tools), select the Server Config tab, and click the DarkRP preset. It writes the DarkRP-appropriate gamemode setting straight to garrysmod/cfg/server.cfg. Restart the server and DarkRP loads on the next start. If you would rather edit the file directly, open File Manager, edit garrysmod/cfg/server.cfg by hand, add the line gamemode darkrp, save, and restart; both routes write to the same file. ![The Config Editor Server Config tab, showing a Server.cfg Builder with a DarkRP preset button and fields for server name, max players, and password](/assets/help/game-setup-guides/darkrp-02-server-config-builder.webp "Server Config tab of the Config Editor, with the DarkRP preset selected") Custom jobs live in garrysmod/addons/darkrpmodification/lua/darkrp_customthings/jobs.lua. The file ships with example jobs you can edit or replace. The Config Editor has a dedicated DarkRP Jobs tab: point it at that jobs.lua path, load the file, and add or edit jobs (name, description, player model, salary, team) through the form instead of hand-editing Lua. Saving writes the file back; restart to apply. You can still edit the file directly in File Manager if you prefer. ![The Config Editor DarkRP Jobs tab, showing the jobs.lua path field and an Add Job button](/assets/help/game-setup-guides/darkrp-03-jobs-editor.webp "DarkRP Jobs tab, pointed at darkrp_customthings/jobs.lua") For admin management, most DarkRP servers use either ULX or SAM. Install ULX by adding the ulib and ulx addons from the Addon Manager (GMod Tools section of the sidebar) with a single click, or upload them manually via File Manager. SAM is a paid addon sold on GmodStore, not something the Addon Manager can fetch automatically; if you buy it, upload the sam folder via File Manager and configure ranks through its in-game interface (F1 or type sam in console). ![The Addon Manager showing the DarkRP gamemode and DarkRP Modification addons with one-click Install buttons](/assets/help/game-setup-guides/darkrp-04-addon-manager.webp "Addon Manager - install DarkRP, ULib, and ULX without leaving the panel") Once ULX is installed, the Admin Ranks page (under Configuration in the sidebar) reads and writes your ULib rank data directly, so there is no need to touch groups.txt or users.txt by hand. The Ranks tab lists every configured rank with its inherit chain, member count, and permission count. Assign yourself superadmin by entering your 64-bit SteamID on the Users tab; changes reload ULX live, with no restart needed. ![The Admin Ranks page showing four ULX ranks: superadmin, admin, moderator, and vip, with their inherit chain and permission counts](/assets/help/game-setup-guides/darkrp-05-admin-ranks.webp "Admin Ranks - superadmin, admin, moderator, and vip, each inheriting from the rank below") After installing any addons from third-party sources, run the Backdoor Scanner from the Monitoring section of the sidebar. It scans your Lua files in the browser for known malicious patterns, things like hidden remote access code that sometimes ships inside free addon packs, and flags anything suspicious before the server opens to players. ![The Backdoor Scanner page, ready to scan the demo DarkRP server for malicious Lua patterns](/assets/help/game-setup-guides/darkrp-06-backdoor-scanner.webp "Backdoor Scanner - run it after every batch of new addon installs") Once the admin mod is set up, admins can kick, ban, and manage players in-game. Use the Admin Ranks page any time the rank hierarchy needs adjusting; it reloads live with no restart.

Question 2

How do I set up a Garry's Mod TTT (Trouble in Terrorist Town) server?

Accepted Answer

Open the File Manager and edit garrysmod/cfg/server.cfg. Add gamemode terrortown and set sv_defaultgamemode "terrortown". Restart the server. TTT will load on the next start. For admin management, install ULX and ULib via the Addon Manager or by uploading the addon folders to garrysmod/addons/. With ULX running, assign yourself superadmin using your 64-bit SteamID via the Admin Ranks page in the panel (GMod Tools section of the sidebar). The main TTT config file is garrysmod/gamemodes/terrortown/gamemode/shared.lua, but editing the gamemode files directly will be overwritten on updates. Instead, create garrysmod/lua/autorun/server/ttt_config.lua for your overrides. Common settings: GetRoundLimit() for round count, GetRoundTime() for round length, GetTraitorPct() to control traitor ratio, and GetDetectivePct() for detective ratio. For ULX karma management, TTT integrates with ULX's karma system automatically when both are installed. Players who RDM lose karma; low-karma players are autokicked. Set ttt_karma_low_autokick and ttt_karma_kick in your config to tune the thresholds. Map rotation is handled by garrysmod/cfg/mapcycle.txt. Add one map name per line. The server rotates through the list when a round ends or the map vote completes. Popular TTT maps start with ttt_ in the Workshop; add them via the Workshop Addon Manager (Workshop Search in the sidebar).

Question 3

How do I set up a Garry's Mod PropHunt server?

Accepted Answer

PropHunt is a custom gamemode. First, download the PropHunt gamemode from GitHub or the Workshop and upload it to garrysmod/gamemodes/prophunt/ via File Manager. Then edit garrysmod/cfg/server.cfg and add gamemode prophunt and sv_defaultgamemode "prophunt". Restart the server. PropHunt requires props available in the map you are running. Use maps that ship with prop spawns; search for ph_ maps on the Steam Workshop. Add them via the Workshop Addon Manager (Workshop Search in the sidebar) and update your mapcycle.txt. The gamemode configuration file is typically at garrysmod/gamemodes/prophunt/gamemode/config.lua. Key settings: round time, team sizes, and which player models hunters use. Edit this file in File Manager and restart to apply changes. For admin management, install ULX and ULib via the Addon Manager and assign yourself superadmin via the Admin Ranks page. PropHunt uses standard ULX commands for admin actions.

Question 4

How do I set up a Garry's Mod sandbox server?

Accepted Answer

Garry's Mod starts in sandbox mode by default, so no gamemode change is needed. The key configuration is in garrysmod/cfg/server.cfg. Essential settings for a sandbox server: sv_downloadurl "" (set this if you use a FastDL or Workshop content server), sv_allowupload 0 and sv_allowdownload 1 to control client file transfers, sbox_maxprops 100 to limit how many props each player can spawn (default is 200; lower it on high-player-count servers to reduce lag), and sbox_maxragdolls 5 and sbox_maxnpcs 10 to cap spawnable entities. For Workshop content, open the Workshop Addon Manager (Workshop Search in the sidebar), switch to the Collection tab, and paste in a collection ID. Players download required content automatically on connect. For admin management, install ULX and ULib via Addon Manager, then use the Admin Ranks page to assign superadmin to your SteamID. The standard ULX rank structure works well for sandbox: user (base), moderator (freeze, remove props, kick), admin (ban, change maps), superadmin (full access). Run the Backdoor Scanner after adding any third-party addons. Free sandbox addons on the Workshop sometimes contain hidden remote access code.

Question 5

How do I set up a Minecraft server with plugins?

Accepted Answer

Before your server will start for the first time you need to accept the Minecraft EULA. Open the File Manager, find eula.txt in the server root, change eula=false to eula=true, and save. Then start the server. The Version Manager page lets you choose and switch server software without manual downloads. For a vanilla experience choose Vanilla. For plugins, choose Paper; it is the best-performing Bukkit-compatible option and supports the widest range of plugins. Spigot is an alternative if a specific plugin requires it. For mods, choose Forge or Fabric depending on which mod ecosystem your mods target. Always back up your world before switching software types, especially between modded and vanilla. With Paper or Spigot running, use the Plugin Manager page to search for and install plugins. The panel places the JAR in the correct plugins/ folder automatically. Restart the server after installing for the plugin to load. For plugins not in the Plugin Manager, download the JAR from a trusted source and upload it to plugins/ via File Manager. The World Manager shows all worlds on your server. You can upload a custom world, download a backup, or delete worlds you no longer need. For multi-world setups, all world folders are accessible from this page. Use the Server Properties page for core settings like max-players, gamemode, difficulty, and view-distance. Use the Player Manager page for whitelist, ops, bans, and banned IPs. Changes through Player Manager take effect on a running server immediately without a restart.

Question 6

How do I install a Minecraft modpack (CurseForge or Modrinth)?

Accepted Answer

Modpacks come in two flavours: server packs (pre-configured, ready to run) and client packs (needs conversion). Always download the server pack if one is available; it includes the correct Forge or Fabric version and all the required mods already configured. For a CurseForge server pack: download the server pack ZIP from the modpack's CurseForge page. Extract it and upload all the contents to your server root via File Manager. The pack includes a forge-<version>-installer.jar or similar; check the included README or start.sh to find the correct JAR filename, then update your server's start command on the Startup page to use that JAR. Most server packs also include a server.properties and eula.txt; accept the EULA in that file before starting. For a Modrinth pack: download the .mrpack file and use the mrpack-install tool (available from GitHub) to extract a server-ready directory, then upload the contents. RAM requirements: modpacks need significantly more RAM than vanilla. A medium modpack (100-200 mods) typically needs 4-6 GB. A large pack (300+ mods) may need 8 GB or more. Check the modpack's recommended server RAM on its CurseForge or Modrinth page and ensure your plan meets it. After uploading, start the server and watch the Console page. The first start is slow as Forge or Fabric loads all mods. Errors on first start are common; read the Console output carefully. "Missing dependency" errors mean a required mod was not included; download and upload it manually. "Incompatible mod set" errors mean two mods conflict; check the modpack's known issues page.

Question 7

How do I set up a Minecraft BungeeCord or Velocity proxy network?

Accepted Answer

A proxy network lets multiple Minecraft servers share a single player pool. Players connect to the proxy and are routed to individual backend servers (lobby, survival, minigames, etc.). BungeeCord and Velocity are the two main options; Velocity is newer and more performant, so use it for new setups. You need at least two servers on your Zeros Host account: one for the proxy and one or more backend servers. On each backend server (not the proxy): open server.properties and set online-mode=false. This is required for the proxy to handle authentication. Also open the Paper or Spigot config and enable BungeeCord mode: in spigot.yml set bungeecord: true, or in config/paper-global.yml under proxies.bungeecord set online-mode: true (for Velocity, use velocity: enabled: true and set the secret key instead). Restart backend servers after making these changes. On the proxy server: download BungeeCord.jar or Velocity.jar and upload it as your server JAR. Edit config.yml (BungeeCord) or velocity.toml (Velocity) to list your backend servers by their internal IP and port. For Zeros Host servers, use the panel-assigned IP and port for each backend. Set the forced_hosts and listeners sections to route the main connection correctly. Important: with online-mode=false on backend servers, they will accept connections from anyone who knows the address. Make sure backend server ports are not publicly advertised; only the proxy address should be given to players. Most firewall setups on VPS hosting handle this, but confirm with the panel's network settings.

Question 8

How do I set up a Terraria server?

Accepted Answer

When your server starts for the first time it generates a new world automatically. To configure it before players join, stop the server and edit serverconfig.txt in the server root via File Manager. Key settings: world (path to your .wld file), worldname (display name), maxplayers (default 8), port (default 7777), password (leave blank for public), and difficulty (0=classic, 1=expert, 2=master, 3=journey). To use an existing world, upload your .wld file to the Worlds/ folder via File Manager, then update the world path in serverconfig.txt to point to it. Restart the server after saving. For mods, you need tModLoader instead of vanilla Terraria - check the Startup tab for a variable to switch server type; the Version Manager page that handles this for Minecraft does not cover Terraria. Once running, mods are placed in tModLoader/Mods/ as .tmod files; download mods from the tModLoader browser in-game or from the tModLoader Workshop, then upload the .tmod files via File Manager. Restart after uploading new mods. To set yourself as an admin, use Terraria's standard in-game password: set password in serverconfig.txt, join the server, then run /password <password> in chat to authenticate as a host.

Question 9

How do I switch between vanilla Terraria and tModLoader?

Accepted Answer

Check the Startup tab for a server type or version variable to switch between the vanilla TerrariaServer binary and tModLoader - this is not on the Version Manager page, which only covers Minecraft. Before switching, back up your world files. World files (.wld) are compatible between vanilla and tModLoader for vanilla-generated content, but if you have tModLoader-specific blocks or items in a world, loading it on vanilla will cause those items to be replaced with empty space. If you are moving from tModLoader back to vanilla, this means content added by mods is lost.

Question 10

How do I install Terraria mods with tModLoader?

Accepted Answer

With tModLoader running, mods are placed in the tModLoader/Mods/ folder as .tmod files. Download mods from the tModLoader in-game mod browser or from the tModLoader GitHub releases page, then upload the .tmod files to tModLoader/Mods/ via File Manager. After uploading, the mods need to be enabled. Edit (or create) the file tModLoader/Mods/enabled.json and add the mod's internal name to the array. The internal name is the filename without the .tmod extension. Save and restart the server. For example, if you uploaded CalamityMod.tmod, add "CalamityMod" to enabled.json: ["CalamityMod", "AnotherMod"] Restart the server after editing. Check the Console page for any loading errors on startup.

Question 11

How do I configure my Terraria world (difficulty, size, seed)?

Accepted Answer

Terraria world settings are configured in serverconfig.txt in the server root. Key settings: world (path to your .wld file), worldname, autocreate (1=small, 2=medium, 3=large, used when creating a new world), difficulty (0=classic, 1=expert, 2=master, 3=journey), and seed (a specific world seed, or leave blank for random). To create a new world with specific settings: stop the server, update autocreate, difficulty, and seed in serverconfig.txt, delete or rename the existing .wld file so the server does not load it, and start the server. A new world is generated with the configured settings. To use an existing world file: upload the .wld file to the server via File Manager, update the world path in serverconfig.txt to point to it, and restart.

Question 12

How do I set up a Project Zomboid dedicated server?

Accepted Answer

When your Project Zomboid server starts for the first time it creates a server configuration file at .cache/Server/YourServerName.ini, where YourServerName is whatever you named your server - not a fixed filename. Stop the server before editing this file, as changes made while it is running will be overwritten on shutdown. Key settings in that .ini file: MaxPlayers (player cap), PVP (true/false), Public (whether it appears in the server browser), PublicName (server browser display name), PublicDescription, Password (blank for no password), SpawnRegion (starting town), and Mods / WorkshopItems (for mod lists). Set your admin password on the Startup page (the Admin Password field, masked by default - click the eye icon to reveal it) rather than editing AdminPassword= in that .ini file directly: the server discards a manually-edited line on every restart, so the change won't stick. To give your own account admin rights, use the Console page - not in-game chat, and without a leading slash: adduser YourUsername first, then setaccesslevel YourUsername admin. Names are case sensitive, and if you try setaccesslevel before adduser the server replies "use /adduser first" - ignore the slash in that message, the console still will not accept one. Our full Project Zomboid admin guide covers this in more detail if you get stuck. To add Steam Workshop mods, find the mod Workshop ID from the URL of its Steam Workshop page. Add the ID to WorkshopItems (semicolon-separated) and the mod ID to Mods in your server's .ini file. The mod ID is different from the Workshop ID; it is listed on the mod's Workshop page under its description. Restart the server after editing. Mods are downloaded and loaded on startup. Sandbox settings (loot abundance, zombie count, XP multipliers, day length) are in a separate file, .cache/Server/YourServerName_SandboxVars.lua - same naming pattern, after your server's own name. The easiest way to configure these is to host a local single-player game with your desired settings, find the generated SandboxVars.lua in your local Zomboid save, and upload it to replace the server's version.

Question 13

How do I update my Project Zomboid server, and what do Build 41 and Build 42 mean?

Accepted Answer

Project Zomboid currently has two versions in active use: Build 41, the long-running previous release, and Build 42, the newer release. Steam updates your desktop game to whichever branch your client is set to, and your server stays on whichever branch it was installed with, so the two can end up on different builds without either side doing anything wrong. When that happens, connecting shows the error "Client version does not match server version", followed by both version numbers. This message is not a sign anything is broken; it simply means your client and server disagree on which build to run, and the fix is to put them on the same one. The panel tells you which build your server is on without you having to work it out. If your server is behind the latest release, you will see an "Update available" notice on the Console page. We are currently improving how server updates are applied, so if an update does not appear to take effect, open a support ticket and we will sort it for you rather than leaving you to work around it. If your server is pinned to a non-default branch, the panel shows a badge next to the server name saying which branch, so you always know at a glance whether you are matched to the standard release or a beta. The Startup page has a field labelled "Steam Beta Branch [requires reinstall]" that controls which branch your server installs. Leave it blank. Blank means the current, default release, and it is what almost everyone wants; most people never need to touch this field at all. On a server you are setting up for the first time, blank and choosing the current release outright do the same thing. On a server that is already running, they do not: blank leaves your server on whatever branch it already has, it does not move it back to the current release. Only entering public explicitly moves an existing server onto the current release; blank alone will not do it, because blank means no branch was requested, not a request for the current one. This is worth knowing even if you never touch the field yourself, because it explains something that looks wrong but is not: a server stuck on an older build does not sort itself out just because this field looks empty. The dedicated server your panel runs is a separate Steam application from the game itself, not the same program, so its list of available branches is not guaranteed to match your desktop game's list. The field only accepts branch names Steam actually publishes for the server application, and typing anything else fails instantly with an error that gives no useful explanation, so an unfamiliar branch name is not a safe guess. To find the real, current list, check the Betas tab for the tool named "Project Zomboid Dedicated Server" in your own Steam library. Every branch listed there is a genuine option for your server. This list can change as branches are added or retired, so checking it directly is more reliable than any fixed list we could put here. ![The Startup page Steam Beta Branch field, labelled "requires reinstall", with a description explaining it accepts a Steam beta branch name such as b41multiplayer](/assets/help/game-setup-guides/pz-01-beta-branch-field.webp "Startup page - Steam Beta Branch field") Branch selection works reliably when you create a NEW server: pick the branch you want at setup and it installs correctly. Switching the branch of an existing server is something support can do for you: contact us with your server ID and the branch you want, and we'll handle it directly rather than have you use this field yourself. Reinstalling does not change your branch and cannot fix an invalid value in that field. A reinstall reinstalls whatever the field currently says, so if it holds a branch name that does not exist, reinstalling fails the same way every time, for the same reason. Correct the field first. Here is what actually happens when a server's branch changes, whether it's a new server being set up on a chosen branch or an existing one being moved by support: the server is reinstalled and its game files are replaced with the files for the new branch. If the server has a world made on a different build, that world will not load afterward. Nothing gets deleted; the new build's files genuinely cannot read a world made on the other build, and there is no tool that converts one into the other. Because of this, take a backup of your server before any branch switch, and confirm it actually completed before going ahead, not just that you started one. One thing worth knowing: a backup taken while your server was on a given build restores that build when you use it, not just the world files inside it. So a backup taken before switching branches is also your way back if you change your mind afterward. If your server has recently changed branch and then fails to start with errors that mention map or world data, that does not necessarily mean your world is damaged. Occasionally a branch change does not fully replace every game file, and older files can end up mixed in with the new ones. The errors point at map data because that is what breaks first, but the cause is the install itself, not your save. Restoring a backup will not fix this, since your world was never the problem, and you would likely see the same errors afterward. If this happens after a branch change, contact support rather than restoring a backup yourself. To change which branch your own Steam client (the game you play, not the server) uses, open Steam, right click Project Zomboid in your library, choose Properties, then the Betas tab, and select the branch that matches your server (or the option to opt out of all beta programs, if your server is on the default branch). If you are not sure which build your friends or players are on, ask them to check the same Betas tab. Everyone connecting to the same server needs to be on the same build.

Question 14

How do I configure Project Zomboid sandbox settings (loot, XP, PvP, zombies)?

Accepted Answer

Project Zomboid sandbox settings are stored in .cache/Server/servertest_SandboxVars.lua. Stop the server before editing this file; changes made while it is running are overwritten on shutdown. Open the file in File Manager. Key settings: ZombieCount (multiplier for zombie density), DayLength (how long an in-game day lasts), Loot (loot abundance, 1=rare, 4=abundant), XPMultiplier (experience gain rate), and PVP (true or false). The file contains every configurable option with its current value. Make your changes, save, and restart the server. The new settings take effect on the next world load. The easiest way to generate a starting config is to set up a local single-player game with your desired sandbox settings, find the generated SandboxVars.lua in your local Project Zomboid save folder, and upload it to replace the server version.

Question 15

How do I add or remove Steam Workshop mods on Project Zomboid, and why does a removed mod sometimes keep loading?

Accepted Answer

Project Zomboid mods are managed most easily through the Workshop Mods page in your server's sidebar. It reads and writes your server's mod list for you, so day-to-day changes do not need any file editing. ![The Workshop Mods page for a Project Zomboid server, showing the page header, a "server is running" notice, and the Installed Mods list](/assets/help/game-setup-guides/pz-02-workshop-mods-page.webp "Workshop Mods page") To add a mod, find it on the Steam Workshop and note two IDs: the Workshop ID (the number in the URL after ?id=) and the mod's internal Mod ID (listed on the mod's Workshop page under the description, usually in a line reading "Mod ID: xxx"). Check the mod's Workshop page loads normally before adding it - a mod that has been removed from Steam can stop your server starting, not just fail to load. Some mods list more than one Mod ID; add a separate entry for each one, using the same Workshop ID each time. On the Workshop Mods page, enter both IDs under Add Mod, click Add Mod, then click Save Changes. Restart your server for the mod to download and load. To remove a mod, click the trash icon next to it in the Installed Mods list, then click Save Changes; the removal is not written to your server's configuration until you click Save Changes, so don't skip that step. If you close the page or move to another tab before saving, the mod is still listed in your server's config and it will keep trying to load a mod that is effectively gone, which can show as a load error in the Console or stop the server starting cleanly. If a mod you removed still seems to be loading after you have saved and restarted, go back to the Workshop Mods page and confirm it is genuinely gone from the Installed Mods list. If it is gone there but the server still references it, check the WorkshopItems and Mods lines directly in File Manager (see below) for a leftover entry, remove it by hand, save, and restart again. If it keeps happening, contact support. If you prefer to edit the config directly, or need to bulk-edit a long mod list, the same data lives in File Manager at .cache/Server/<your server name>.ini (the default name is servertest unless you changed it), in the WorkshopItems (Workshop IDs) and Mods (Mod IDs) lines, both semicolon-separated and in the same order. Stop the server before hand-editing this file directly. If a mod fails to load after adding it, or your server won't start at all after adding one, check the Workshop ID is valid and still published on the Workshop first - a mod that has been removed from Steam can stop your server starting. If the ID checks out, the next most common cause is a missing dependency mod that also needs to be added.

Question 16

How do I run a map wipe on Project Zomboid?

Accepted Answer

A map wipe removes all map data (explored chunks, structures, loot, player bases) and restarts the world fresh. Player character data is stored separately and can be preserved if you want players to keep their characters. Stop the server. In File Manager, navigate to .cache/Saves/Multiplayer// (the default name is servertest unless you changed it; ignore any Zomboid folder at the server root, it is unused). Delete the map chunk files: these are the numbered folders and .map files inside this directory. Character data lives in a separate file, not inside that folder: .cache/db/.db. Leave this alone if you want characters to survive the wipe. If you also want to wipe characters, delete this file as well. Start the server. A new world generates fresh on the next run. Players who connect will spawn as if the server is brand new.

Question 17

How do backups and world saves work for a Project Zomboid server?

Accepted Answer

Project Zomboid stores its world and player data in a different location than you might expect if you have looked at a home install before: your server runs with a custom cache directory, so its save data sits under a .cache folder in your server root rather than directly alongside your other server files. Because of this, hunting through File Manager for the raw save files is more error-prone than it needs to be. Use the Backups page in your server's sidebar instead. It captures your full server state, including world data, in one step, without you needing to know exactly where every file lives. Create a manual backup before anything risky: reinstalling, wiping the map, or making bulk mod changes. Some server settings can reset to their defaults after a reinstall, so a fresh backup protects your world even if something else about the reinstall does not go as expected. ![The Backups page in the Zeros Host panel, showing storage usage and a Create Backup button](/assets/help/game-setup-guides/project-zomboid-backups-01-backups-page.webp "Backups page - one click captures your full server state, including world data") If you just want to check what world saves currently exist on your server without digging through File Manager, the Saves page in the sidebar lists them for you, with when each one was last touched. It is read-only for now (no rename or delete from that page yet), but it is the quickest way to confirm a save is actually there before you rely on it. ![The Saves page in the Zeros Host panel, listing world saves stored on the server](/assets/help/game-setup-guides/project-zomboid-backups-02-saves-page.webp "Saves page - a read-only list of world saves stored on your server") When restoring a backup, you do not have to restore everything: the restore screen has a "Restore specific files instead" option that lets you pick just the world/map or just player data (or hand-pick individual files) and leaves the rest of the server untouched. This is safer than a full restore when you only need to roll back one thing, since it cannot undo unrelated changes you have made since the backup was taken. If a backup ever shows a "Database corrupted" warning, that means one of its database files failed an integrity check when it was created; the backup itself still exists, but restoring it will bring that corruption back too, so treat it as a fallback rather than your first choice if you have a more recent, non-flagged backup available. Player character data is stored separately from map/world data. If you want to wipe the map while keeping everyone's characters, or the other way round, see the map wipe guide rather than deleting files by hand; deleting the wrong folder from a custom cache path is easy to get wrong. Schedule regular automatic backups from the Backups page rather than relying on manual ones alone. If you ever need to move your world to a different server or restore an older version, restoring from the Backups page keeps the file layout consistent, which manually copying files out of a .cache directory does not guarantee.

Question 18

How do I set up a Valheim dedicated server?

Accepted Answer

Your server's start command and core settings live on the Startup page: server name, world name, and password are set there as startup variables. Valheim requires a password of at least 5 characters; the server will not start without one. Decide on a world name before your first start, since this is the name Valheim uses for the save files it generates and changing it later starts a brand new world rather than renaming the existing one. The first start takes a few minutes longer than normal, since the server downloads the Valheim dedicated server files before it can generate the world. Watch the Console page for progress; a successful start ends with a line confirming the game server is listening for connections. Your server is public by default and appears in the in-game server browser under its configured name. If you would rather keep it private, set Public to 0 on the Startup page; a private server will not appear in the browser. Either way, friends can always join directly - give players your server's address and port from the Network page along with the password. World save files are written to .config/unity3d/IronGate/Valheim/worlds_local - note that is a hidden dotfile path, not the server root, so you will not find it by clicking around from the top level - as a .db and .fwl pair named after your world. Back these up regularly from the Backups page: a corrupted or lost world file cannot be recovered any other way.

Question 19

Can I install mods on a Valheim server (BepInEx)?

Accepted Answer

Not at the moment. Server-side mods are not supported on Zeros Host Valheim servers today, and uploading BepInEx to your server will not load it. Valheim mods load through BepInEx, which has to be injected before the game starts. On Linux that means launching the server through BepInEx's own start script, so it can set the loader up first. Our Valheim servers launch the game binary directly, and the start command itself is not editable from the panel - you can change startup variables such as server name, world name and password, but not the command that runs. So BepInEx files placed on the server are simply ignored, and nothing about them will appear in your Console. An earlier version of this guide described an upload procedure and told you to watch the Console for BepInEx loading each plugin. That procedure could not work on our servers, and those log lines were never going to appear. If you tried it and saw nothing, you did not do it wrong. What does still work is client-side-only mods. A mod that changes your own interface, camera or visuals, and does not change how the game behaves, runs entirely on your machine and needs nothing from the server. Mods that change gameplay - ValheimPlus, content mods, balance and difficulty mods - must be loaded by the server as well as every player, so they cannot be used on a Zeros Host Valheim server for now. If server-side mods matter to you, tell us through the contact form or on Discord. Supporting BepInEx is a change to how the server is started rather than a setting we can switch on, so it is a piece of work rather than a toggle, and demand is genuinely how we decide what to build next.

Question 20

How do I manage, back up, or replace my Valheim world?

Accepted Answer

Your active world is a matched pair of files in .config/unity3d/IronGate/Valheim/worlds_local - note that is a hidden dotfile path, not the server root, so you will not find it by clicking around from the top level. In there you will see: .db (the world data) and .fwl (metadata, including whether it's a custom seed). Both files share the name set in your Startup page world name variable; the server will not find your world if the files and the variable disagree. To back up your world, use the Backups page rather than only relying on the raw files; scheduled backups protect you if a crash or bad shutdown corrupts a save mid-write. You can also download the .db/.fwl pair directly via File Manager for an off-panel copy. To move an existing single-player or another host's world onto your server, stop the server, upload that world's .db and .fwl files to the same .config/unity3d/IronGate/Valheim/worlds_local folder via File Manager, rename them to match your Startup page world name exactly, and start the server. To start completely fresh instead, stop the server, delete or rename the existing .db/.fwl pair (back them up first if there is any chance you will want them back), and start; Valheim generates a new world on that next boot using the world name and any seed you configured. A world seed can only be set at creation. If you want a specific seed, you need to set it before that world's files exist, either by wiping first or by choosing the seed on your very first start.

Question 21

How do I invite friends to my Valheim server?

Accepted Answer

The most direct route is "Join IP" from Valheim's main menu. Enter your server's address and port, which you'll find on the Network page in the panel, then the password when prompted. This works whether your server is public or private. Your server is public by default, so it also appears in the in-game "Servers" browser under its configured name and friends can search for it there instead. If you would rather it not be listed, set Public to 0 on the Startup page; a private server will not appear in the browser. To give trusted players admin commands in-game (spawning items, flying, etc.), add their Steam64 ID to adminlist.txt, one ID per line, then restart the server. That file is at .config/unity3d/IronGate/Valheim/adminlist.txt - the same hidden dotfile folder your world saves live in (one level up from worlds_local), not the server root, so you will not find it by clicking around from the top level. The permittedlist.txt (allow-list for a private server) and bannedlist.txt sit alongside it. If a file is not there yet, start the server once and Valheim creates it. Their Steam64 ID is found through any Steam ID lookup site using their profile URL.

Question 22

How do I set up an Unturned server?

Accepted Answer

Your server installs and starts on its own after you order it, so there is nothing to run yourself. The first start takes a few minutes longer than later ones, because the server downloads the Unturned game files from Steam before it can load a map. Watch the Console page: the server is fully up when it prints Loading level: 100%. The settings you are most likely to change live on the Startup page, not in a config file. Server Name is what players see in the server browser and in the Connect Directly menu, and it is limited to 50 characters. Map chooses which official map loads, and defaults to PEI. Both take effect on the next restart. Auto Update is on by default and runs a Steam update check on every boot. That keeps you current with the game, which matters in Unturned because players on a newer client cannot join an older server. If you would rather your server booted faster and stayed on a pinned build, set it to 0. Additional Arguments passes extra launch flags through to the server exactly as you type them. Leave it blank for a working public server. The two flags most people want are -GSLT to appear in the Steam server list and -Password to make the server private. These are deliberately not separate fields: an empty value would be passed through as a bare flag, swallow the next argument, and crash the server on boot. Some settings are fixed and not editable, including the internal server folder name and the Steam App ID. That is on purpose; changing the folder name would start a brand new world and orphan your existing one.

Question 23

How do my friends join my Unturned server?

Accepted Answer

Unturned gives every server a numeric Server Code, and it is the easiest way to get people in. When your server starts, the Console prints a line reading Server Code: followed by a note that your friends can enter that code in the Connect Directly menu to join without port forwarding. Copy the digits and send them over. Your friends open Unturned, choose Play, then Connect Directly, and enter the code. There is no address to type, no port to explain, and nothing for them to forward. You can also join by address if you prefer. Your server address and port are on the Network page in the panel. Give players both, and they connect the way they would to any other dedicated server. By default your server will not appear in the public Steam server list. Appearing there needs a Game Server Login Token, which you add as -GSLT under Additional Arguments on the Startup page. You generate that token yourself from Steam's Game Server Account Management page using App ID 1110390. This is optional: players can always join by Server Code or by address without it. If you want the server private, add -Password to Additional Arguments and share the password alongside the code.

Question 24

How do I change the map on my Unturned server?

Accepted Answer

Map is a setting on the Startup page, not a config file you have to go and find. Pick the map you want, restart the server, and it loads on the next boot. The maps that ship with the game are PEI (the default), Washington, Yukon, Russia, Germany, Alpha Valley, Monolith, Destruction, Tutorial and Paintball_Arena_0. The important thing to understand is that changing the map starts a fresh world on that map. It does not carry your existing base and players across. Your old world is not deleted, though: it stays on disk under the server's Servers folder, so switching back to the previous map returns you to the world you left there. That makes it safe to try a map and go back, but it does mean each map keeps its own separate save. Because of that, take a backup before you switch if the current world matters to you. The Backups page captures the whole server including every map's saved world, so you have a copy you can restore from regardless of which map you end up on.

Question 25

How do I install Rocket plugins on my Unturned server?

Accepted Answer

Rocket is the plugin framework most of the Unturned community builds on, and it is already wired into your server rather than something you install first. When the server boots, the Console prints the Rocket version it loaded and registers its commands straight away, so admin tools such as /rkick, /rwho, /admins, /airdrop and /ban work from the console without any setup. To add a plugin, stop the server, upload the plugin's .dll into the Rocket/Plugins folder using the File Manager, and start the server again. Rocket picks up plugins on startup, so a restart is what makes a new plugin load. Watch the Console as it comes back up: Rocket names each plugin it loads, so if yours is not in that list it has not loaded, and that is the place to start looking. Most plugins generate their own configuration file inside Rocket/Plugins the first time they run. So the usual order is upload, restart once to let the plugin create its config, stop, edit the config, then start again. A plugin written for a different Rocket version, or for a much older build of Unturned, may fail to load or throw errors in the console. Check the plugin's own page for which version it targets. If a plugin breaks your server's startup, remove its .dll from Rocket/Plugins and restart to get back to a working server.

Question 26

How do I deploy a discord.js bot?

Accepted Answer

Create your bot application at discord.com/developers/applications and add it to your Discord server with the appropriate permissions. Copy the bot token from the Bot page; you will need it as an environment variable. In the panel, go to the Startup page for your server and add an environment variable named TOKEN (or whatever your code reads) with your bot token as the value. Never put the token directly in your code files; environment variables keep it out of version control and out of your file uploads. Upload your bot files via File Manager. Your project needs a package.json with a main or start field pointing to your entry file. The panel runs npm install on first start to install your dependencies from package.json. Make sure discord.js is listed under dependencies, not devDependencies. If your start command is not node index.js, update it on the Startup page under the start command field. Common alternatives: node src/bot.js, node . (uses the main field in package.json). After uploading files and setting the start command, click Start. Check the Console page for errors. Common issues: missing TOKEN environment variable (bot will throw an error about an invalid token), missing dependencies (run npm install manually from the Console if needed), or a syntax error in your code. The console output will show the exact error. To update your bot code, stop the server, upload the new files via File Manager, and start again. If you have added new dependencies, the panel will run npm install again automatically.

Question 27

How do I deploy a discord.py bot?

Accepted Answer

Create your bot application at discord.com/developers/applications and add it to your Discord server with the appropriate permissions. Copy the bot token; you will need it as an environment variable. In the panel, go to the Startup page and add an environment variable named TOKEN (or whatever your code reads from os.environ) with your bot token. Never hardcode the token in your source files. Upload your bot files via File Manager. Include a requirements.txt listing your dependencies. The panel installs them automatically from requirements.txt on first start. Make sure discord.py or py-cord (whichever you use) is listed there. Include the correct version pin if your code depends on a specific API version. Set your start command on the Startup page. Common options: python bot.py, python main.py, or python -m yourpackage if structured as a package. The panel uses the Python version configured for your server; check the Startup page for the Python binary being used. After uploading files and configuring the start command, click Start. Check the Console page for errors. Common causes of failure: TOKEN environment variable not set (you will see a LoginFailure or similar error), a missing import (ModuleNotFoundError means a dependency is not in requirements.txt), or a Python version mismatch. If dependencies fail to install, check the Console output from startup for pip error messages. To update code, stop the server, upload updated files via File Manager, and restart. If you have changed requirements.txt, the panel will re-run the install automatically.

Game Setup Guides