A complete OSRS bingo rules template plus drop verification and anti-cheat tips. Set screenshot requirements, prepping rules, and disputes for fair clan events.
Nothing kills a clan bingo faster than a cheating accusation on the final night. Clear OSRS bingo rules and a solid drop verification process protect your event, your prize pool, and your friendships. This guide gives you a copy-ready rules template, a screenshot verification standard, and practical anti-cheat measures so every tile is earned fairly.
Already planning your board? Combine this with our board setup guide and tile ideas for a complete event.
Bingo events get competitive fast, especially with GP prizes on the line. Without published rules:
Publishing rules before the event removes ambiguity and makes your decisions defensible. Post them in your clan Discord and pin them.
Adapt the sections below to your clan. Keep it short enough that people actually read it.
Drop verification is where fairness is won or lost. Set one standard and apply it to everyone.
RuneLite's Screenshot plugin can stamp the in-game time and date onto captures. Require it. A timestamp inside the event window is the single strongest piece of evidence.
| Cheating method | How to prevent it |
|---|---|
| Pre-banking grindable items | Require in-window drop messages, not just "having" the item |
| Reusing old screenshots | Require event-window timestamps via RuneLite |
| Account sharing / buying carries | Declare accounts up front; ban undeclared accounts |
| Photoshopped drops | Require uncropped chatbox + timestamp; spot-check rares |
| Trading completions between teams | Drops count only for the receiving player's team |
| Submitting after the deadline | Hard cutoff; log submission time automatically |
The most effective single defence is automatic submission logging — when the platform records who submitted what and when, most disputes resolve themselves.
Manual verification means a host scrolling Discord, comparing timestamps, and updating a spreadsheet at 2am. It does not scale, and tired hosts make inconsistent calls.
A dedicated bingo platform fixes this:
That turns verification from a chore into a few clicks, and gives you an auditable record if anyone contests a result.
A timestamped screenshot showing the drop in chat, a collection log slot, or an achievement popup, with the player's username visible and the timestamp inside the event window. RuneLite's screenshot plugin is the standard tool.
Most clans require grindable items to be obtained during the event (proven by an in-window drop message), while allowing pre-banked consumables. Decide and publish this before you start.
Require RuneLite timestamps, declare accounts up front, set a hard submission deadline, and use a platform that logs submissions automatically. Spot-check rare drops manually.
Name 2–3 trusted judges before the event and give hosts final say. Require disputes to be raised within a set window so results aren't reopened days later.
Good OSRS bingo rules plus automated drop verification keep your event fair without burning out the host. Get an OSRSHub bingo server to handle screenshot submissions, submission logging, and live standings automatically — so you can enforce the rules with one click instead of a spreadsheet.
Next, lock in your board with our step-by-step setup guide, or get fresh tasks from our OSRS bingo tile ideas.