-
Notifications
You must be signed in to change notification settings - Fork 80
Attendance OCR
Screenshot Upload lets you record event participation without typing names. Someone posts the in-game event mail/result screenshots in a channel, the bot reads them, matches the players to your roster, and saves the attendance for you to review and confirm.
It currently supports screenshots from these sources:
| Event | Where to find the screenshot in-game |
|---|---|
| Foundry Battle | Mail → Alliance → [Foundry Battle] Registration Ends and Results |
| Canyon Clash | Mail → Alliance → [Canyon Clash] Solo Participation and Legion X Battle Result |
| Power Rankings | Alliance → Power Rankings |
| Alliance Showdown | Mail → Alliance → Alliance Showdown Ranking |
For Foundry Battle and Canyon Clash, it's recommended to upload both the registration mail and the result mail together - the bot matches who signed up against who scored in order to determine who attended, records their scores, and takes a snapshot of their power/combat power (Foundry/Canyon Registration) all in one go.
You don't need to be technical to set this up. This page will walk you through it.
You'll need a channel to upload the screenshots - creating a dedicated one is recommended.
Once the channel is created, follow these steps:
- Run
/settings, open Attendance, pick your alliance, and choose 📥 Screenshot Upload. - On the Screenshot Upload menu, click ➕ Add Channel.
- Pick the channel where people will post them (e.g.
#attendance).
That's it - the channel starts accepting all supported event types right away. The bot figures out which event each screenshot is on its own, so you rarely need to touch anything else. From the channel's edit screen you can fine-tune:
| Option | What it does |
|---|---|
| 🗂️ Accepted event types | Turn individual events on/off for this channel (all on by default). |
| 📄 Info message / Pin | Posts (and optionally pins) a helper message that explains what to upload. |
| 🔒 Uploaders | Who may upload - anyone with channel access or admins only. |
| 🗑️ Auto-delete screenshots | Removes the uploader's screenshots after the bot finishes reading them, keeping the channel clean. |
| 📝 Edit Keywords | Usually not needed. They act as a filter: if you set any, the bot only processes uploads whose message text includes one of them. Handy when non-event images also get posted in the channel. |
| 🗑️ Remove Channel | Stops processing screenshots here and removes the helper message if present. |
When screenshots land in the channel, the bot does all of this automatically:
-
Capture. Someone posts the in-game event screenshots. The bot reads every image attached. If the channel has keywords set, the message text must include one of them or the upload is ignored.
-
Identify the event. The bot reads the uploaded screenshots in whatever order you sent them until it recognizes one, then works out which event it is (Foundry, Canyon, Power Rankings, Showdown) and whether it's a registration mail or a results mail, and routes the batch to the right reader.
-
Read the text (OCR). It scans each image and pulls out player names and their numbers (points, power, etc.). Misread letters and digits are cleaned up automatically.
-
Match names to your roster. Each name is compared against your alliance's member list to find who it belongs to. Stylized "fancy" letters are converted back to normal ones first, so decorated names still match. For Foundry and Canyon, registered players are matched up with their results.
-
Use what it has learned. Names it can't read cleanly are checked against its memory of ones you've identified before - so a name only needs your help once.
-
Review and confirm. You see the rows and fix anything that needs it (see below).
-
Save. Confirmed rows are recorded as attendance for that event, ready for reports.
- Take the in-game screenshots for one event (see the table at the top for where each one lives).
- Post them together in the upload channel. Include the screenshot header with its timestamp - that's how the bot tells events apart and tells registration from results.
- The bot reads them and posts a review message.
💡 A few rules for clean reads:
- One event per upload - don't mix screenshots from different events.
- Upload the registration and result mail together for Foundry / Canyon.
- Set your in-game interface language to English before screenshotting - other languages aren't supported yet.
- Finish (save) your current event before starting the next upload.
The review lists every player the bot found, with a mark showing how confident the match is. Fix anything that isn't right, then submit:
- Edit a row (dropdown) - correct a misread name or number, or choose the right player for an uncertain match (by name or ID).
- Add Row - add a player the OCR missed.
- Edit Event Info - fix the event's date (for Canyon/Foundry, also the legion and alliance rank). Shows as Set Date for a Power Rankings snapshot.
- Time - set the event's UTC time slot (only appears for Canyon/Foundry events that have one).
- Unmatched: On/Off - filter the list down to just the rows that still need a match, so you can clear them quickly. Appears whenever something is still unmatched.
- Submit - save the attendance for the event.
- Cancel - discard this without saving.
When you edit a row with no/uncertain match, you can replace the name with the player's ID and submit. This will:
- If the ID is already in this channel's alliance, match the row to them directly.
- If the bot doesn't know the ID yet, it looks the player up (like the
/wcommand) and adds them to the alliance, then matches the row to them. - If the ID belongs to a different alliance, it still matches the row to that player but leaves them where they are - it won't move anyone between alliances.
OCR isn't perfect - always give the rows a quick check before submitting. Every correction you make is remembered for next time, so you don't have to keep fixing the same issues.
Once an event is saved, its participation shows up in the normal Attendance reports and player history - the same as attendance you'd mark by hand.
"The bot isn't reacting to my screenshots."
- Confirm the channel is registered under Attendance → Screenshot Upload, that the event type is enabled for it, and that you posted an image (not a link). If Uploaders is set to admins only, regular members can't upload.
"It picked the wrong event."
- Make sure the screenshot's header and timestamp are visible and the in-game language is English. If a specific event is consistently mis-detected, an admin can add a Keyword for it on the channel's edit screen.
"A player didn't match."
- Fix it on the review screen by typing their name or ID - the bot remembers the correction so the same screenshot text matches automatically next time. Make sure the player is actually in the alliance roster.
"Foundry/Canyon results are missing who registered."
- Upload the registration mail and the result mail in the same batch so the bot can pair them.
See also: Bear Tracking for recording bear hunt damage from screenshots.