The process watcher is a background service that runs continuously while Rift CE is open, scanning for activeDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/N3XT3R1337/RiftCE/llms.txt
Use this file to discover all available pages before exploring further.
RobloxPlayerBeta processes at a configurable interval. It tracks which account owns each process, monitors memory usage, detects when a process exits, and can automatically relaunch sessions — making it the core component for unattended, long-running account sessions.
How it works
Every time the watcher ticks, it callsProcess.GetProcessesByName("RobloxPlayerBeta") and compares the result against its internal registry of launched PIDs. For each tracked process it updates the live memory reading and checks whether configured thresholds have been crossed. Processes that disappear from the list trigger disconnect handling or relaunch logic depending on your settings. The StatusChanged event fires at the end of each scan, which updates the account status indicators in the Rift CE dashboard in real time.
When you launch an account through Rift CE, the watcher registers that process ID against the account automatically via RegisterLaunch. Only processes launched through Rift CE are tracked — existing Roblox windows you opened manually are not managed.
Enabling and configuring the watcher
The watcher is enabled by default (WatcherEnabled = true). To adjust settings, go to Settings → Process Watcher.
| Setting | Default | Description |
|---|---|---|
WatcherEnabled | true | Enable or disable the watcher entirely |
WatcherInterval | 5 seconds | How often the watcher scans for process changes |
Setting
WatcherInterval very low (under 2 seconds) increases CPU usage, especially when running many simultaneous Roblox instances. The watcher enforces a minimum interval of 1 second. For most use cases, the default of 5 seconds is a good balance between responsiveness and performance.Watcher features
Auto-close on memory
When
AutoCloseOnMemory is enabled, any tracked Roblox process that exceeds MemoryThresholdMB (default 2048 MB) is killed automatically. Use this to prevent a single runaway instance from exhausting system RAM during long farming sessions.Auto-close on disconnect
When
AutoCloseOnDisconnect is enabled, the watcher watches for a process to exit unexpectedly. It waits DisconnectTimeoutSeconds (default 30 s) before treating the exit as a confirmed disconnect — this gives Roblox’s normal reconnect flow time to complete. After the timeout, the account status is set to Offline.Auto-relaunch
When
AutoRelaunch is enabled, the watcher relaunches an account into the same place and job ID after it closes — whether from a crash, a disconnect, or a memory-triggered kill. The relaunch is delayed by RelaunchDelaySeconds (default 10 s) to avoid hammering Roblox’s join endpoint. Relaunch only fires if a PlaceId was registered at launch time.Live status tracking
The watcher updates each account’s
Status field (InGame or Offline) on every scan tick and surfaces the total count of active tracked processes via ActiveCount. The dashboard refreshes automatically via the StatusChanged event without any manual polling.Settings reference
| Setting | Type | Default | Description |
|---|---|---|---|
WatcherEnabled | bool | true | Enable the process watcher |
WatcherInterval | int | 5 | Scan interval in seconds (minimum 1) |
AutoCloseOnMemory | bool | false | Kill processes that exceed the memory threshold |
MemoryThresholdMB | int | 2048 | Memory threshold in megabytes for auto-close |
AutoCloseOnDisconnect | bool | false | Close the process after a disconnect timeout |
DisconnectTimeoutSeconds | int | 30 | Seconds to wait before confirming a disconnect |
AutoRelaunch | bool | false | Relaunch the account after its process closes |
RelaunchDelaySeconds | int | 10 | Seconds to wait before relaunching (minimum 3) |
Common use cases
Unattended farming: EnableAutoRelaunch with a RelaunchDelaySeconds of 10–30 seconds. If a session crashes or you get disconnected, Rift CE will rejoin the same server automatically without any manual intervention.
Memory-capped multi-instance: Enable AutoCloseOnMemory and set MemoryThresholdMB to a value that keeps your total RAM usage below system limits. Combined with AutoRelaunch, any instance that grows too large is recycled and restarted fresh.
Disconnect detection only: Enable AutoCloseOnDisconnect without AutoRelaunch if you only want the watcher to clean up and mark accounts offline when sessions drop, without automatically restarting them.