Reports with context
Read descriptions, attached saves, output logs and status history. Public visitors see the report description.
Review reports, manage access and keep the game catalogue up to date.
Development updatesSign in with your staff username and password. New accounts require a private invitation from the owner.
Read descriptions, attached saves, output logs and status history. Public visitors see the report description.
Manage keys and catalogue entries through the same operations used by the Versus bot.
Review the full context, attached saves and status history.
Look up a record or issue a key, then use the maintenance controls below.
Search by Discord user ID or an existing script key.
Set the account, subscription and license for a new key.
Grant Developer access in Versus scripts and the launcher. This does not create a staff website account.
Changes apply to the existing record.
Inspect a place record and manage its recorded issue status.
Read the current catalogue record before applying a change.
Invite staff privately and manage access to this workspace.
Choose the username assigned to the new staff account.
Review each account and enable or disable staff access.
Keep the main Versus update and individual game releases up to date.
View public release historyPublish a short summary of the released loader and site changes. The full public changelog stays available below.
Save a draft, review the website and Discord previews, then publish. Each batch can include up to ten games.
Choose an event look, try the preview and set how many rewards are available. New events start off.
Use a unique passphrase for your staff account.