What it does, and what it will not do
How the nicknames update, the roles land and the bans stick
Everything below is either a rule CheckRo enforces or a line it refuses to cross.
- No roadmap language
- No number about our own size
Because we do not have one worth quoting.
One Roblox account, one Discord link, enforced
The link table holds the Roblox user id under a uniqueness rule. A second Discord account attempting to claim an already linked Roblox account is not scored, weighed or flagged. It is refused, and told exactly why.
No threshold anyone can tune.
No quiet retraining that changes the answer next month.
The same input gives the same answer.
The reason is a sentence rather than a confidence score.
Leaving, and coming back
Any time
Unlink whenever you want
It is your account and your link, and nothing about removing it is punished.Immediately
The same Discord account can re-link
Changing your mind twice is not suspicious behaviour.15 days
A different Discord account waits
This is the whole anti-cycling mechanism, and it is the only waiting period in the product.
Five answers, and one of them is “we could not check”
When CheckRo looks up a Roblox account, the flow can end in five distinguishable places, and they are never collapsed into a single failure screen.
We found exactly your account.
The normal path.
We found several that look close.
You pick, we do not guess.
We found nothing under that name.
Stated as a fact about the search, not as an accusation.
We could not check.
Roblox was slow, unreachable or rate limiting us. Nothing has been decided and your turn is still open.
We refuse, and here is the rule.
A structural no, in plain words, with the route to contest it.
Why the fourth one has its own colour
A network failure read as a verdict tells someone they were turned away when nothing was decided at all. On our screens that state is cyan and carries a signal meter, never red and never final. It means our side fell over, and it says so.
Where CheckRo differs from a verifier on its own
We only compare against what a bot documents about itself. That keeps this table short, and it keeps it true.
| Behaviour | CheckRo | Some verification bots |
|---|---|---|
| Verifies a Roblox account | Yes | Yes |
| One Roblox account, one Discord link | Yes, enforced by the database | No. One Roblox account can be verified on more than one Discord account |
Scroll the table sideways to see every column
Some verification bots let one Roblox account verify on many Discord accounts.
One popular bot's own docs say so
“users can verify as the same Roblox account on multiple Discord accounts, so it's possible they have multiple accounts in your server.”
If that stops being true, this table changes.
Why CheckRo
Bans that stick
When staff ban a verified member, their Roblox account goes on your server's list, so a new Discord account cannot verify with it. On by default for new servers.One Roblox account, one Discord link
A rule in the database refuses the second link. It holds even when two people try at the same moment.Every flag says why, and can be appealed
Staff read the reason in plain words. The member can run /appeal, and a person on your team answers.Sign in with Roblox, and nothing tracked
Members verify by signing in with Roblox. No IP addresses are stored and nothing fingerprints a device. The only cookie a member gets is a short-lived one during that sign-in.Risk flags for your staff to review
Choose how new a Roblox account has to be, and how few groups it can be in, before it is flagged for your staff to look at. The one account rule itself has no setting.Free to start
Verification, the one account rule, flags with reasons and appeals are all free. Premium adds extras.
The things CheckRo refuses to do
Some of these are ours. Some are required of any app that touches Roblox or Discord. We do not distinguish between the two in practice, and none of them is a setting.
No stored IP addresses, tracking cookies, user agents or device fingerprints
Roblox tells third party apps not to fingerprint users and not to combine Roblox data with data from outside sources.No identity beyond the numeric Roblox user id
Usernames change. The id does not, and it is the only thing we key on.No cross-server ban lists and no shared reputation
What happens in one server stays in that server.No cold direct messages
CheckRo replies where you spoke to it.No Roblox password, ever
Verification reads a public profile, which is the only thing it needs.No data we do not need
The audience here skews young, and the safest record is the one that was never written.
What running it is like
Setup
One command
Invite the bot, run /checkro setup, pick the verified role. That is the configuration.Backfill
The queue heals itself
Members who verified before you chose a role are granted it automatically once you choose one. Nobody has to run anything again.Checking
Status on demand
/checkro status tells you what is configured and whether the role can actually be granted.
The classic failure, once more
The CheckRo role must sit above the verified role in Server Settings, Roles. Discord will not let a bot grant a role above its own, and it fails silently. If members verify but never get the role, this is almost always why.
Works
CheckRoVerified@everyoneFails quietly
VerifiedCheckRo@everyone