Custom Battle
War Thunder custom battle operations are gated until the full interface is ready.
Custom Battle must include protected automation health, game-version control, live reports, pending actions, TAS moderation review, PAT operations 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.
Operational writes stay closed unless the authenticated backend runtime approves them.
War Thunder reports require a signed-in Vuplore ID; the backend derives the reporter from the session.
Implementation Notes
Prepared frontend states.
The operations interface still needs final live tests 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 Vuplore-linked ticket and then staff handles internal execution.
Operational Parity
Required before launch.
Active custom battle reports require Vuplore sign-in and 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 automation activity must be logged without exposing credentials.
Public pages must never reveal bot accounts, tokens, internal room detection details, or moderation queues.