Game Clients
Which game client each RF Online server here speaks to, the exact build behind the ones where a version number is not enough, and why a client from one version cannot talk to a server from another.
One Server, One Client
Every RF server here is built against a single game client, and it speaks that client’s language and nothing else.
| Server | Game client |
|---|---|
| RF Online 4.15, Age of Patron | Version 4.15 |
| RF Online 2.2.3.2, Golden Age | Episode 2.2.3.2 |
| RF Online 2.1.6, Secret of Holystone | Episode 2.1.6 |
| RF Online 2.1.5, Red Army | Episode 2.1.5 |
| RF Online Giga 4 Part 2 | Giga 4 Part 2 |
| RF Online 1.0.5 | Version 1.0.5 |
| RF Online 1.5 | GamesCampus 1.5b |
The client is a program we do not control and cannot patch, so the server has to say exactly what that client expects, byte for byte, for the version it happens to be.
We Do Not Ship One
No RF release here contains a game client. The client is the one you already own and installed to play, and the server is the part we wrote. Gate to Heavens works the other way round: its client comes inside the release, because it is ours to give away.
You do not need anything else from us to make your copy work. There is no patched executable, no loader and no replacement binary in any of our archives.
1.5 Needs One Specific Build
For every other row in that table, naming the version identifies the client completely: an Episode 2.1.5 client is an Episode 2.1.5 client, whoever you got it from.
1.5 is the exception, and it is worth knowing before you go looking for a copy. Three different game clients call themselves RF Online 1.5. They are separate builds rather than copies of one, they disagree with each other about what to send, and only one of the three is supported here: the retail GamesCampus 1.5b client.
| File | RF_Online.bin |
| Build date | 2013-03-13 |
| Size | 10,153,352 bytes |
| MD5 | 04f83be3a212582224d379dad655352f |
The build date is the one the file itself carries, which survives copying and installing where a file’s timestamp on disk does not. If the copy you have reports those numbers, it is the build the server was written against.
The other two 1.5 clients, a Korean build from 2012 and an English one from later the same year, are not supported and are not expected to work. They are different programs that happen to share a version number, and nothing more than that is meant by leaving them out.
Versions Are Not Interchangeable
An RF client from one version cannot talk to a server from another. There is no partial result and no login screen you get past first: the two disagree on the shape of the very first message.
That is why these are separate servers with separate downloads rather than one server with a setting. Between versions the message numbering changes, the record layouts change, the data tables change, and in some cases the encryption on the wire changes method rather than keys.
So match the client to the server, and read choosing a version before you commit to one.
Pointing Your Client at a Server
You do not edit anything inside the client to do this, and there is nothing to patch. Every RF
release ships rflauncher.exe: copy it into your client folder, run it instead of the game
executable, and it writes what the client needs and starts it already logged in.
The launcher covers the settings file beside it, and installing a server covers the other end.