BATTALION: Legacy Server Not Showing in Server Browser? Fixes

When a BATTALION: Legacy server does not show in the in-game Server Browser, the cause is usually one of three things: Steam cannot reach the server's query port (UDP 27015 by default), the server is on an older build than the players after a patch, or the server simply has not registered yet. Players can still try connect with the address in the console while you fix it. Work through the checks below in order and you will find it within a few minutes.

How the Server Browser finds servers

BATTALION: Legacy lists community servers through Steam. When the server starts, it registers with Steam over its query port, which Bulkhead's self hosting guide says is UDP 27015 unless you change it with -QueryPort=. Steam then answers the game's Server Browser with the list of registered servers.

That gives two separate things that can break:

Path	Port	What breaks it
Being listed	Query port (UDP 27015 by default)	Port closed, server not registered, wrong build
Joining	Game port (UDP)	Port closed, wrong address, version mismatch

If players can connect with the console but cannot see the server, the listing is the problem. If neither works, the server or its game port is.

BATTALION: Legacy, a World War II arena shooter

Check 1: Try the console connect

Before you change anything, have one player open the console in game and type:

connect <server-ip>:<game-port>

On our servers the full address with the port is shown in the panel. If the connect works, your friends can play right now and you can fix the listing calmly. If it fails too, skip ahead to checks 3 and 4.

Check 2: Search the way the browser expects

In game, go to Play, then Server Browser.

Search for one distinctive word from your server name rather than the whole name. Clan tags with brackets and symbols often do not match a full string search.
Clear any filters, especially ones that hide empty or passworded servers. A brand new server is empty.
Refresh after a minute. A server that just started may not be in the list on the first refresh.

The name comes from -SteamServerName on the launch line, or Server Name in our panel, up to 60 characters. If you changed it, restart the server so it registers under the new name.

Check 3: Is the server on the current build?

After a game patch, Steam updates every player's game right away. A server still on the old build drops out of what those players can see and join.

Self hosted: stop the server and run SteamCMD's install line again:

steamcmd +login anonymous +force_install_dir <InstallDir> +app_update 805140 +quit

GamezServers: keep Auto Update on in the panel. It pulls the latest build from Steam each time the server restarts, so one restart after a patch brings it current.

If you see the problem right after a patch and nowhere else, this is almost always it.

Check 4: Open the query port and game port (self hosting)

The most common cause on a home server is a closed query port.

Forward UDP 27015 (or whatever you set with -QueryPort) to the PC running the server.
Forward the server's game port, also UDP.
Allow the server executable through Windows Firewall for both private and public networks, or open the ports in your Linux firewall.
If you run two servers on one machine, give each its own query port and game port, and forward both pairs.
Make sure the forward points at the PC's current local IP. If the router hands it a new address after a reboot, the forward silently stops working. A DHCP reservation fixes that.

Our port forwarding guide walks through typical routers. If your ISP uses carrier grade NAT, nothing you do on the router will open a port, and hosting without port forwarding explains your options.

A quick way to tell if it is your network: if the server shows up for someone on your home Wi-Fi but not for anyone outside, the ports or the ISP are the problem.

Check 5: Did the server actually finish starting?

Read the console. A server that crashes during startup, or restarts in a loop, registers for a moment and disappears again. Run it with -Log so the log prints to the console. On our servers the live console in the panel shows it, and restarting from there lets you watch the whole start.

Look for:

An error right after the map loads.
A port already in use, usually from a second copy of the server still running.
A failed Steam login line.

Fix what the log names, start again, and give the browser a minute.

BATTALION: Legacy gameplay

Check 6: Only one player cannot see it

When everyone else sees the server and one player does not, look at their side:

Their game is not updated. Have them restart Steam so it downloads the patch.
Their Steam download region is far from the server. Server lists can be affected by region, so try switching it in Steam's Downloads settings, restarting Steam and checking again.
Their own network blocks server queries. Try from a phone hotspot to rule it out.

The console connect still works for them in most of these cases, so give them the address while you sort it out.

Quick checklist

Console connect works? Then it is only the listing.
Search one word of the name, clear filters, refresh.
Server updated after the latest patch.
Query port (UDP 27015 by default) and game port forwarded and allowed.
Server started cleanly, no crash loop in the log.
One player only? Check their game version and region.

A server that is already reachable

Most of this list is about home networks. A BATTALION: Legacy server from GamezServers comes with its own address and open ports, Auto Update pulls the latest Steam build on every restart, and the server name and admin password are set in the panel. The live console shows the startup log if anything goes wrong, and you can restart with one click before scrim night. For the full self hosted setup, see how to host a BATTALION: Legacy server.

FAQ

Why is my BATTALION: Legacy server not in the Server Browser?

Usually the query port is blocked, the server is on an older build after a patch, or it has not finished starting. Check them in that order.

What is the BATTALION: Legacy query port?

UDP 27015 by default. Change it with -QueryPort= on the launch line, and forward whichever port you choose.

Can players join without the Server Browser?

Yes. Open the console in game and type connect followed by the server address and game port.

My server disappeared after an update. What happened?

The game updated and the server did not. Run the SteamCMD update for app 805140, or restart a GamezServers server with Auto Update on.

How long does a new server take to appear?

Usually a minute or two after it finishes starting. If it is still missing after that, check the ports and the log.