Attendance from screenshots
Upload a rally screenshot for an open boss attendance window and review high-confidence roster matches before applying them.
Screenshot intelligence
Turn guild screenshots into reviewable records
ForgeKeep uses OCR where guilds already have evidence: in-game screenshots. Attendance scans read rally member lists and match them against the guild roster, while Combat Power scans read a member’s own screenshot before updating their profile. Low-confidence reads, unmatched names, and unusual changes stay reviewable instead of silently changing the record.
Dashboard field guide
See ocr scanning in motion.
A sample view of the ForgeKeep dashboard, with the exact records and handoffs this feature is designed to keep together.
Why it matters
Replace disconnected updates with a reviewable workflow.
Combat Power updates
Let members submit a Combat Power screenshot from the web or Discord without allowing the image name to choose whose profile changes.
Confidence-aware review
Surface OCR confidence, match confidence, unmatched reads, and flagged changes for the right officer to verify.
Operational flow
How the workflow fits together
- 01
Upload the evidence
Submit a rally screenshot for attendance or use /cpupdate image:<screenshot> for a Combat Power update.
- 02
Read and match
ForgeKeep extracts visible names or values, matches them to the authorized guild context, and records confidence signals.
- 03
Review and apply
Officers review uncertain attendance matches and flagged changes before the confirmed result updates the dashboard record.
Related guild operations
Start with your current operation
Bring ocr scanning into the same guild record.
Create a workspace, invite the right officers, and migrate one workflow at a time. Private guild data stays behind application authorization.