QANGA Server Version Mismatch After an Update: How to Fix It

When a QANGA patch lands, players update through Steam straight away, but a custom server stays on its old build until it is updated. QANGA checks the client and server versions against each other, so an old server either disappears from the list or tells players to update. The fix is to update the server (SteamCMD app 1652070, or a restart if auto update is on), let the first start finish, and take a backup first in case the update touches saves.

Why this keeps happening with QANGA

QANGA is in early access and patches a lot. In 2026 there was a move to Unreal Engine 5.7 in June with a hotfix two days later, an AI and combat rebuild in July, and a big module and interface update in September. Since an early hotfix in 2024 the game compares client and server versions and prompts for an update when they differ, and the server list filters by build. Every one of those patches means every custom server must update before anyone can join.

QANGA cyborg with a vehicle

Step 1: Confirm it is a version problem

Signs it is the version and not something else:

It worked yesterday and a patch came out today.
Players see an update prompt or a version message when joining.
The server is gone from the list for everyone at once, right after a patch.
The server console shows it running normally.

If the server never worked, or only one player has trouble, see the other sections below first.

Step 2: Back up the world

Do this before updating, every time. Early access updates can change the save format, and the developers have fixed save bugs in recent patches, including progress being lost when an older save finished after a newer one, and saves mixing between servers on different ports (both fixed in v0.0.23a).

Stop the server cleanly so it saves.
Copy the server's Saved folder somewhere safe, with the date in the name.
Only then update.

A general walkthrough is in how to back up a game server.

Step 3: Update the server

Self hosted:

steamcmd +force_install_dir /home/qanga/server +login anonymous +app_update 1652070 validate +quit

Then start the server again. validate checks every file, which helps after a big engine change.

Hosted with auto update on: restart the server. The update runs at start.

If you run the game's beta or a test build on your own PC, your client will not match a server on the public branch. Players and server need the same branch.

Step 4: Let the first start finish

The first start after an update takes noticeably longer. The server checks and installs files, then loads the universe. Do not restart it halfway because it "looks stuck", which only starts the process again. Wait until the console shows the server is ready (on current builds it prints the Steam sockets address), then give the server list a minute or two before searching.

Step 5: If it is updated but still missing

Some patches changed how servers register:

The June 2026 engine update. After the move to Unreal Engine 5.7, many Linux servers vanished from the list until hotfix v0.0.21b, which builds the correct Steam file into the Linux server. If your server still runs a build from those two days, or you kept a manually copied steamclient.so from the workaround, update to the current build and remove old manual copies.
v0.0.21a fixed a server listing issue that kept some servers out of the browser. Another reason to be on the current build.
Query port. The list asks the query port about your server. If a firewall or router rule changed, the server runs but is never listed. Check the port is open for UDP.
Name search. Search for the exact session name, 5 to 25 characters.

Step 6: If the world looks reset

After an update, a server occasionally starts on a fresh universe instead of your world. Before panicking:

Check the server is using the same port as before. Current builds keep saves per port, so a port change looks like a new world.
Check the save folder is where it was and was not overwritten.
If the update really broke the save, restore your backup with the matching older server build, or accept a fresh start. Early access means an occasional wipe, and patch notes usually warn when one is coming.

Quick diagnosis

What you see	Most likely cause	Fix
Update prompt when joining	Server on old build	Update, restart
Server gone for everyone on patch day	Server on old build	Update, restart
Gone after the June 2026 engine update	Old Linux build	Update to current, drop manual steamclient.so
Updated but still missing	Query port, or still starting	Check port, wait for ready line
One player cannot join	Their client on beta or not updated	Match branches, update game
World looks new	Port changed or save broken	Restore port or backup

QANGA base under construction

Avoiding it next time

Watch the QANGA announcements on Steam, keep auto update on, and make backups a habit before restarts. If the server is hosted, the restart is the update.

On a QANGA server from GamezServers, Auto Update is on by default, so a restart from the panel pulls the build that matches your players. Ports stay fixed, which keeps the per port saves where they belong, and one click backups let you snapshot the world before a big patch. The live console shows when the first start after an update has finished. New to running one? See how to host a QANGA dedicated server.

FAQ

Why can't I join my QANGA server after an update?

The server is on the old build. QANGA checks client and server versions, so update the server and restart.

Does a QANGA update wipe my world?

Usually not, but early access updates can change saves. Back up the server's save folder before every big update.

How long does a QANGA server take to start after an update?

Longer than usual, since files are checked and installed first. Wait for the console to report the server is ready.

Why did my QANGA server disappear from the list after the engine update?

Linux servers needed a fix to register after the June 2026 Unreal Engine 5.7 update. Hotfix v0.0.21b solved it, so update to the current build.