Skip to main content

Record lookup

Checking an account against the record archives.

Module: lookup (on unless switched off). Both commands are set up to work from a DM as well as inside a server, since they're meant to work like a public utility rather than something gated behind a server's own configuration.

Checking one account

/lookup target: SomeUsername

Works with a Roblox username, a Roblox ID, a Discord ID or mention, or a Titanite ID. It works out which you gave it. If it guesses wrong, or you know exactly what you're passing, say so:

/lookup target: 123456789 kind: "discord id"

kind is auto (default), roblox id, roblox username, discord id, or titanite id.

You get four separate panes:

PaneWhat it answers
IdentityWho this is, and which Roblox account is linked
RecordThe RCR archive, and the OSA archive in its own block
RotectorAn external database of accounts flagged for predatory content
LinksThe raw cross-reference, including where sources disagree

They're kept separate on purpose. A single blended "danger score" would take an unreviewed keyword match and launder it into a verdict. Each pane says where its answer came from and how sure it is.

Two things to read carefully:

  • "derived" next to a standing means nobody reviewed it.
  • Rotector's "Unflagged" means nothing has been detected yet. It does not mean safe.

Searching by something other than a person

/rcrsearch query: scamming standing: banned

For when you're checking a pattern rather than a person: everyone banned for a thing, everything in a category, the most recently updated records.

BoxWhat it does
queryName, Roblox ID, or alias. Leave it blank to browse the whole archive
standingbanned, flagged, or watchlisted. Leave blank for everything
categoryFree text, narrows further

The results message has its own buttons and a select menu to page through and re-sort without retyping the command.

A worked example

Checking someone who joined a server and immediately raised concern:

/lookup target: SketchyPlayer123

The Identity pane confirms the Roblox account and its linked Discord. The Record pane shows a banned entry, marked derived — meaning the ban was recorded from a pattern match, not manually reviewed yet. The Rotector pane shows Unflagged, which only means Rotector hasn't looked, not that the account is clean.

Wanting the wider picture, not just this one account:

/rcrsearch standing: banned category: scamming

Every banned record tagged as scamming, most recent first. From here the message's own controls re-sort or filter further, sort by recency instead of relevance, narrow to a different category, without running the command again.

Troubleshooting

What you seeUsually means
"Couldn't read ... as a Roblox username, Discord ID..."It couldn't tell what you gave it. Add kind: and say which.
A pane shows a red dotThat source couldn't be reached. The other panes are still valid, the message tells you which one failed rather than pretending it found nothing.
A pane shows a white dotThat source isn't configured on this bot. Not an error.
"No record" but you know they're documentedCheck the OSA block too. 69 of its 93 records exist nowhere else, which is exactly why it's shown separately.
Both commands still work in a server where nothing else is set upCorrect, that's deliberate.