RageCOOP Can't Connect to Server Fix (Version, Port, F9 Menu)

When RageCOOP will not connect, read the message the client shows: the server tells you why it refused. RAGECOOP version x.y.z required! means client and server versions differ. A silent timeout means the server is not reachable on UDP 4499. Username errors are about spaces or special characters. And if the F9 menu never appears at all, ScriptHookV or ScriptHookVDotNet is out of date for your GTA V build. Here is each case and its fix.

Error messages and what they mean

Version mismatch

The server checks the client version on every connection and rejects anything different. RageCOOP has two lines in use: the last numbered release, 1.5.4.7, and the nightly build. A player on nightly cannot join a 1.5.4.7 server and the reverse.

1. Decide which build the group uses. On GTA V Legacy 1.0.3258.0 and newer, the project's own release notes say to use the RageCOOP nightly together with the ScriptHookVDotNet nightly.
2. Put that build on the server.
3. Have every player download RageCoop.Client.zip from the same release on the RAGECOOP-V releases page, extract it outside the GTA V folder, and run RageCoop.Client.Installer.exe again.

On a GamezServers server, the Version field in the control panel takes latest, nightly or a release number such as 1.5.4.7. Change it, then reinstall the server files. The reinstall writes a fresh Settings.xml, so download a copy of yours from the file manager first and put your changes back afterwards.

The server cannot be reached

A connection that hangs is a network problem, not a mod problem.

• Wrong protocol. RageCOOP uses UDP 4499. A TCP forward does nothing.
• Wrong address. Friends need your public IP, not 192.168.x.x, written as ip:port, for example 203.0.113.25:4499.
• Firewall. On Windows, allow the server: netsh advfirewall firewall add rule name="RageCoop.Server" dir=in action=allow protocol=UDP localport=4499.
• Port changed. If you edited Port in Settings.xml, forward that port instead and tell players the new one.
• Testing from home. Connecting from the same PC or LAN does not test the forward. Ask a friend outside your network.
• Carrier grade NAT. If your router's WAN IP differs from your public IP, port forwarding cannot work. RageCOOP's UseZeroTier option is one way around it, and hosting without port forwarding lists others.

The router steps are in how to port forward a game server.

No F9 menu, or GTA V crashes on load

If the RageCOOP menu never appears, the client is not running. RageCOOP is a ScriptHookVDotNet script, which is loaded by ScriptHookV, so the chain breaks at the weakest link:

1. ScriptHookV out of date. After every GTA V patch, ScriptHookV needs an update for the new game build, and until then it refuses to load. Get the latest from dev-c.com.
2. ScriptHookVDotNet too old. RageCOOP needs 3.6.0 or later, and the nightly SHVDN on recent Legacy builds.
3. .NET Framework 4.8 missing. Install the runtime from Microsoft.
4. Wrong edition. RageCOOP is built for GTA V Legacy. The Enhanced edition is a different executable.
5. Menu key changed. The default is F9. A player who changed MenuKey in the client settings needs their own key.

Kicked after joining

Two server settings kick players on purpose:

• MaxLatency (default 500 ms). Players far from the server, or on bad Wi-Fi, get kicked when their ping spikes over it. Raise it to 800 or 1000 for groups spread across continents.
• KickSpamming with SpamLimit (default 100). A player who spawns more than 100 entities, which trainer mods make easy, gets kicked. Raise the limit for a sandbox server, or turn KickSpamming off if you trust everyone.

KickGodMode is off by default. If you turned it on, god mode trainers get people kicked too.

Server missing from the list

The Servers list in the F9 menu only shows servers that announce themselves.

1. Set AnnounceSelf to true in Settings.xml.
2. Make sure MasterServer is https://masterserver.ragecoop.com/. Older config files point at masterserver.ragecoop.online, which no longer answers, so the server never registers.
3. Restart the server.

Private groups do not need the list at all. Server IP plus Connect in F9 works whether the server is announced or not.

When nothing above helps

Check the server log, RageCoop.Server.log, next to the server program. With the default LogLevel of 0 it is verbose, and new handshakes, joins and errors all show up there. Then check the player's own logs in the GTA V folder: ScriptHookV.log and ScriptHookVDotNet.log show whether the client scripts loaded.

Skip the network side

Most of the trouble on this page is ports, firewalls and home connections. A GamezServers RageCOOP server has its own address with no forwarding, writes the correct port into Settings.xml for you, and lets you set the RageCOOP version from the control panel to match your group's client. You edit Settings.xml in the file manager, watch players connect in the live console, and email support@gamezservers.com if you get stuck. If you are still deciding how to run it, how to host a RageCOOP server covers the whole setup.

FAQ

Why does RageCOOP say a different version is required?

Your client build differs from the server's. Install the client from the same release as the server, or switch the server to the build your group uses.

Is RageCOOP's port TCP or UDP?

UDP. The default is 4499.

Why do I not see the RageCOOP menu?

ScriptHookV or ScriptHookVDotNet did not load, usually because a GTA V update made ScriptHookV out of date. Update both and try again.

Can I join RageCOOP from GTA Online?

No. Load story mode first, then press F9 to connect.

Why was I kicked for high ping?

The server's MaxLatency setting kicks players over 500 ms by default. The server owner can raise it in Settings.xml.