Skip to main content
The Automation tab is the control center for bot deployment. It contains three launch mode cards, an Anti-AFK configuration card, a Quick Config section, and a live Run Monitor panel.

​
Launch Modes

24/7 Alting

Persistent mode — auto-deploys and removes bots continuously to maintain your target server count.

Normal Launch

Launch a fixed number of alts once. No automatic redeployment — ideal for events.

Enterprise Cluster

Permanent multi-PC cluster deployment. Bots never leave. Requires Enterprise license.

​
Mode 1 — 24/7 Alting (Persistence Mode)

The flagship mode. Botify continuously monitors your ERLC private server via the PRC API and keeps it filled around the clock. Deploy Logic:
  • Polls the PRC API /server/players endpoint on each cycle
  • Deploys a new wave of bots when player count drops below deploy_threshold (default: 35)
  • Launches accounts in configurable waves (Batch Size + Wave Delay)
  • Automatically refreshes cookies before each launch wave
  • Auto-minimizes Roblox windows after launch (20 retries, 3-second delay each)
Auto-Remove Logic: Ghost Server Detection: Triggers when Botify tracks 20+ bots but the PRC API reports fewer than 10 visible players — indicating a Roblox server-side ghost state.
  • All tracked bots are killed immediately
  • The server is relaunched from scratch
  • A 300-second cooldown prevents rapid re-triggering
Teleport Error Detection: Botify scans Roblox log files for the following error codes and relaunches affected instances:

​
Mode 2 — Normal Launch

Launch a fixed number of alts in a single wave. Default: 5 accounts.
  • No continuous monitoring or redeployment after launch
  • Auto-remove logic still applies — bots are pulled when server reaches 38–39 players
  • Same wave deployment system (Batch Size + Wave Delay)
Best for one-off fills — events, staff operations, or testing — when you don’t need 24/7 persistence.

​
Mode 3 — Enterprise Cluster

Requires an Enterprise license key or staff Discord role. Locked on Standard plans.
  • Routes bots by Server Code — no PRC API key required
  • Bots remain in the server permanently (no auto-leave logic)
  • This node is registered in the botify_enterprise_clusters MongoDB collection
  • Supports coordinated multi-PC deployments under a single server code

​
Anti-AFK Configuration

Configure the Anti-AFK system directly from the Automation tab card:
See the Anti-AFK System page for full technical documentation including reconnect detection details.

​
Quick Config

Adjust core wave deployment settings without opening the Settings tab:
For 15+ instances, enable Ultra-Low GPU Mode and Working Set Trim in Settings → Performance and Memory & CPU Optimizer.

​
Run Monitor Panel

The live status area at the bottom of the Automation tab:
Clicking Stop terminates all Roblox processes managed by the current session. Accounts remain stored — only the running processes are closed.