From adding the bot to configuring every module, field by field. Everything is set in the browser; members use it through the Discord menu.
Three steps take you from nothing to a configurable server.
It joins and greets the server with the docs and support links.
Pick the server language, then it creates every channel, wires it to its module and posts the menu. Owner or Administrator only.
After /setup, register the owner account from the link it gives you, then sign in to the web panel to configure everything.
Run /setup in Discord (owner or Administrator only) and pick the server language first. It creates a menu category with these channels named in that language, wires each one to its module and posts the bot interface. Running it again with a different language renames the channels. If no owner account exists yet, it hands you a registration link to claim ownership.
Sign in with Discord. The person who claims the first invite is the owner; they bring in helpers from the Accounts page.
Account tiers control who manages the panel. They are separate from the Discord permission roles below, which control who can use features in Discord.
Full control of one server in the panel. The first owner claims the link from /setup.
Helper access invited by an owner. Every configuration change they save is logged under their name.
Global panel administrator (mainly relevant to self-hosters who run the whole instance).
Map Discord roles to what they unlock. Each group lives with the module it belongs to.
Each module has a master toggle plus its own settings. Turn on only what you need.
How the bot looks and speaks in this server, plus the embed style and staff roles used everywhere.
Chat, voice and invites earn XP that feeds levels, role rewards and leaderboards.
A per-server shop of PvP and utility items bought with XP. Items are created in the global admin Items page; each server enables the system from the Public config page (Items toggle + channel). Requires Public to be on.
Greets new members with a custom message in one or more channels.
Says goodbye when a member leaves, in one or more channels.
Thanks members who boost the server.
Run giveaways with entry rules and winner selection from Discord.
Lets members flag themselves AFK; the bot adjusts their nickname and warns anyone who mentions them.
Routes member feedback into a channel, optionally pinging a role.
Members rate staff; approved ratings drive dynamic roles placed above your staff roles.
Always on. Warn, time out, kick, ban and tempban members from the panel or the staff menu; every action is a numbered case.
Always on. Post as the bot from the Messages tab: plain posts, embeds, rules panels, reaction roles and dropdown roles, with a live preview.
Lets members opt in to notifications for channels you list, from the bot menu.
Lets boosters create a personalized role, placed directly above the Server Booster role so its colour shows.
Handles creator applications and posts TikTok LIVE alerts.
Each member follows their own YouTube, Twitch and TikTok creators and is tagged when they post.
Posts Discord Quest alerts. Quest data is discovered by the accounts the operator has linked, so nothing per-server is needed for alerts.
Forwards messages from a source channel the operator has linked into a channel in this server. Add as many forwarders as you need.
Posts alerts when new free, limited or official Roblox catalog items appear.
The public pages — server statistics, leaderboard, members, and the per-member account (Profile, History, Themes, Guide) — are always on. Items, Minigames, Market, Daily tasks and the server invite are enabled here as sub-toggles.
Members mention the bot to talk to it, or reply to one of its messages to keep going without mentioning again. Set this on the admin panel under the AI tab, not per bot or per server, so every bot and every server shares one configuration. Each member keeps their own conversation in each server. Restart the bot after saving.
Everyone in the channel is heard by one shared session.
A member says "join voice" to the bot in chat. It joins the channel that member is in.
If the member is not in voice, the bot says so instead of joining.
If it is already in a call, it tells the next person it is busy and stays where it is.
A trained wake-word model listens for that exact phrase, so a busy channel never sets it off.
Whoever wakes it holds the conversation. Say you are done to release it for the next person.
It answers, then mutes itself. The mute icon shows whether it is listening.
Moved to another channel, it goes back to whoever invited it. Only they can send it away.
Ask it to leave, or it leaves when the member who invited it leaves, or when the channel empties.
It says a short goodbye out loud, then disconnects. There is no fixed call length limit.
Three optional tools the AI reaches for on its own: searching the live web, reading a page it was linked to, and drawing a picture. Server data needs none of these. Each is a separate URL, model and key on the admin panel under the AI tab, so they can point at different providers. Any OpenAI-compatible gateway works. Restart the bot after saving.
Each tool needs its URL, model and key. Until all three are set the bot is never offered that tool.
Nothing is forced. It searches, reads or draws only when the question calls for it.
Game questions go to your wikis. Web search is for what the wikis do not cover.
Web fetch only opens a URL a member sent or a search result returned, never an invented one.
A generated image is uploaded straight to the channel. In voice it lands in the voice channel chat.
Every key is write-only. Save with the box blank to keep the key you already have.
The AI can read this server's own live data, so "what is in the shop", "who is number one" and "what are my tasks" get real answers instead of guesses. It works as soon as AI chat is on — there is nothing extra to configure.
Members, XP, messages, voice minutes and every module total.
Any metric, any period — XP, chat, voice, steals, gambling.
Prices, what each item does, how long it lasts, what is coming.
This server's own rates, so "how much XP for an hour in voice" is exact.
What is running, the prize and how long is left.
The same guide members read, so answers match the site.
Level, bag, assets, minigames, history, tasks and streak.
Comes with AI chat. No extra URL, model or key.
A module you turn off disappears from the AI too.
Members read their own bag, tasks and history, never anyone else.
Leaderboards, shop, giveaways and quests are open to everyone.
Disguised members stay off every list the AI can read.
The same answers, spoken short instead of listed.
Without this, the AI answers game questions from memory and gets them wrong. Add a wiki and it looks the answer up instead. Set this on the admin panel under the Wikis tab. It applies to chat and voice alike, on every bot and every server.
Open the admin panel's Wikis tab and paste the api.php URL. Any MediaWiki site works, including Fandom.
Test confirms the endpoint answers and is really a wiki, then fills in the name for you.
Members just ask. Full questions work, not only exact page names.
Prices, weights and drop rates come from the wiki infobox, so stat answers are exact.
Skin lists, tables and changelogs come through in full. Nothing is trimmed.
No per-game rules. Ask in any language and it still finds the English page, then answers back in yours.
Repeat questions answer instantly and the wiki is not hammered.
Chat picks up a new wiki on the next message. Voice picks it up on the next call. No restart needed.
A few wiki hosts refuse traffic coming from servers, so the bot gets turned away even though the address is right. A relay fixes this: it forwards the lookup from somewhere the wiki does accept. Only the wikis you point at it are affected, everything else keeps connecting directly.
Some wikis refuse requests from server IPs. Test says the wiki refused, not that your URL is wrong.
Copy scripts/relay.php to any hosting the wiki does accept, often cheap shared hosting, and open it over https.
Edit RELAY_KEY in the file to a long random string. The relay refuses to run while the key is still the default.
Paste the relay address into Relay URL and the same secret into Relay key, then press Test.
With a relay set, Test uses the relay too, so a green result means the whole path works.
The same relay serves any wiki. Set the fields per wiki, and leave them blank for wikis that work directly.
A chat behind the Ask AI button in the bottom right corner of every panel page. Say what you want and it sets it up for you instead of you clicking through the forms. It runs on the AI you set up on the admin panel under the AI tab, with no extra key.
Ask from any page. It opens the builder and fills in text, embeds, buttons, role actions and translations.
Leaderboards, statistics, leveling rules, giveaways and the shop, read live.
Adds a wiki from its address, edits it or switches it off. Panel admin only.
Creates, reprices, schedules or switches off items. Panel admin only.
Flips the switches on the Settings tab. Panel admin only.
It works once AI chat is on with a URL, key and model.
A built message lands in the editor unsaved. You press Save or Send.
One click puts the message back the way it was before the change.
Ask for any languages. Only text you changed is translated again, the rest is kept.
It adds and edits. Deleting stays a click of your own in the panel.
Owner and staff accounts reach their own server and nothing else.
Live server data comes from the running bot.
Two parts: enable the module per server, then create items in the admin catalog. Items are shared across every server that turns Items on.
On the server Public config page, turn on the Items toggle. This unlocks buy and use actions. Public must be on.
Pick an Item Events Channel where steal, bomb, leech, gift and other announcements post. Keep it separate from the level channel. If unset, item events are not announced.
Open the admin Items page and add items. Each needs a name, an effect type, a description and an XP cost. Items live in the catalog and appear in every server that has Items enabled.
Each effect type has its own settings: percentages and cooldowns for steal/bomb, multiplier and scope for boost, spy success chance, and so on.
Limit an item to a date range or to recurring days and times so it only shows in a window. Leave blank for always available.
Show in shop hides or reveals an item without deleting it. Allow use lets you freeze copies members already own. You can also gift copies straight to members.
Members open the shop from the Items button, spend XP, and use items from their bag (which holds up to 50). The Guide tab inside the shop explains every item to them.
With Daily tasks on, your shop sets the economy: the median item cost sizes XP rewards, and item rewards are drawn from items priced near the value of the task or check-in day that earned them. Hidden and disabled items are never handed out.
Members click the Menu button in the menu channel. Every button is always shown — if a feature is off or needs a role, clicking it explains why.
The project is open source under the GNU AGPL-3.0. Run your own instance with Node, MySQL and optional Redis.
Create a database. The app builds its schema and runs migrations automatically on first start. Redis is optional.
Copy .env.example to .env and set APP_NAME, APP_URL, DB_*, MAIL_* and SECRET. Add REDIS_URL if you use Redis.
Run npm install then npm run build. The Node adapter outputs a server bundle.
Start with node build for production, or npm run dev while developing. The schema is created on first boot.
Create a bot in the Discord Developer Portal, add its token and application id to the bots table, then set BOT_ID for the bot process and restart.
Copy .env.example to .env and fill these in.