Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.botifymanager.xyz/llms.txt

Use this file to discover all available pages before exploring further.

The Stale Join Watchdog monitors all bot accounts that are tracked as “running” (Roblox process is open) but are not appearing in your ERLC private server according to the PRC API. It catches accounts that launched successfully but failed to teleport or got stuck at a loading screen.

​
How It Works

  1. For every account tracked as “running” by the engine, Botify checks the PRC API /server/players response
  2. If an account is missing from the server list after stale_join_timeout minutes (default: 10 minutes), it is marked stale
  3. An alert dialog is shown listing all stale accounts
  4. Optionally, stale accounts are automatically relaunched with a configurable delay
The watchdog only fires while the engine is running (24/7 Alting or Normal Launch modes). It does not monitor accounts launched manually outside of the engine.

​
Stale Join Alert Dialog

When stale accounts are detected, a dialog appears: 
⚠️  Stale Join Alert

The following accounts have been running for 10+ minutes
but are not detected in your private server:

  •  CoolAlt123   (running 14m)
  •  AltAccount7  (running 12m)

  [Relaunch All]      [Dismiss]
  • Alerted accounts are not alerted again until they are relaunched and go stale a second time — preventing repeated popups for the same account
  • The dialog shows each account’s name and how long it has been running without joining

​
Auto-Relaunch

Configure in Settings → General to automatically relaunch stale accounts without a dialog prompt:
SettingKeyDefaultRange
Not-in-Server Alert Timeoutstale_join_timeout10 min5–60 min
Stale Relaunch Delaystale_relaunch_delay5s2–30s
The relaunch delay staggers relaunches to avoid flooding the server with simultaneous join requests.

​
Jail Manager Integration

The watchdog integrates with ERLC’s jail system via the PRC API:
  • Monitors all active bot accounts for jail status in-game
  • Tracks jail events alongside stale join events in the bot tracker
  • Jailed bots are flagged in the Accounts table and can be optionally relaunched after release
  • Jail events are logged to the Logs tab and botify_logs MongoDB collection

​
Common Causes of Stale Joins

CauseExplanation
Teleport error 524VIP server is full or temporarily unavailable
Teleport error 773Roblox failed to complete the teleport
Teleport error 279Connection error during join
Cookie expired mid-sessionAccount lost authentication during the teleport sequence
Region restrictionServer or account is region-blocked
Ghost serverServer appears active in PRC but is inaccessible
If the same accounts repeatedly go stale, check their Cookie Age indicator in the Accounts tab. Yellow or red cookies should be refreshed immediately.