The bot for a server that runs on rules
Roleplay servers are the most structure-dependent communities on Discord. Characters need approval, scenes need their own space, and disputes need a record — all of which is done by hand on most servers, by one exhausted admin.
What usually breaks in roleplay servers
- Character sheets arrive in inconsistent formats and get lost
- Scenes clutter the same few channels
- Rule disputes come down to who remembers what
What the bot does about it
Every command below is a real command in the catalog, switched on from the dashboard. Nothing here needs code, and nothing needs a developer.
Character approval as a real process
Application forms collect sheets in a fixed format and route them for approval, with roles granted on acceptance.
- /apply
- /verify
- /role
- /temprole
Space for scenes
Temporary voice and text spaces let a scene have its own room and disappear when it is finished, instead of accumulating dead channels.
- /tempvoice
- /rolemenu
- /embed
- /sticky
Dice, prompts and randomness
Rolls and random pickers handle the mechanics in-channel, and case logs settle the disputes that follow.
- /roll
- /dice
- /pickrandom
- /case
- /modnote
It is still your bot
Whatever kind of server you run, the setup is the same: the Discord application is created on your own account, so the bot carries your name, your avatar and your colors. Members never see UsaTech. You configure it from a web dashboard, and there is no code at any point.