> ## 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.

# automation

> Configure and run Botify's three launch modes: 24/7 Alting, Normal Launch, and Enterprise Cluster.

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

<CardGroup cols={3}>
  <Card title="24/7 Alting" color="#3b82f6" icon="clock">
    Persistent mode — auto-deploys and removes bots continuously to maintain your target server count.
  </Card>

  <Card title="Normal Launch" color="#3b82f6" icon="play">
    Launch a fixed number of alts once. No automatic redeployment — ideal for events.
  </Card>

  <Card title="Enterprise Cluster" color="#3b82f6" icon="server">
    Permanent multi-PC cluster deployment. Bots never leave. Requires Enterprise license.
  </Card>
</CardGroup>

***

### 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:**

| Player Count Reached | Bots Removed   |
| -------------------- | -------------- |
| 39 players           | 2 bots removed |
| 38 players           | 1 bot removed  |

**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:

| Error Code         | Meaning                       |
| ------------------ | ----------------------------- |
| `524`              | Game/VIP server unavailable   |
| `773`              | Teleport failed               |
| `279`              | Connection error              |
| `restricted space` | Region or account restriction |

***

### 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)

<Note>
  Best for one-off fills — events, staff operations, or testing — when you don't need 24/7 persistence.
</Note>

***

### Mode 3 — Enterprise Cluster

<Warning>
  Requires an **Enterprise license** key or staff Discord role. Locked on Standard plans.
</Warning>

* 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:

| Setting            | Options                              | Description                                                                   |
| ------------------ | ------------------------------------ | ----------------------------------------------------------------------------- |
| **Action Type**    | Space (Jump), W/S (Walk), Zoom (I/O) | Input sent to each Roblox window per cycle                                    |
| **Interval**       | 3, 6, 9, 11, 13, or 15 minutes       | How frequently the Anti-AFK cycle fires                                       |
| **User-Safe Mode** | Toggle                               | Checks for keyboard/mouse inactivity via Win32 `LASTINPUTINFO` before acting  |
| **Auto-Reconnect** | Toggle                               | Detects kick dialogs via pixel sampling (RGB 57, 59, 61) and clicks Reconnect |

<Info>
  See the [Anti-AFK System](/anti-afk) page for full technical documentation including reconnect detection details.
</Info>

***

## Quick Config

Adjust core wave deployment settings without opening the Settings tab:

| Setting            | Key              | Default | Range | Description                                |
| ------------------ | ---------------- | ------- | ----- | ------------------------------------------ |
| **Batch Size**     | `batch_size`     | 5       | 1–15  | Accounts launched per wave                 |
| **Wave Delay**     | `wave_delay`     | 10s     | 1–60s | Seconds between each wave                  |
| **Max Concurrent** | `max_concurrent` | 30      | 1–50  | Hard cap on simultaneous running instances |

<Tip>
  For 15+ instances, enable **Ultra-Low GPU Mode** and **Working Set Trim** in **Settings → Performance** and **Memory & CPU Optimizer**.
</Tip>

***

## Run Monitor Panel

The live status area at the bottom of the Automation tab:

```text theme={null}
● Running   |   Mode: 24/7 Alting   |   Server: 31 / 40   |   Bots: 12
```

| Element              | Description                                                         |
| -------------------- | ------------------------------------------------------------------- |
| **Mode Label**       | Active mode: `24/7 Alting` / `Normal Launch` / `Enterprise Cluster` |
| **Status Indicator** | `Running` (green dot) or `Stopped` (gray dot)                       |
| **Server Count**     | Live player count from the PRC API                                  |
| **Bot Count**        | Number of active Roblox instances currently managed                 |
| **Stop Button**      | Immediately halts the engine and closes all managed instances       |
| **Live Log Output**  | Scrolling real-time event log, filtered to engine activity          |

<Warning>
  Clicking **Stop** terminates all Roblox processes managed by the current session. Accounts remain stored — only the running processes are closed.
</Warning>