Wiki & Setup Documentation

Download Bot Full Package

Download the bot package files from either of the mirrors below. The ZIP contains all required configuration, updater, and manager tools.

Extract to Root C:\

Extract the files directly into the root folder of your C:\ drive. Do not nest it under other folders.

Verify Execution Path

Ensure that the Manager executable is located exactly at: C:\Bot Manager RP v2\ManagerBot.exe. If this path is wrong, configuration bindings will fail to load.

Download HWID Grabber Tool

Download the official HWID tool to generate your hardware key.

Run & Get HWID

Open GetHWIDkeyFBH_Protected.exe, fill in your information, and click "Get HWID". Wait until the message shows "Completed".

Retrieve and Place Key File

Send a message to developer @NewBieT on Telegram to obtain your key file. Once received, copy the key file into: C:\Bot Manager RP v2\.

LoginData.txt Column Specifications

Open C:\Bot Manager RP v2\LoginData.txt and populate it. Separate each column using a single TAB (\t) character. Columns 8-13 are optional.

Example Line Formats

Minimal Format (8 columns separated by tabs):

1	1	user@gmail.com	password123	GAUTHSECRET123	eauser@gmail.com	eapass456	EAGAUTHSECRET

Load Account Database

Open ManagerBot.exe, go to the Acc Manage tab, click Load LoginData, then click Create Bot Folder. For any accounts already logged in, check Logged In to skip them, and click Save. Finally, click CreateNewMatchData to bind configurations.

Method 1: Auto Pairing (Recommended)

In ManagerBot, click AutoGetToken. The manager will launch a browser, fill in credentials, and bypass 2FA. Do not move your mouse during this sequence. If it fails, click GenUrl, log in manually via browser, copy the redirected URL, paste it into the manager, click GetToken, and then click PairToken.

Method 2: Manual Pairing by AccountID

If Auto Pairing fails, retrieve your decimal Account ID using our own tool located at C:\Bot Manager RP v2\FBH_GetAccountID_Tool. (Please note that the website psn.flipscreen.games is no longer operational). In the PS4 settings, navigate to Remote Play Connection Settings -> Add Device to get an 8-digit PIN. In ManagerBot, click PairAccID, input the Account ID and PIN, and click OK.

PS4 Console Calibration

To ensure pixel detection and OCR engines read the screen layout correctly, configure these parameters on your consoles:

• System language must be set to English.
• If using an Asian PS4 console, change the button settings so that X is mapped to OK (confirm).
• Ensure Enable Remote Play is checked under connection settings.
• Set the Display Area to Minimum in the screen area settings.
• Your PSN account name and display character set must use standard English letters.

Recommended Host PC Specs

For running large scale operations (supporting up to 32 concurrent PS instances), we recommend:

Overview & Activation Checkboxes

The CustomRP Scheduler automatically starts and stops bots on a per-PS time-based schedule, eliminating the need to launch bots manually. Each PS runs its own independent scheduling loop. Activate the following checkboxes in your Manager dashboard to enable it:

• ✅ Use CustomRP checkbox (isUseCustomRP)
• ✅ Schedular CustomRP checkbox (Schedular2)
• ✅ IsUse (select) checkbox for the target PS
• ✅ IsLoop checkbox for the target PS

Schedule Column & Slot Formats (BotSchedularPlayTime)

Configure the schedule string in your configuration settings. Columns are separated by Tab (\\t) characters. The structure consists of 8 columns: 1 slot name column + 7 day columns (Sunday through Saturday):

sbname\t[Sun]\t[Mon]\t[Tue]\t[Wed]\t[Thu]\t[Fri]\t[Sat]

Time Slot Format: mode_HH:MM-HH:MM

• mode: ScriptMode number (see reference table below).
• HH:MM-HH:MM: Start time – Stop time. (Start and stop times should not use 24:00 or 00:00).
• Multiple slots in one day: separated by a vertical bar pipe |.

Example Config:

💡 sb0101: Every day from 09:00–10:00, run ScriptMode 1 (PlayUnlock, 3 matches).
💡 sb0199: Every day at 00:01–00:02 run mode 31 (Activate digital account); at 10:00–10:01 run mode 32 (Deactivate digital account). Both run exactly once per day.

ScriptMode Reference Table

Modes dictate what workflow the bot executes during the scheduled time window. Prefix the mode number to your time slot (e.g. 22_12:00-15:00).

Special Modes Persistence File

To track if a special script (modes 30-39) has run for the day, the scheduler logs executions in: C:\\Bot Manager RP v2\\SpecialScriptLastRun.txt

File Layout (Tab separated):

sb0199_31\t2026-04-02\nsb0199_32\t2026-04-02

How to Force Re-run a Special Mode:

• Open SpecialScriptLastRun.txt in Notepad.
• Delete the line corresponding to the mode you want to re-run (e.g., delete the sb0199_31 line).
• Save the file. The scheduler will automatically catch up and run the job on the next poll.
• Or, delete the entire file to force reset special modes for all accounts.

Scheduling Priority Flow & Loop Behavior

Every 1 second, the scheduler evaluates active and pending jobs in the following order:

1️⃣ Missed Special (Guaranteed-once mode missed or pending. Runs only when NO bot is currently active on this PS)
       ↓
2️⃣ Active Slot (Regular playtime window is open. Wait if a bot is already active)
       ↓
3️⃣ Idle (No active playtimes. Status shows "NoAcc in this playtime")

Loop State Reference:

Plus / Digital Account Mapping (sb98 / sb99)

Plus accounts (e.g. sb0198) and Digital accounts (e.g. sb0199) do not have their own CustomRP scheduler slots. Instead, they automatically **share the CustomRP instance configuration** of sb{PS}01 on the same PS machine. The scheduler handles this mapping in the background; no extra setup is required.

Important Integration Notes

• Single Instance Enforcement: Only one bot instance runs per PS machine at a time. The scheduler enforces this lock.
• ScriptMode 0: If no mode number prefix is defined in the slot, the bot runs with the default checkbox flags checked in the Manager UI.
• Auto-Exit: The stopTime is automatically passed to the bot executable as a runtime argument. The bot closes itself when the time is reached, eliminating manual process kills.
• API Configuration Forwarding: Key settings (such as API keys and price thresholds) are forwarded automatically from the current Manager config database.
• No Spaces in Delimiters: Ensure your scheduler configuration uses strict Tabs and not spaces. Some text editors automatically convert Tabs to spaces, which will break the scheduler parsing.