GoldSync

GoldSync synchronizes configured, code-free Roblox Studio hierarchies with native .rbxm files in a Rojo workspace. Scripts remain owned by Rojo and are rejected from GoldSync roots.

How it works

GoldSync activates when an open workspace contains goldsync.project.json and runs a localhost-only broker on 127.0.0.1:34873. It does not contact an external GoldSync service or collect telemetry.

The broker registers each open GoldSync repository and routes Studio requests through a live session marker generated from Rojo's current session ID. Rojo synchronizes that marker into its connected Studio place, and GoldSync rejects every other Studio window. It detects rojo serve --port overrides and verifies the listener's project name. Studio place IDs and names do not need configuration, and different projects can be served at the same time.

Snapshots are written atomically. Conflicting writes are paused, and configured .rbxm Git conflicts can be inspected through native Base, Yours, Theirs, and editable Result trees in Studio.

When a configured RBXM conflict appears, GoldSync names the project in an actionable notification. Open Conflict Viewer temporarily connects that workspace to Studio for conflict viewing even while Rojo is offline; normal syncing remains paused. This can be disabled with goldsync.conflictNotifications.enabled.

Installation

Install this extension, then restart Roblox Studio once. GoldSync installs and updates its Studio plugin automatically. Use GoldSync: Install Studio Plugin from the Command Palette to repair the installation manually.

Commands

Use the GoldSync status-bar item for logs. The Command Palette also provides refresh, configuration, and log commands.

Workspace trust

GoldSync does not activate in an untrusted workspace because synchronization reads and writes the configured local RBXM paths and launches its bundled localhost broker.