Old School Ops

GoMMO Client Patcher

Patches an official RF Online client so it plays on a private server. Which builds it knows, what it changes, how to undo it, and how it keeps itself current.

Applies to RF Online 4.55RF Online 4.15RF Online 2.1.6RF Online 1.5 · updated 2026-10-10
On this page

GoMMO Client Patcher prepares an official RF Online client for a private server. The retail clients were built to run against their publishers' own services, and some stop before the login screen because of a check no private server can satisfy: an expired build date, an anti-cheat service that cannot start, a second copy refused. The patcher recognises the client you give it and switches those checks off.

It is for the official game clients only. GoMMO Client needs no patching.

Getting it

Every RF bundle carries it as tools\GoMMO_Client_Patcher.exe. It is also a download of its own on the GoMMO Client Patcher page: unzip it into a folder you can write to, such as Documents or the desktop. Nothing needs installing.

Patching a client

  1. Open GoMMO_Client_Patcher.exe.
  2. Drop RF_Online.bin, or the folder holding it, on its window, or press Browse for RF_Online.bin. Dropping the file on GoMMO_Client_Patcher.exe itself opens it straight away.
  3. The patcher names the build and switches on the fixes that build needs. Press Patch client.

Start the game from your launcher as usual afterwards.

What it shows you

Each fix has a switch, a line saying whether it is already applied, and a recommended label when your build needs it. What it changes under each fix explains the check it removes and lists every offset in RF_Online.bin it writes, with the bytes before and after, so you can see exactly what happens to your program before you press anything.

A badge at the top says what the file is now:

  • Original: an untouched copy of a build the patcher knows;
  • Patched: every recommended fix is already applied;
  • Modified: a known build that has been changed before, by this patcher or another.

A file that matches no known build is refused, and nothing is written to it.

Undoing it

  • It backs the file up first, as RF_Online.bin.<date-time>.backup beside the original, every time it writes.
  • Restore original puts back every byte the patcher knows about as the build shipped.
  • To go back to an exact earlier copy, rename one of the backups to RF_Online.bin.

The builds it knows

The Game Clients page lists which client each server needs and what the patcher switches off in each. In short: Dragonborn's expiry, Age of Patron's GameGuard checks and expiry, Secret of Holystone's HackShield, one-copy limit and intro movie, and RF Online 1.5's HackShield, its "HS Err 8" box, its intro movies and its monster aura list. It does not recognise the 2.2.3.2, 2.1.5 or Giga 4 Part 2 clients and refuses to change them.

Window mode

On a client that reads its window mode from R3Engine.ini beside it, the patcher can set it to windowed or full screen. Full screen asks Windows for the resolution in the file at your display's current refresh rate, and a client that is refused that mode closes before its first frame. When your display cannot run the resolution in the file, the patcher sets your desktop's own resolution instead and says so.

Program Files

Windows does not let a program write into Program Files without permission. When the client is installed there, the patcher says so and offers Run as administrator, which asks Windows for permission and opens the same file again.

Updates

The patcher checks for a new version when it starts. When one is out, it downloads it beside itself and installs it the next time you open it. A copy in a folder it cannot write to says a new version is out and links to the download instead.

Something here wrong?

Out of date, incomplete, or assuming something it should not. Documentation errors are bugs, and this one arrives tagged and pointed at this page.

Top xp sources

How xp works
Loading…

Open the full search page