RF Help

Get help with your RF Online private server: setup, configuration and troubleshooting from other server owners.

About RF Help

Troubleshooting for RF Online server owners across 2.2.3 and v1.5 - connection errors, database problems, client crashes and configuration mistakes.

Most problems posted here come down to a handful of causes: the client pointing at the wrong address, a database the server cannot reach, a missing runtime library, or a port that was never opened. Search before posting - the same RF Online errors come up often and usually already have an answer.

RF Online private server files centre on the 2.2.3.2 GU build - Xtreme Server Files, the Golden Age repack, Woofe Emu - alongside 2.2.3, 2.1.6, 2.1.5, 2.2.1 and Giga 4 Episode 2 (Kaswynn), dating from 2005. The 2.2.3.2 and 2.1.5 guides require 64-bit Windows and MSSQL 2005 or 2008 Express, with the exgame, rf_account, rf_world and rf_web databases created and ODBC configured before ZoneServer, launcher and webserver start; Giga 4 Episode 2 runs on 32-bit. Launcher emulator setup uses ports 80, 8080 and 10007, and launchers set to 127.0.0.1 are posted. Tools include GameCP panels, DAT and EDF editors, .strs built from zoneserver.h, and client, server and R3 engine source.

Client versions covered here 2.2.3v1.5

Common questions

Why will my RF Online client not connect to the server?
Nearly always the address the client is pointed at. On many builds the server address sits inside a packed client file rather than a plain text config, so it has to be edited there. Check as well that the server is listening and the port is actually open.
Why will my RF Online server not start?
Usually a database it cannot log in to, a missing runtime, or a port already in use by something else. The server console or log normally names the cause on the first failure, and the processes often have to be started in a particular order.
How do I get a useful answer about RF Online here?
Post the RF Online build you are running, the file set you used, the exact error text and what you have already tried. Threads with that detail get answered; vague ones usually do not.
Back