Wiki & Setup Documentation

Download Bot Full Package

Download the bot package files from the mirror 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.

Run AutoUpdate.exe

Run AutoUpdate.exe inside the bot folder to update the bot to the latest files.

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-15 are optional.

AccNo Slot Index Rules

The account slot number dictates the role of the profile on the PlayStation console:

• 1: Primary main account. (Must be paired and have LoginedPS checked. Automatically logged in first).
• 2 – 10: Sub accounts on the same console.
• 98: PlayStation Plus sharing account. Uses Plus mode.
• 99: Digital sharing account. Used for digital primary unlock.
• ⚠️ Slot values 11 – 89 are strictly not allowed and will throw errors on database load.

Sbnumber Naming Format

The system automatically calculates the Sbnumber from PSNo and AccNo using the format: sb{PSNo:D2}{AccNo:D2} (padding to 2 digits):

Example Line Formats

Minimal Format (8 columns separated by tabs):

1	1	[email protected]	password123	GAUTHSECRET123	[email protected]	eapass456	EAGAUTHSECRET

With PsnID + RefreshToken (10 columns):

1	1	[email protected]	password123	GAUTHSECRET123	[email protected]	eapass456	EAGAUTHSECRET	PlayerOne	eyJhbGci...

Full with CustomRP configurations (14 columns):

1	99	[email protected]	pass999	[email protected]	eapass	DigiGamer	bc60a7123456	80fd6184abcd1234	abc123RPkey==	0

Load Account Database

Go to the Acc Manage tab, click Load LoginData. For any accounts already logged in on PS, check Logged In to skip them, and click Save to bind configurations.

Old Tutorial Reference

There is also an old tutorial link for more info: docs.google.com/spreadsheets

Method 1: Auto GetToken and Pair (Recommended)

In ManagerBot, select the account row and click AutoGetToken. The manager will launch a browser, fill in credentials, and bypass 2FA. Do not move your mouse during this sequence. Once the RefreshToken is successfully generated, click PairToken to complete linking.

Method 2: Pair URL (Manual Login fallback)

If Auto Pairing fails or if you are configuring from a remote PC:

1. Click GenURL. A secure login URL is automatically generated and copied to your clipboard.
2. Open any web browser, paste the URL, and log into your PSN account manually.
3. Once logged in, the browser page will go blank or redirect. Copy the entire redirect link URL from the address bar.
4. Back in ManagerBot, click GetToken and paste the redirect link. Once the token loads, click PairToken.

Method 3: PairAccID (Pairing via PIN & AccountID)

Ideal for manual pairings and working around automated browser block screens:

• First, fill in the **NPSSO Token** (see the retrieval guide below).
• In the PS console, go to Remote Play Connection Settings -> Add Device to display an 8-digit PIN on screen.
• In ManagerBot, click PairAccID. The bot will automatically query your Account ID from your PSN ID using the NPSSO token, input the PIN code, and complete linking.

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.

Centralized API Management

ManagerBot centrally manages and distributes API cards to idle worker bots. Unlike older versions where bots managed their own connections, this centralized approach provides load balancing and security.

API Slot Setup: To add slots, enter the Site (DGN/UBuy), User ID, and API Key. The system will auto-generate an ID for tracking.

Priority & Looping Controls

• Priority Order: ManagerBot polls API slots from top to bottom. Reorder priority by selecting a row and using the **Move Up** / **Move Down** buttons. Always click **Save API Config** afterward.
• Poll Timeout: Sets the looping interval (in milliseconds) for how frequently ManagerBot queries DGN/UBuy.
• Smart IgnoreHash Routing: If a card is pulled but the assigned bot previously purchased from the exact same client, the system routes the card to a different bot, avoiding spamming identical ignore hashes.

Daily Limit Reset

Define the maximum number of cards a Bot can buy per day for both normal and Cycle (infinite loop) modes. Once hit, the Manager sends a NO_API signal, prompting the bot to rest. Limits reset globally across the entire system automatically every midnight (00:00) without requiring a restart.

Auditing & Fail Reason Mapping

Track logs under the dedicated API Logs window. You can filter historical records by Date (e.g. 2026-04-11.json) and bot name. If a bot fails a purchase, specific codes (e.g. OutBid, Expired, TM_MaxTarget) are logged and reported back to DGN/UBuy.

Worker Engine & Safety watchdogs

• Multi-Buy Loop: In cycle API mode, the bot will rapidly attempt to buy up to 5 consecutive times during a single API burst.
• Smart Expiry OCR: When multiple identical cards are present, the bot uses OCR to verify the card's exact expiration timer on the console screen against the server timestamp.
• Smart Retries: If the expiry time doesn't match, the bot hits D-Pad Right (up to 4 times) to scan neighboring cards, guaranteeing it picks the correct API-listed card.
• Watchdog Recovery: If a worker bot crashes during card analysis, the API lock is automatically forcibly released after exactly 3 minutes.

Advanced Checkbox Functions

Rival Match & PSN ID OCR Verification

On a new PC setup, you should verify if all PSN Online IDs are correctly recognized by the OCR engine. If the OCR misreads a PSN ID, the matchmaker will not recognize the account, preventing bot matchups.

MatchData Re-Generation

Every time you replace accounts, consoles, or edit the LoginData.txt file, you must reload the configurations. Go to the Acc Manage tab, click Load LoginData, and then click **CreateNewMatchData**. If MatchData is out of sync or contains wrong info, bots will fail to run matches.

Why is my new bot account stuck looping in the L2 menu?

Check if the account has console market access unlocked. The bot will always attempt to relist transfer list cards before launching a match. If the console transfer market is locked, the bot will get stuck. Enable ObjectUnlock2 to finish objectives and unlock console market access.

Unlock WebApp Market Workflow: Fresh accounts must complete 2 objectives (New Begin, Venturing Out) via ObjectUnlock2. Afterward, run daily 3 Squad Battle matches (check PlayUnlock, set UnlockMatch = 3 and MatchLimit = 3).

Acc Manage Tab utility

The **Acc Manage** tab is used to load accounts for AccLogin (adding secondary profiles to the PS4 console), automate retrieving decimal AccountIDs from PSNIDs, and simplify clipboard actions for Method 2 browser pairing URLs.

Ticking disableLoop during Pairing

The bot manages pairing configuration files at each individual slot folder level. If you perform manual pairing on a slot while other bot processes are running, always tick **disableLoop** in ManagerBot first to prevent file lock write collisions.

Control Keys

All buttons located in the Control panel send real-time controller simulation commands (like pressing buttons) to all active bots. You can uncheck **Select** for specific PS instances if you want to exclude them from receiving global inputs.