Back

FAQ

This page explains every part of the dashboard and how it lines up with the Discord bot. The same server settings, queue, strikes, and rooms are used in both places. A change on the site updates Discord, and a change in Discord shows up here.

Signing in

Log in with Discord. The bot only lists servers that you and the bot both belong to. After login, a session is saved on this computer so a bot restart does not kick you back to the login page. Sign out is the red button on your player card at the bottom of the left sidebar. That drops the session in this browser.

Your card shows your Discord picture and name. The server dropdown above the menu switches which server you are looking at. Only enabled VRChat groups for that server are shown.

Who sees which menu

Everyone who can open the dashboard sees Instances. Extra pages appear from your Discord roles and permissions:

If a button is missing, that Discord role or permission is not on your account for this server.

Left sidebar

The sidebar stays put while the main area changes.

Instances

This is the public board. It lists every enabled group, the rooms that group has open, and the request queue. The line under the title shows the poll timer and whether requests are on. The page refreshes on its own. You do not need to reload the browser. Close times tick down between refreshes.

Queue

Each waiting request shows its place, world, and minutes. When a slot is free, the bot opens the next one. The Discord embed shows the same queue.

Room cards

A card shows the world name, how full the room is, who requested it, and the region once someone is inside. An empty room stays short: it says it is waiting for the first join, and it hides the fuller details until then.

Request instance

Each group has a Request instance button. If you cannot request, the button does nothing and the hover text says why: missing role, request lock, a ban, or requests paused. The form does not open in those cases.

If you can request, a window opens on top of the page. You can drag it and resize it. It does not leave the Instances page.

For each world you pick a favorite or paste a wrld_ id. Leave both empty to use that group’s default world. Then set minutes, region (US, US East, EU, or JP), and instance type. Group, Group+, or Public is only a choice when the server allows it. Otherwise the type is locked and the form tells you which one.

Hosts can add another world and remove one they added by mistake. If the group announces opens, there is a checkbox to post the open in the Discord channel.

Continue does not open the room yet. The window switches to the rules. Agree sends the request and closes the window. Disagree closes it and sends nothing. Agree can only be used once, so it cannot be spammed into several rooms.

A successful request is queued. A notice on the page confirms it, without Discord markup. The same request shows on the Discord board.

Mod

Mods see every enabled group, whether requests are paused, whether opens are announced, the queue, and each live room. This page also refreshes on its own.

These actions are written to the server’s audit channel and to the Logs page.

Strikes

The list is everyone cached for that server, not only people who already have a strike. People with active strikes are sorted first. Everyone else says No strikes. Search matches a display name or a Discord id and updates as you type. A long server shows the first matches and asks you to type more.

Names and pictures stay cached. Someone is removed from this list when they leave the server. Click a person to open their history.

One person’s history

The top shows their name, picture, Discord id, active strikes, how many records exist, and whether requests are locked. Under that is every warning and strike: kind, date and time, who did it, and the reason.

On Discord, a record that has files shows that evidence is on the dashboard. The files themselves stay here.

Logs

This page is this server’s audit log, saved by the bot when an action happens. It does not include the bot’s private log file, and it does not list other servers. The first time you open it, the bot copies up to the last 500 messages from the Discord audit channel if it is allowed to read that channel. After that, the table opens from the saved copy. Filter the box to match the time, action, person, or detail, or pick one action from the list. Choose 10, 25, 50, 100, 150, or 200 rows per page. That choice is remembered in this browser. Previous and Next move between pages. Click a column heading to sort. Time starts with the newest line. Action, By, and Detail start at A when you click them. Click the same heading again to reverse it. A long detail stays short in the table. Click it to open the full text. Refresh reloads the saved rows. If the bot cannot read the audit channel, Setup and this page say so. New actions are still saved here. The newest setup save has an Undo button on that row. It puts the settings back and works once. That undo is logged too, with each value that was put back. An undo row does not get an Undo button. Older save rows do not get one either.

Setup

This is the same configuration as /setup in Discord, split into Server, Requests, Channels, Worlds, Rules, and one page per group. The row of buttons at the top switches sections. Save this server stays hidden until a setting changes, then it appears at the bottom and writes the whole form. The audit log lists each setting that changed, with the old value and the new value. Undo for that save is on the Logs page, on that row only, and it works once. If you try to leave Setup, switch servers, or sign out while changes are not saved, the page stops you and asks before those changes are dropped. A zero on a group limit means “use the server default.” The Account chips at the top are buttons. A server manager (Manage Server) can click one to see that VRChat account’s status and log in with a username and password, enter the 2FA code VRChat asks for (email or authenticator app), re-check the session, log in again with the saved password, or log out and remove the saved login. These are the same steps as /setup in Discord. The password is stored encrypted and is never shown again. Hosts can see the status but cannot change logins. Login tries from the dashboard are limited to a few every 10 minutes so VRChat does not lock the account.

Server

Dashboard rules

Website only. This does not change the Discord rules text. HTML and CSS are allowed so staff can format it. Scripts are removed. The preview under the box is what people see after they press Continue on a request. They still have to agree or disagree.

Each group

The bot can run up to three groups. Group 1 stays enabled. A disabled group is hidden on Instances and Mod.

Bottom of every page

The bar above the footer is VRChat’s status from the bot’s last check: platform status, which saved accounts are online or limited, and when the last poll ran. A green dot is normal. Yellow is a warning. Red is a major or critical problem.

Under that are FAQ, Terms of service, Privacy policy, and the credit line.

Notices

Confirms, warnings, and errors show as cards on the page. They stack instead of covering each other, stay up for about a minute, and can be closed with X or swiped away. A second confirm appears before a strike, a time change, or a delete. The browser’s own popup dialogs are not used.

Developed and Maintained by AncientAnarchist