Skip to content

OpenTTD: Common Issues

Learn how to fix common issues with your OpenTTD game server, from version conflicts and missing NewGRFs to desyncs and incorrect savegames → Find out more

17 November 202610 min read2 Views0 helpful

Introduction

Running your own OpenTTD game server is a lot of fun, but it also means taking responsibility when something goes wrong. Version conflicts, missing NewGRFs, or the wrong savegame are common hurdles that almost every server owner encounters sooner or later.

To help you spend less time troubleshooting and more time building your transport network, we’ll show you the most common issues here and how to fix them directly in ZapX.

Problems and solutions

The causes of server issues are often not immediately obvious. Your main place to check is your server’s Console. Lines containing [openttd-entrypoint] show what your server prepares at startup, such as which savegame it loads. You can also enter commands in the Console, such as server_info to view the invite code, players, and companies.

General

General issues are often related to basic settings, the game version, or simple misconfigurations. They can usually be fixed quickly with a few checks.

Players see “VERSION CONFLICT”

The game and server must use exactly the same OpenTTD version. Your server is currently running OpenTTD 15.3, the latest stable version. Players using a different version, including a test version such as 16.0-RC, can’t join. They’ll need to install the exact version your server is running.

Server not in the server list
  • Check in Overview whether your server is online.
  • In the Configuration tab, under Startup Parameters, check whether Server Game Type is set to public. With invite-only, your server intentionally won’t appear in the list; with local, it won’t register with the OpenTTD service at all.
  • If the Console says “Server registration failed,” registration with the OpenTTD service didn’t work, and your server automatically switches to local. Restart it so it can try again.
  • If it says that another server registered with the same invite code, a second server is still running with the same details. This could be an old installation from which you copied secrets.cfg, for example. Stop the other server and restart yours.

Regardless of whether it appears in the list, you can always connect directly to your server using Add Server and the IP address and port shown in Overview. Learn more in Connecting to the server.

Changes don’t take effect or are lost
  • No restart: Changes to Startup Parameters only take effect after a restart.
  • Changed a value in the file: Your server overrides the server name, passwords, number of companies, and visibility with the Startup Parameters every time it starts. Change these settings there, not in openttd.cfg, private.cfg, or secrets.cfg.
  • Edited a file while the server was running: OpenTTD rewrites openttd.cfg when it shuts down. If you edit it while the server is running, your changes will be lost the next time it stops. Stop the server first.
  • Setting applies to new games: Many values in openttd.cfg, such as the map size (map_x, map_y) or the NewGRFs in the [newgrf] section, only apply to a new map. A loaded savegame keeps its own settings.
A player can no longer join their company

Company passwords have not been available since OpenTTD 15. Instead, access to a company is controlled by an allowlist linked to the player key for that particular game. If someone suddenly starts playing from a new installation or another PC, the server won’t recognize them and they’ll join as a spectator.

  • Another member of the company can authorize them again in the Online Players window.
  • If no one from the company is online, you can help through the Console: use clients and companies to find the player and company numbers, then use move to move them directly into the company, for example, move 5 1. Use authorized_key add company:1 client:5 to authorize them for the company permanently.
All company slots are occupied

Once your server reaches the configured maximum number of companies, new players can’t start their own company and can only watch or join an authorized company. In the Configuration tab, under Startup Parameters, increase Max Companies to a maximum of 15. Keep in mind that AI companies count toward the limit. You can remove abandoned companies in the Console with reset_company and the company number shown by companies.

Savegames

There are a few things about savegames in OpenTTD that you should know.

Wrong savegame or a new map after startup

The Savegame startup parameter determines which savegame your server loads. When it starts, the Console shows which file is being loaded with [openttd-entrypoint] loading.

  • latest (default): Your server loads the latest savegame from save and save/autosave. If there isn’t one yet, it creates a new map.
  • new: Your server creates a new map on every startup. To continue playing, switch back to latest.
  • Filename, for example, mygame.sav: Your server loads this exact file on every startup. Any progress you make afterward is saved in the automatic savegames and won’t be loaded the next time the server starts. Once your own savegame has loaded, it’s best to switch Savegame back to latest.

If your server can’t find the specified file, it displays a warning in the Console and loads the latest savegame instead.

Custom savegame won’t load

Upload your savegame to the save folder in the Savegames tab and enter its filename under Savegame. A savegame from an OpenTTD version newer than the one your server is running can’t be loaded. Savegames from older versions usually work. If your savegame uses NewGRFs, Game Scripts, or AIs, your server needs them too. See Extensions below for more information.

Progress is missing after a restart

When you stop or restart your server through ZapX, it first saves the current map as save/autosave/exit.sav and loads it again the next time it starts. OpenTTD also automatically saves every 10 minutes by default to save/autosave. So after a crash, at most you’ll lose the progress made since the last automatic save.

To save manually in between, enter a command such as save backup in the Console. You can also set this command to run regularly under Schedules.

Extensions (NewGRFs, Game Scripts, AIs)

NewGRFs, Game Scripts, and AIs are what make OpenTTD so versatile. Problems can arise if they’re missing on the server or on players’ computers, or if their versions don’t match.

Game stays paused after loading (“Missing NewGRF files have been disabled”)

Your savegame uses NewGRFs that are missing from the server. OpenTTD disables them and pauses the game. Upload the missing NewGRFs before continuing.

Upload the missing NewGRFs to the server, either directly from OpenTTD’s online content through the Console or as files:

  1. Through the Console: content update retrieves the list of available content, content state and a search term show matching entries, content select with the entry number selects one, and content download downloads everything selected to the content_download folder.
  2. As files: Upload the NewGRF to the newgrf folder in the Files tab.

