Is your Alchemy Factory game server not working as it should? Don’t worry—most issues are easy to fix yourself. According to the developers, the Alchemy Factory dedicated server is still experimental, so updates can sometimes change how it behaves. In this guide, you’ll find the most common issues, their causes, and what you can do to resolve them.
You can narrow down most issues by checking the Console. Lines containing [alchemyfactory-entrypoint] show what your server is preparing during startup. Lines containing [ServerConfig] come from the game itself and show, for example, which settings it started with. You can also find the same messages in the file AlchemyFactory/Saved/Logs/AlchemyFactory.log in the Files tab.
Alchemy Factory is officially available as a Windows server only. We run it on Linux using a compatibility layer. This works reliably, but makes the first startup a little slower, in particular.
The first startup takes a very long time
During the very first startup, your server sets up additional runtime components. This can take 15 to 25 minutes. In the Console, you’ll see the line Running extended Wine bootstrap and, at the end, Extended Wine bootstrap complete. The game then starts and creates the ServerConfig.ini file for the first time.
Don’t stop or reinstall your server during this process, or setup will start over. The first startup after an update or reinstallation may also take a little longer.
The server won’t start or shuts down immediately
Check the Console to see where startup stops.
- If you see a line containing
[alchemyfactory-entrypoint] ERROR, your server couldn’t prepare its runtime environment or game files. Restart it once. If that doesn’t help, contact our support team. - If the server shuts down shortly after the Console warns about low memory, there isn’t enough RAM. See Performance below for more information.
- If you edited
ServerConfig.inimanually, check that each setting is on its own line in the formatname=value.
Alchemy Factory gives you three ways to join your server: through the server list, directly using an IP address and port, or with a join code. For details, see Connecting to the server.
I can’t join using an IP address after the first startup
During the very first startup after installation, your server may still be running in Steam relay mode. In this mode, it’s not possible to connect using an IP address and port. Players may see a message such as PendingConnectionFailure.
You can identify the mode in the Console, in the line [ServerConfig] join address::
- If the address contains
steam.and the noteSteam relay, your server is still in relay mode. - If it shows your IP address and port with
direct IP, everything is configured correctly.
Solution: Restart your server once. It will switch to direct mode automatically, and you’ll then be able to join using an IP address and port.
If the line direct-IP cert auth status: 3 remains in the Console for several minutes after startup, the Steam authentication process is stuck. Restarting the server should help in this case too. The correct status is 100 (OK).
The server doesn’t appear in the server list
- Not registered with Steam yet: Your server registers with Steam after startup. If it doesn’t work right away, it will automatically try again (the
session_retry_secondsvalue, every 10 seconds by default). Once you seesession created OKin the Console, it’s registered. - Not public:
server_public=1must be set inServerConfig.ini. If it’s set to0, your server won’t appear in the list. - LAN mode: Keep
server_lanset to0. If it’s set to1, your server will only be visible on a local network.
You can connect directly using an IP address and port or with the join code while your server is not yet listed. The current join code is shown in the Console, in the line [ServerConfig] join address:.
Message says the game version doesn’t match
If you see a message such as “Game version does not match host version” when joining, the game and server are running different versions. This usually happens right after a game update.
- Update your game on Steam.
- It may take a little while for the server update to become available after a game update. When it’s ready, ZapX will show the Update available notice when you open your server. Select Apply update to install it.
You can check your server’s current version in the Console, in the line advertised game info updated: version=.
My password isn’t accepted
- Check that you’re using the correct uppercase and lowercase letters.
- Set the password in the Configuration tab under Startup parameters, in the Server password field. If the field is empty, your server is open to everyone.
- Restart your server after changing the password. The new password won’t take effect until you do.
Other players can’t join even though there should be free slots
The max_clients value in ServerConfig.ini determines how many players can join your server at the same time. It’s set to 4 by default. Change the value in the Configuration or Files tab, then restart your server. You can check the value your server is currently using in the Console, in the [ServerConfig] loaded: line next to maxClients.
All server settings are stored in the ServerConfig.ini file in the main folder. You can edit it in the Configuration tab, use Edit directly to edit it as raw text, or edit it in the Files tab.
My changes don’t take effect or have disappeared
- The server hasn’t been restarted: Alchemy Factory reads
ServerConfig.inionly when it starts. Restart your server after every change. - A value is overwritten at startup: Your server writes
server_nameandserver_passwordto the file at every startup using the Startup parameters (Server name and Server password). It always setsserver_relayto0so players can join using an IP address. Make sure to change the server name and password under Startup parameters. - Ports:
server_portandquery_portin the file have no effect. Your server always uses the ports assigned to it by ZapX, which you can see in Overview. - The file was edited while the server was running: It’s best to edit
ServerConfig.iniwhile your server is stopped, then restart it.
All other values, such as max_clients, admin_password, autosave_mode, and pause_when_empty, are retained.
I can’t become an admin
The Console in Alchemy Factory is read-only; you enter commands directly in the game. You’ll need an admin password:
- Set a password for
admin_passwordinServerConfig.ini. This value is empty by default, so no one can become an admin. - Restart your server.
- In the game, press Enter to open the chat, then enter
/admin, followed by a space and your admin password.
Enter /help in the chat to see all available commands. The max_admins value determines how many players can be admins at the same time. It’s set to 1 by default.
Nothing happens in the world when no one is online
This is intentional. If pause_when_empty=1 is set in ServerConfig.ini (the default), your server pauses the game while no players are connected. To keep your factory running, set the value to 0 and restart your server. Your server will then need more resources even when no players are online.
Your save data is stored in the AlchemyFactory/Saved/SaveGames folder. Each world has its own folder, such as NewGame_ followed by a number.
My progress is missing after a restart
The autosave_mode value in ServerConfig.ini determines how often your server saves:
0→ Save when sleeping in the game1→ Every 5 minutes (default)2→ Every 10 minutes3→ Never
Progress made since the last save may be lost when the server restarts. Schedule restarts for times when no one is playing, and don’t set autosave_mode to 3.
Find and manually back up your save data
Open the AlchemyFactory/Saved/SaveGames folder in the Files tab or via SFTP. Your world’s folder contains the automatic saves, such as AutoSave0 to AutoSave2. If you want to replace anything there, stop your server first and copy the entire world folder as a backup.
Good server performance is essential for an enjoyable gaming experience. RAM is especially important for Alchemy Factory. Keep an eye on usage in the Statistics tab.
RAM usage keeps increasing over time
We’ve observed that Alchemy Factory’s RAM usage gradually increases over many hours, even when no one is online and the factory remains unchanged. Usage is much lower right after a restart. This points to an issue with the game’s server itself. Adding more RAM often just delays the problem.
Solution: Set up regular restarts in the Schedules tab, for example once a day at a time when no one is playing.
Brief spikes when building large structures
When you place many objects at once—for example, when cutting and pasting a large structure or using a large blueprint—your server needs significantly more RAM for a short time. The game itself warns in multiplayer that this kind of operation may fail. It’s best to split large blueprints into several smaller steps.
System requirements aren’t met
As your factory grows, it needs more RAM and processing power. ZAP-Hosting provides a recommended minimum configuration during checkout. If resources become insufficient over time, even with regular restarts, the easiest way to improve stability is to upgrade using the button in Overview.
Network issues can cause lag, delays, or disconnections. There are many possible causes, but the right settings and security measures can usually resolve them.
Ping spikes, lag, and disconnections
Lag and disconnections often happen when your server is reaching its limits, for example, when RAM is almost full. First, check usage in the Statistics tab. Choosing a server location close to your players can also 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 sometimes targeted by attacks, especially Distributed Denial of Service (DDoS) attacks. These flood the server with an extremely high volume of traffic, causing lag, disconnections, or even complete downtime. ZAP-Hosting automatically protects your server against common and advanced attacks. You can see past attacks in the DDoS Manager. If you suspect an attack, contact our support team.
Regular backups can save you a lot of stress and hassle. 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 ZapX Pass, you can also create your own backups at any time and restore them with one click—with ZapX Pass Pro, you can even schedule them automatically. Learn more in our guide to Backups.
Since the Alchemy Factory dedicated server is still experimental, it’s especially worth creating a backup before an update. Regularly restarting your server from the Schedules tab also helps keep RAM usage under control.
Still having issues after troubleshooting? Our support team is here for you every day. Just start 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 resolve it!
With these tips, you can resolve the most common issues with your Alchemy Factory server yourself. For an overview of all areas of your server, see our Dashboard overview. If you have more questions or need help, our support team is here for you every day! 🙂