Is your Operation: Harsh Doorstop game server not working as expected? Don’t worry, you can solve most issues yourself in just a few steps. This guide covers the most common problems, their causes, and how to fix them.
First, check your server’s Console. It shows where the startup process stops. Lines with [ohd-entrypoint] and [ohd-config] show what your server prepares at startup, such as the map, game mode, and number of bots.
If your server stopped starting after you added a mod, try removing it in the Workshop tab and restarting the server. This is a quick way to find out whether the mod is causing the issue.
- Check the Overview to make sure your server is online, and wait one or two minutes after starting it.
- Search the server list for part of your server name and check the server list filters in the game.
- If you set a server password, make sure the capitalization is correct.
For more information, see Connect to the server.
- Unsupported characters: The server password can’t contain spaces,
?, or quotation marks. Otherwise, your server will start without a password. The RCON password can’t contain spaces or quotation marks. Otherwise, RCON will be disabled. In both cases, you’ll see a message in the Console. - No RCON port: ZapX only opens the RCON port after you set an RCON password and restart your server.
- Make sure BLUFOR bots and OPFOR bots are set to a value greater than
0, then restart your server after saving. - Bots only join the game once the first player joins your server. Until someone connects, the server waits for the round to start.
- If a name is entered in the Custom map (Mod) field, it takes priority over the Starting map. Clear the field to play an official map again.
- For a map from a mod, check its short name, such as
Tarnokhiv, and make sure the mod is installed on your server. - If the Game mode is set to
auto, maps with_Skirmish_in their name automatically run as Skirmish. To use a different mode, select it in the Game mode field.
- Your server applies Workshop changes the next time it starts. Restart it after adding a mod in the Workshop tab.
- Check that the Workshop ID is correct and that the mod is public in the Steam Workshop.
- If the
Modsfolder already contains a manually uploaded folder with the same name, your server won’t overwrite it. Delete or rename your folder to use the Workshop version. - Manually uploaded mods must be placed directly in the
Modsfolder, asMods/<Modname>/<Modname>.uplugin. If the folder is one level deeper, the game won’t load the mod.
- No restart: Changes to the Startup parameters only take effect after a restart.
- Changed the value in the file: Your server overwrites the server password and RCON settings in
Game.iniwith the Startup parameters every time it starts. Make those changes there instead. - Admin added again: Your server adds admins from the Admin Steam IDs field to
Admins.cfgevery time it starts. Remove the ID from the field first, then remove it from the file.
- Check that the SteamID64 in the Admin Steam IDs field is correct. It has 17 digits and starts with
7656. Your server skips invalid entries and displays a message in the Console. - Restart your server after saving. The admin is only added after the restart.
An empty Operation: Harsh Doorstop server uses about 1 GB of memory. Usage increases with more players, bots, and mods. Keep an eye on resource usage in the Statistics tab.
Still having problems after troubleshooting? Our support team is here for you every day. Just create a support chat in your ZapX customer account and describe your issue in as much detail as possible, ideally including an excerpt from the Console. We’ll look into it as soon as possible and help you solve the problem!
With these tips, you can solve the most common issues with your Operation: Harsh Doorstop server yourself. Our guide Server Configuration shows you how to configure your server. If you have more questions or need help, our support team is available every day! 🙂