Then restart your server.

Set up NewGRFs, Game Scripts, or AIs for a new game

Downloading an extension with content download only makes it available; it doesn’t enable it. The extensions used by a new map are listed in the [newgrf], [game_scripts], and [ai_players] sections of openttd.cfg. The easiest way to set up the list is in your own OpenTTD single-player game, then copy the sections from your local openttd.cfg.

  1. Stop your server and add the sections to openttd.cfg.
  2. Set Savegame to new and start the server. It will now create a new map with your extensions.
  3. Then set Savegame back to latest; otherwise, you’ll get a new map every time the server restarts.

An existing savegame keeps the NewGRFs it was created with.

Players see “NEWGRF CONFLICT”

The server is using NewGRFs that the player is missing or has in a different version. They should select the server, open NewGRF Settings, and click Find missing content online. If a NewGRF isn’t available through online content, they’ll need to install it themselves.

Crashes and desyncs

Nothing ends a good session faster than a crash or a player who keeps getting disconnected.

Players are disconnected with “Network game synchronization failed” (desync)

A desync occurs when the game and server no longer calculate the same result, causing the game to disconnect. The Console will show “desync error.” Common causes include:

  • Different NewGRF versions: Players and the server must use exactly the same NewGRFs. Ask affected players to update their NewGRFs through NewGRF Settings.
  • Faulty NewGRFs or Game Scripts: If the desync started after you added an extension, that extension is the most likely cause. Test the map without it.
  • Known game bugs: OpenTTD itself can also have bugs that cause desyncs. These are regularly fixed in new versions.

A single desync is nothing to worry about: the player can simply rejoin and will receive the current map.

Faulty or outdated extensions

Crashes are often caused by faulty or outdated NewGRFs, Game Scripts, or AIs, especially when several are used together. Keep your extensions up to date: in the Console, after running content update, select all available updates with content upgrade and download them with content download. However, an existing savegame will continue to use the versions it was created with.

To narrow down the cause, start with a minimal configuration: create a test map without extensions, then add them back one at a time. This will help you identify exactly which one is causing the issue. Back up your savegame first.

Performance

A fresh OpenTTD map requires very few resources. However, requirements increase significantly as the map grows and you add more vehicles and AI companies.

Server stutters on large maps
  • Map size and vehicles: Large maps with thousands of vehicles require a lot of CPU and memory. Keep an eye on resource usage in the Statistics tab.
  • AI companies: Each AI is constantly calculating. Having fewer AI companies can noticeably reduce the load on your server.
  • Game Scripts and NewGRFs: Complex extensions require additional resources.

If your server is consistently reaching its limits, upgrading it through Overview is the easiest way to get more performance.

“Downloading the map took too long”

When joining, the game downloads the entire map from the server. The default timeout may not be long enough for very large maps or slow connections. Stop your server and increase the max_download_time (default 1000) and max_join_time (default 500) values in the [network] section of openttd.cfg, for example, by doubling them. The values are specified in game ticks.

Game requirements not met

To keep your game server running smoothly and reliably, it’s important to choose a configuration that suits your project. Requirements depend heavily on map size, number of vehicles, AI companies, and extensions.

During the ordering process, ZAP-Hosting provides a recommended minimum configuration. Follow this recommendation or scale up if needed. If your project grows over time, upgrading your game server is the easiest way to ensure performance and stability.

Network

Network issues can cause lag, delays, or connection drops.

Ping spikes, lag, and network delays

Lag is usually caused by limited server resources, a player’s slow connection, or a server location far from your players. First, check in the Statistics tab to see whether your server is under load. Choosing a server location close to your players can help reduce latency.

If you suspect routing issues or other external network problems, don’t hesitate to contact our support team. We’ll help you investigate and find the best solution.

DDoS and other network threats

Game servers are occasionally targeted by Distributed Denial of Service (DDoS) attacks. These flood the server with huge amounts of traffic, causing lag, connection loss, or even complete downtime.

Most of these threats are outside your control, but ZAP-Hosting provides integrated protection and defense mechanisms to protect your server against common and advanced attacks. If you suspect your server is being targeted and it’s causing problems, contact our support team for help and next steps.

Preventive measures

Regular backups can save you a lot of stress and trouble. Create backups regularly so you can restore an older, working version if something goes wrong. We already back up your game server automatically every day. With the ZapX Pass, you can also create your own backups at any time and restore them with a click—with ZapX Pass Pro, you can even automate them on your own schedule. Learn more in our guide to Backups.

Before trying new NewGRFs, Game Scripts, or AIs, it’s also a good idea to back up your map using save and a custom name in the Console.

Conclusion

These steps should help you resolve your issue. If your problem is listed here, the relevant solution will usually point you in the right direction and get your server running again quickly. For an overview of all areas of your server, see the Dashboard overview.

If not, don’t hesitate to contact our support team: simply start a Support Chat in your ZapX customer account. We’re here every day and happy to help! 🙂

FAQ

Frequently asked questions

The versions usually don’t match. The game and server must use exactly the same OpenTTD version, currently 15.3. If a player is missing NewGRFs, they can find them under NewGRF Settings by selecting Find missing content online.
Check the Savegame startup parameter. With new, the server creates a new map at every startup; with latest, it loads the latest savegame from save and save/autosave.
The server is usually missing NewGRFs used by your savegame. Upload them through the Console using the content commands, or as files in the newgrf folder, then restart the server.

Feedback

Was this article helpful?

Your feedback helps us prioritize and improve content.

0 of 0 Users found this article helpful.

Personal support

Need more help than the guide provides?

Our ZAP support team knows your product — briefly describe your issue and we'll help you personally.

Zappy knows this guide and answers you right in the chat.