CASE 03
minecraft-statusbot
Server status panel in Discord, refreshed every 30 seconds and configured entirely through slash commands.
30s · refresh interval
Context
Players don't open the launcher to find out whether the server is down — they ask in Discord.
Staff answered the same question several times a day.
My role
Built the bot that keeps status, online players, version and ping in an editable panel.
Made everything configurable through slash commands — /setstatus, /setip, /settext — no file editing.
Added dynamic voice channels with player counts.
Documented deployment on Discloud, Render and Oracle Cloud.
Technical decisions
Thirty seconds
Short enough to feel live, long enough to stay under the Discord API rate limit and the queried server's.
Configuration through slash commands
The person running the panel is a moderator, not a programmer. If the task requires editing YAML, delivery failed.
Deployment on three free providers
The bot has to fit what the community can pay: nothing. Three documented paths stop a single provider outage from killing the project.
Outcome
MIT licensed, running on third-party servers.
Panel refreshes with no manual intervention.
Deployment documented for someone who has never deployed a bot.
Stack
- Python
- discord.py
- MIT
Gallery
Next case
04 · desktop-organizer →