Custom Battle
War Thunder custom battle operations are gated until the SREC interface is ported.
Custom Battle must use the same operating shape as SREC: bot bridge health, game-version control, live reports, pending commands, TAS moderation actions, PAT bot controls, and clear public support intake. Vuplore will not expose a fake operational interface before those pieces work together.
Operations
Useful without exposing staff tools.
Request help with custom battle setup, session preparation, rules, or player access issues.
EU and NA operational notes are shown publicly only as service availability, not as bot account details.
Bot endpoints require the server-side War Thunder bot API key. Without it, bridge writes are rejected.
Reports and requests go through the Support Center with Custom Battle selected as service.
Implementation Notes
Prepared frontend states.
The SREC operations interface still needs to be ported before staff can run this as a live service.
Attachments or staff queue are being checked before confirmation.
Event operations paused because staffing, region, or platform conditions are not ready.
Sensitive controls are moved to authenticated department workspaces.
Public pages must never show bot credentials, account tokens, or internal queue identifiers.
Support request creates a public ticket and then staff handles internal execution.
SREC Parity
Required before launch.
Active custom battle reports must route to Trust & Safety with claim, resolve, and audit actions.
Game version, bot process state, pending commands, and command results must be visible to Product & Technology.
Player snapshots, command results, and suspicious bridge activity must be logged without exposing credentials.
Public pages must never reveal bot accounts, tokens, internal room detection details, or moderation queues.