Old School Ops

Linking a server

Linking the game's server folder so the map shows and installs what the server places, as well as what the client draws, including RF Online placements kept in the server's database.

Every game · updated 2026-10-31
On this page

A game client draws the map; the game's server decides what lives on it. Link the server folder and Studio edits both.

Linking

On the inspector's Server tab, choose Link server folder and pick the folder of the game's GoMMO server, or drop the folder onto the map. Studio checks that it is a server for the same game, then adds the server's spawns, NPCs and regions to the map. The project remembers the link.

The status bar shows Server linked and the server's name. Unlink server hides the server's objects again.

The Server panel on the rail can link the folder too, and runs the server for you; see Running the server.

Without a server

Without a link you can still edit and install everything the client holds. Objects saved into server data are installed only while a server is linked, and the Install dialog says how many files it is leaving out.

  • Spawns and NPCs, with the real monster or NPC at each.
  • Regions and, on RF Online, town zones and ore veins.
  • Server-side settings for a new map, such as its map type.
  • Search across the server's maps in Find on every map.
  • On RF Online, Populate from a map on the Tools panel, which copies another map's monster camps; see Brushes, prefabs and the Tools panel.

Not every game can link a server yet. Studio says so when you try.

Where an RF Online server keeps its placements

Studio reads the server's settings.ini the way the server does, and reads and installs the spawns, NPCs and portals wherever that server keeps them. The link message names the source.

serverplacements are kept in
Dragonborn, Age of Patron, 1.5 and Golden Age, in the default game data modethe server's content database, SQLite or MySQL, one set of rows per map
Dragonborn, Age of Patron and Golden Age in the client game data modethe content database that mode builds
Dragonborn, Age of Patron and Golden Age in Legacy Game Data Modethe server's map files, with Studio's changes in its custom folder; every install also writes the retail spawn files below
every older RF Online versionthe server's map files, with Studio's changes in its custom folder

When the placements are in the database, the Install dialog shows a map's whole set as one row, placement rows of map …, marked server database. A map you have not changed writes nothing. The install is backed up and restored like any file. If the database is missing or has no placement tables, Studio refuses the install and says how to set it up again.

Retail spawn files

On RF Online: Dragonborn, Age of Patron and Golden Age, the Map tab has Also write retail spawn files, off to begin with. Switch it on and Install also writes the map's spawns into the original server file layout, in the folder settings.ini names as LEGACY_PATH (or gamedata-legacy when that folder is outside the server folder), so a server or tool that reads those files gets the same spawns. A server running in Legacy Game Data Mode gets these files on every install whatever the switch says. A spawn's Block setting names the block its spawns are written into.

Blocks you did not change are written back exactly as they were, so installing an unchanged map writes nothing. Legacy Game Data Mode reads the written files back into the same spawns, with two exceptions: a respawn of 0 comes back as 15 seconds, and two spawns of one monster with the same respawn time at one point merge into one. The original zone server has not been tried on a zone Studio wrote. RF Online 1.5 has no Legacy Game Data Mode, so it has no such setting.

Installing to a server

Install writes server files into the server's own custom folder, which the server reads before its shipped data, and the server reads them when it starts. On RF Online servers that keep their placements in the database, a map's spawns, NPCs and portals go into the database instead, and a running server picks them up within a few seconds, guard towers included. Players already on the map see new and moved NPCs straight away.

Known client limitation: RF Online: Dragonborn, RF Online: Age of Patron and RF Online: Golden Age clients have no way to remove an NPC they are already showing. A removed NPC leaves the server at once, but a player already on the map keeps seeing it until they next enter the map. RF Online 1.5 clients are built to hide it straight away, though that has not yet been seen on screen.

Test in game installs, restarts the server only when it has to, and launches the client; see Running the server.

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