A few pages and one change to the bot, all small.
Status and changelog
rowarden.com/status shows whether RoWarden is up, checked when you open the page: the dashboard and database, the Discord bot, Sign in with Roblox, payments, email and background work such as syncs and scheduled jobs. Notices from the Status & Maintenance category show below the checks. The health check behind it now also notices scheduled jobs that have fallen behind, which usually means a worker or cron stopped.
rowarden.com/changelog lists every release, newest first, with the same notes you see in Release Notes here, for people who don't have a forum account.
About, Compare and pricing
About says who is behind RoWarden (one developer), how to reach me, and what RoWarden asks of Roblox and of you. It only uses Roblox's official Open Cloud and sign-in, never asks for your password or cookies, and you choose what permissions an API key has and can remove it at any time.
Compare looks at Hyra, RoWifi, Bloxlink, RoVer, Neo Shift, SCNX and the free in-game admin systems: what each is for, what it costs as listed, and where RoWarden fits.
The pricing page has a short "Who needs Plus?" section, and the founding studios offer: 25 spots, 60 days of Plus and no card needed, for groups and studios with a staff team who will tell me honestly what didn't work. Feature pages also have their own preview images now.
Bot invites ask for Administrator
Every invite link for the RoWarden bot now asks for the Administrator permission: the one from an experience's settings, the community server link, the public verification link and the invite for custom bots. The public verification link used to ask for five separate permissions.
Roles, nicknames, log channels, stats and support alerts all need different permissions, and every new feature that needs one more would mean asking every server owner to re-invite. With Administrator from the start, new features work in servers that already have the bot.
- Giving a bot Administrator is a lot of trust. RoWarden only acts through the commands and features you set up for your server.
- Discord's role hierarchy still applies. The bot can only manage roles below its own, so keep its role above the roles it should sync.
- Servers that added the bot earlier keep the permissions they gave it, because Discord doesn't let a bot raise its own. To use new features there, give the bot's role Administrator in Server Settings → Roles, or invite it again.
If you'd rather not give a bot Administrator, tell me why in Feature Requests.