The Discord side of your Minecraft server
The game has its own systems. Discord is where everything around it happens — applications, whitelist requests, downtime notices and the arguments that follow a griefing incident.
What usually breaks in Minecraft servers
- Whitelist and application requests arrive as unstructured DMs
- Nobody knows the server is down until people complain
- Rule disputes turn into arguments with no record of what happened
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.
Structured applications and verification
Application forms and a verification gate replace the DM pile, so new players arrive with the information you actually need.
- /apply
- /verify
- /rolemenu
- /welcome
Announcements that go out on schedule
Scheduled messages and recurring reminders handle restart windows, event nights and map resets without you posting them manually.
- /schedule-message
- /reminder-recurring
- /announce
- /sticky
A record when something goes wrong
Case logs and mod notes mean a griefing dispute is settled by looking it up rather than by who argues hardest.
- /case
- /modnote
- /warn
- /logging
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.