Rising World Server Not Showing Up or Can't Connect (Fixes)

If your Rising World server is missing from the multiplayer list, skip the list and use Connect by IP at the bottom of the Multiplayer screen with the full address and port, for example 203.0.113.10:4255. The list depends on the query port (TCP, always the game port minus one), so a closed 4254 hides the server while it still works by IP. If players cannot connect even by IP, the usual cause is an edition or version mismatch: the current Rising World and the old Java version cannot join each other, and a client that just updated cannot join a server that has not.

Which problem do you have?

Edition and version

Rising World exists in two editions that do not talk to each other:

A Java client never sees a current server, and a current client never sees a Java one. Worlds do not convert between them either. On GamezServers both run on the same plan, and you switch with the server type in the panel: the standard Rising World type for the current version, Java Legacy for the old one. Pick the one that matches what your group actually plays, and have anyone on the other edition switch their branch in Steam (right click Rising World, Properties, Betas).

After a game update

JIW-Games patches the current version regularly, and Steam updates players straight away. A server still on the previous build then turns everyone on the new build away, which looks exactly like a network fault.

1. Make sure Auto Update is on in the panel (it is by default).
2. Restart the server. It checks for and installs the update on start.
3. Watch the console until the server reports it is ready, then connect.

On a home server, update with SteamCMD (app 339010) before starting. If one player is still refused, they are probably the one out of date: have them restart Steam so the patch downloads, or check that they have not joined a test branch under Betas.

The list and the query port

The server list asks each server for its details over the query port, which is always the game port minus one, over TCP. The developer's dedicated server setup thread is clear that this port is required for a server to appear in the list. With the default game port of 4255, the query port is 4254.

Reasons a working server is not in the list:

• Query port closed. On a home server, forward 4254 TCP as well as 4255. If you changed Server_Port, the query port moves with it.
• Server_Visible=False in server.properties. That hides the server on purpose. Set it to True and restart.
• Filters. The list can hide password protected or full servers. Clear the filters and search the name again.
• The list is slow. A freshly started server can take a while to show up. Connect by IP in the meantime.
• Searching the wrong name. On GamezServers the Server Name in the panel is written into Server_Name on every start, so a name you typed into the file gets replaced by the panel value.

None of these stop Connect by IP. If the address works directly, your server is fine and only the listing needs attention.

How to Connect by IP

1. Start Rising World and open Multiplayer.
2. Click Connect by IP at the bottom of the server list.
3. Enter the address with the port, for example 203.0.113.10:4255. On GamezServers, copy the address from the panel exactly as shown.
4. Enter the password if the server has one.

The console works too. Open it with the key left of 1 and type:

connect 203.0.113.10 4255

Leaving out the port is the classic mistake. If your server does not run on the default 4255, an address without a port goes nowhere.

Ports and the server state

If even Connect by IP fails, check that the server is actually reachable.

On a home server, forward both protocols for the game port, allow the server through Windows Firewall, and test from outside your network. Our port forwarding guide has router steps. On a hosted server there is nothing to forward, so a timeout there usually means the server is not running yet.

Also confirm the server finished starting. A large world can take a while to load after a restart, and a connection attempt before it is ready fails. Wait for the console to say the server is ready. If it stops with an error instead, read the last lines: a world folder that does not match World Name makes the server generate a fresh world, which takes time and is easy to mistake for a hang.

Password problems

• On GamezServers, set the Server Password in the panel. The panel writes it into server.properties on every start, so a password edited only in the file is replaced at the next restart.
• Blank means no password. If players keep getting asked for one, an old value is still set.
• Use letters and numbers only. It rules out typing and keyboard layout problems when a player swears the password is right.
• Restart after changing it. The server reads the password at start.

Whitelist, bans and the player cap

When most of the group gets in and one person does not:

• Whitelist. With Server_UseWhitelist=True, only players listed in the server's whitelist file can join. Add their UID (their Steam ID) or turn the whitelist off.
• Bans. An admin may have banned them, possibly with a long duration. unban <uid> from the console lifts it. The commands are in our Rising World admin commands guide.
• Player cap. Settings_MaxPlayers in server.properties sets the limit. When the server is full, the next player is refused.
• Their own connection. A player on a strict school or work network may block the ports. Try a different network to rule it out.

Checklist before you ask for help

Less to check next time

Most of this list exists because a home server needs ports, a PC that stays on and manual updates. A Rising World server on GamezServers has its own address with the port shown in the panel, updates on restart, keeps the password and world name in panel settings, and lets you switch between the current version and Java Legacy from the panel. New customers get 50% off the first month. To bring an existing world along, follow how to move a Rising World save to a server.

FAQ

Why is my Rising World server not in the server list?

The query port (the game port minus one, TCP) is not reachable, Server_Visible is off, or the list has not refreshed yet. Connect by IP still works.

Can Java version players join the new Rising World?

No. The editions are separate. Java players need a Java legacy server, and current version players need a current server.

Do I need the port when using Connect by IP?

Yes, unless the server runs on the default 4255. Enter it as address:port.

Why can nobody join after a Rising World update?

The server is still on the old build. Restart it with Auto Update on so it installs the patch, then try again.

What ports does a Rising World server need?

4255 TCP and UDP for the game and 4254 TCP for the server list. RCON uses 4253 TCP if you turn it on.