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 Remote Command system lets you send commands to any registered Botify PC via the botify_commands MongoDB collection — no direct network connection to the target PC required.

​
How It Works

1

Insert Command

A command document is inserted into the botify_commands MongoDB collection, targeting a specific PC by target_pc name.
2

Node Polls

The target Botify instance polls botify_commands every few seconds and finds the pending command.
3

Auth Verification

The node verifies the auth_token matches its command_token. If it doesn’t match, the command is silently rejected.
4

Execution

The command is executed on the target PC.
5

Audit Log

Result is written to botify_command_history. The command document is removed from the queue.
All commands require a valid auth_token matching the target node’s command_token. Invalid tokens are silently rejected and logged.

​
Command Reference

​
Engine Control

CommandActionParameters
start_247Start 24/7 Alting mode—
start_normalLaunch N alts (Normal Launch)count (default: 5)
stopStop the current engine and close all bots—
restartRestart the Botify EXE entirely—

​
Account Management

CommandActionParameters
kill_accountKill a specific running Roblox instanceusername (required)

​
Diagnostics

CommandActionResponse
screenshotCapture screen and upload to botify_screenshotsBase64 PNG stored in MongoDB
system_statsReturn CPU, RAM, disk, and instance statsJSON stats object

​
UI Control

CommandActionParameters
lockDisable the Botify UI on the target PC (freeze all controls)—
unlockRe-enable the UI after a lock command—
broadcastDisplay a notification banner in the Botify appmessage (string), from (string)

​
Command Document Format

{
  "target_pc": "MainPC",
  "owner_id": "123456789012345678",
  "auth_token": "<32-byte-hex-token>",
  "command": "start_normal",
  "params": {
    "count": 10
  },
  "timestamp": "2026-05-20T12:00:00Z"
}

​
Example Commands

{
  "target_pc": "MainPC",
  "owner_id": "123456789012345678",
  "auth_token": "<your_auth_token>",
  "command": "start_247"
}

​
system_stats Response

{
  "cpu_percent": 45.2,
  "ram_total_gb": 16.0,
  "ram_used_gb": 8.3,
  "ram_percent": 51.9,
  "disk_free_gb": 120.4,
  "roblox_instances": 12,
  "roblox_total_ram_mb": 960
}

​
Audit History

After execution, every command is logged in botify_command_history: 
{
  "pc_name": "MainPC",
  "owner_id": "123456789012345678",
  "command": "start_normal",
  "params": { "count": 10 },
  "result": "success",
  "executed_at": "2026-05-20T12:00:05Z"
}

​
Security

  • auth_token is a 32-byte random hex string generated on first run, stored in botify_nodes
  • Commands without a matching token are silently rejected — no error is returned to prevent enumeration
  • The lock command disables all UI controls on the target PC — useful for preventing interference during automated runs
  • owner_id verification is optional but recommended for an additional layer of access control