Screenshot Verification

Screenshot verification turns joining your server into a one-step process. A new member posts a screenshot of their in-game governor profile in one of your verification channels, and the bot reads their governor name and alliance tag, gives them the role you mapped to that alliance, and renames them to their exact in-game name.

Tier	Patron
Command	/verification
Who can use	Everyone verifies, Admins configure
Set up on	Dashboard or Discord

How members verify

1. The member opens their own governor profile in Rise of Kingdoms and takes a screenshot (phone or PC, any game language). Cropping to just the profile panel is fine, as long as the green Action Points bar stays in the shot - that’s how the bot knows it’s their own account.
2. They post the screenshot in one of your verification channels.
3. The bot reacts while it reads the image, then replies with the result:
   • Alliance registered - they get that alliance’s role and their nickname becomes their governor name.
   • Alliance not registered - they get your fallback role if you set one, otherwise the bot explains that their alliance isn’t registered and to contact an admin.
   • Someone else’s profile - profiles opened from the map or rankings (the ones with Mail and Chat buttons) are rejected; only the member’s own profile counts.
   • Unreadable or wrong screenshot - the bot asks for a clearer screenshot, or one that includes the Action Points bar.

Replies clean themselves up after a minute or two so the channel stays tidy. Each member can attempt verification a few times per day, with a short cooldown between attempts.

If a member changes alliance later, they can simply verify again - the bot swaps their old alliance role for the new one.

Setting it up

The quickest way is the Verification tab at dashboard.codexhelper.com:

• Enable the feature and pick the verification channels members will post in (up to 10, e.g. one channel per alliance).
• Add your alliance mappings - the tag from the in-game brackets (like 3505 in [3505]Imperial Demons) and the role its members should receive. Fill in the alliance name too: tags are tiny and the bot occasionally misreads one, and the name gives it a second way to match. Symbols in a tag are ignored, so [NV~] and NV are the same mapping.
• Optionally pick a fallback role for valid profiles whose alliance has no mapping (a Visitor role, for example). With no fallback, those members are rejected.
• Choose whether the bot renames verified members and whether it deletes non-screenshot messages posted in those channels.

Changes reach the bot within about a minute. Everything can also be configured in Discord with the /verification settings panel below.

The bot only ever assigns roles from your mapping list or the fallback role. Nothing written in a screenshot can make it assign anything else.

Bot permissions

The bot needs Manage Roles and Manage Nicknames, and the verification roles must sit below the bot’s role in your role list. It also needs to view, send messages, and add reactions in every verification channel (plus Manage Messages if you turn on message deletion). Discord never lets a bot rename the server owner, so owners keep their nickname.

The /verification settings panel

One command runs the whole feature in Discord. It requires Administrator or Manage Server permissions (or the server’s Bot Admin role), and opens a private control panel showing the current state of every setting. Pick an item from its menu to change it:

• Verification on/off - toggles instantly. You need a channel set before enabling.
• Verification channels - pick where members post their screenshots. You can set up to 10 channels; a screenshot posted in any of them verifies the member, so one channel per alliance works fine.
• Alliance roles - list every registered alliance, add one (type the tag and optional name, then pick its role), or remove one. Adding the same tag again updates its role.
• Fallback role - pick the role for valid profiles whose alliance has no mapping. A Remove fallback role button appears when one is set; removing it means unregistered alliances are rejected instead.
• Rename members on/off and delete other messages on/off - toggle instantly.
• Recent verifications - the last 10 attempts, with who verified as whom and why any attempt was rejected.

The panel saves each change immediately - there is no separate save step.

Troubleshooting

• “That screenshot is too blurry or cropped” - ask the member to post an uncompressed screenshot of the profile screen, not a photo of their screen. Crops are fine if the text is sharp.
• “I can’t tell that this is your own profile” - the crop cut off the ownership signals. Ask the member to include the green Action Points bar (potion bottle + green bar) in the screenshot.
• “That looks like someone else’s profile” - they screenshotted another player’s profile (Mail/Chat buttons instead of an Action Points bar). Only their own profile verifies them.
• “Alliance isn’t registered” - add the tag under Alliance roles in /verification settings or on the dashboard, or set a fallback role. Adding the alliance name alongside the tag also lets the bot recover from a misread tag. The bot posts a notice to your server log channel whenever an unregistered alliance tries to verify.
• Roles not being assigned - check the bot has Manage Roles and that the verification roles are below the bot’s role. The bot posts the exact problem to your server log channel.
• Nicknames not changing - the bot needs Manage Nicknames, and can never rename the server owner or anyone with a role above its own.