Rust based autobumper for discord servers utilizing disboard for server advertisement, this bot doesnt have any special features except automatically bumping your own server.
Youll have to host this bot on your own hardware, but its super duper simple to do so. AWS has t3.micro instances that is more than enough for this bot that either is free or costs $5 a month.
Automating user accounts is a violation of Discord's Terms of Service. This bot serves as a proof of concept, and I cannot endorse its usage. Proceed at your own risk.
- Automatically triggers DISBOARD
/bumpevery ~2h15m - Uses
serenity_selfgatewaysession_id+ raw/interactionsPOST - Optional filter by application via
COMMAND_APP_ID(e.g., DISBOARD302050872383242240)
- Rust toolchain (stable)
- Discord user token (selfbot). You are responsible for the account and ToS implications.
- Target guild and channel where DISBOARD is installed and slash-commands are enabled
- Create
.envinUGPTbumper:
DISCORD_TOKEN=your_user_token
GUILD_ID=123456789012345678
CHANNEL_ID=123456789012345678
COMMAND_QUERY=bump
# Optional: restrict to DISBOARD app only
COMMAND_APP_ID=302050872383242240
# Optional: bump interval (defaults to 2h15m)
DURATION_HOURS=2
DURATION_MINUTES=15
# Optional: random extra minutes added each cycle (0..=JITTER_MINUTES)
JITTER_MINUTES=5- Run locally (fastest iteration):
set -a; source UGPTbumper/.env; set +a
cargo run --manifest-path UGPTbumper/Cargo.tomlThe service will try once on startup, then repeat every configured interval (defaults to 2h15m). Consider adding a small jitter (e.g., +3–5 minutes) when scheduling externally to avoid obvious patterns.
- 400 on search: ensure
COMMAND_QUERYmatches an available slash command in that channel; checkGUILD_ID/CHANNEL_ID. - 400 on interactions: ensure
session_idis obtained (you should see READY in logs). If multiple "bump" commands exist, setCOMMAND_APP_ID.