How OSRS bingo automatic tracking works. Wise Old Man, RuneLite plugins and screenshot proof compared — what each one can and cannot actually verify.
Every clan that runs a second bingo asks the same question the day after the first one ends: is there a way to stop doing this by hand? Somebody spent the whole event opening screenshots, cross-checking timestamps, and retyping numbers into a spreadsheet, and they are not volunteering again.
OSRS bingo automatic tracking is the answer, but it is not one thing. It is four different mechanisms with genuinely different capabilities, and most of the frustration in this space comes from expecting one of them to do another's job. A Wise Old Man sync cannot see your Zulrah drop. A RuneLite plugin cannot verify a player who does not install it. A Discord webhook does not score anything at all.
This guide explains what each mechanism can actually observe, where each one silently fails, and how to combine them into a board that mostly runs itself. If you have not built the board yet, start with the board setup guide or skip straight to the free board generator.
Old School RuneScape does not have an events API. There is no endpoint Jagex publishes that says "player X received item Y at time Z". Everything described below is a workaround for that single missing feature.
That gives you exactly two families of tracking:
Polling the hiscores. Something asks Jagex's public hiscores what a player's stats and kill counts are, waits, asks again, and reports the difference. This is how Wise Old Man works.
Watching the client. A plugin runs inside RuneLite on the player's own machine, sees game events as they happen, and reports them outward.
Everything else — Discord bots, screenshot channels, submission forms — is transport or proof, not detection. Confusing transport with detection is the single most common mistake in clan event planning. A Discord webhook is a very good pipe and not a tracker.
Wise Old Man is the de facto standard for OSRS group tracking. It polls the official hiscores, stores snapshots, and exposes gains over a time window through competitions and groups.
This makes it excellent for a very specific and very common category of bingo tile: "gain 500k Slayer XP", "kill Vorkath 25 times", "complete 10 medium clues". Those tiles need zero screenshots and zero admin judgement. The number went up, or it did not.
This is the part clans learn the hard way.
It cannot see individual drops. The hiscores know you killed Zulrah 40 times. They do not know whether a tanzanite fang fell. Any tile of the form "obtain X" is invisible to hiscores polling. That is most of the exciting tiles on a typical board.
It cannot see unranked players. A player below the hiscores threshold in a skill simply has no entry, and gains cannot be computed from nothing. This bites low-level and fresh accounts hardest — exactly the members a good board is trying to include.
Snapshots are not instant. Updates depend on when a player's profile was last refreshed. If you start an event at 20:00 and a player's last snapshot was at 14:00, six hours of afternoon grinding can land inside your event window unless you force a fresh snapshot at the start. Always trigger a group update at the exact moment the event opens and treat that as the baseline.
The public API is rate limited, and rightly so. A tool syncing a 60-player group every minute will get throttled. Any platform doing this properly syncs on a schedule with backoff, which means "live" means every few minutes, not every second. If a tool promises instant hiscores updates for a large group, it is either wrong or about to be rate limited.
Wise Old Man is the strongest option for counting tiles and useless for drop tiles. Roughly half a good board is countable, so this alone removes about half your admin work.
A RuneLite plugin sits inside the player's client and observes real game events: a chat message announcing a drop, a collection log slot filling, a loot window closing. It can then fire that event at a webhook or an API.
This is the only mechanism that closes the drop-tile gap. Tools in this space include the community loot trackers and clan broadcast plugins; several bingo platforms ship their own.
Every player must install it, and configure it correctly. This is not a technical problem, it is a social one. In a 40-person clan you will get maybe 25 installs on day one and three people who typed the event key wrong. Your board must work for the other 15.
It is client-side, so it is trust-based. A plugin reports what the client tells it. A determined cheater can send fabricated events. For a friendly clan event this rarely matters; for one with a real GP prize pool, it matters enough that you want a second signal on the high-value tiles.
Plugin availability changes. Third-party plugins live in the RuneLite plugin hub and are maintained by volunteers. Anything you build your event around can break after a game update at the worst possible moment.
It cannot see the past. Install the plugin mid-event and it knows nothing about the three hours before.
Essential for drop tiles, unreliable as your only mechanism because coverage is never 100%. Design for partial adoption from the start.
The oldest method, and the one clans keep coming back to. A player takes a screenshot, submits it, an admin approves it, and the tile flips.
People dismiss this as "manual", but it has two properties nothing else has:
It works for every tile. "Wear a full set of matching armour in the Grand Exchange." "Get a level 3 skiller to a Wintertodt crate." No API and no plugin will ever see those, and they are often the most fun tiles on the board.
It works for every player. No install, no hiscores entry, no configuration. A brand new account on a phone can participate.
The failure mode is not accuracy — it is admin load. A 25-tile board with 8 teams is up to 200 approvals, and if those arrive as raw images in a Discord channel with no structure, one person spends their weekend scrolling.
The fix is not to abandon screenshots. It is to give them structure: submissions attached to a specific tile and player, queued, with an approve/reject action and a rejection reason. That turns a scrolling problem into a clicking problem. Our rules and drop verification guide covers what to require in the screenshot itself.
The universal fallback, and the only mechanism that covers 100% of tiles and 100% of players. Its cost is admin time, and structure is what reduces that cost.
A Discord webhook is a URL you post to, and the message appears in a channel. That is the whole feature.
It tracks nothing. It verifies nothing. What it does is close the loop between something happening and your clan finding out, and that is worth more than it sounds — the single biggest driver of engagement in a clan bingo is people seeing progress happen in near real time.
Use it for:
The trap is wiring raw plugin output straight into a public channel. Every drop from every player, unfiltered, becomes noise inside an hour and people mute the channel — which is the exact opposite of the goal. Filter to event-relevant events only. Our Discord integration guide walks through the setup.
| Capability | Wise Old Man | RuneLite plugin | Screenshot + approval | Discord webhook |
|---|---|---|---|---|
| Skill XP gains | Yes | Yes | Yes, manually | No |
| Boss kill counts | Yes | Yes | Yes, manually | No |
| Clue completions by tier | Yes | Yes | Yes, manually | No |
| Individual item drops | No | Yes | Yes | No |
| Collection log slots | No | Yes | Yes | No |
| "Do something silly" tiles | No | No | Yes | No |
| Works for unranked accounts | No | Yes | Yes | n/a |
| Works with zero player setup | Yes | No | Yes | n/a |
| Resistant to fabrication | High | Low | Medium | n/a |
| Latency | Minutes | Seconds | Admin speed | Seconds |
| Admin effort | None | None | High without tooling | None |
Read the table by column and the conclusion is unavoidable: no single column is all "yes". Every serious setup is a combination.
After the mechanisms, here is the practical recipe. Assume a 5x5 board and a mixed clan.
1. Sort your tiles into three buckets before the event. Countable (XP, KC, clue tiers), droppable (specific items, log slots), and judgement (everything else). A healthy 25-tile board lands roughly 10 / 10 / 5.
2. Point each bucket at the right mechanism. Countable tiles resolve from hiscores gains. Droppable tiles resolve from a plugin or a screenshot, whichever arrives first. Judgement tiles are screenshot-only. Publish which bucket each tile is in, on the board, before you start.
3. Force a hiscores baseline at the start whistle. Not the night before. The gap between snapshot and start is the most common source of "that XP was already banked" arguments.
4. Treat plugin events as submissions, not verdicts, on high-value tiles. For a 1-point easy tile, auto-approve. For the 15-point raid unique that decides the event, let it land in the approval queue with the screenshot attached. This is the cheap answer to the trust problem, and it costs an admin one click.
5. Keep screenshots open for everything, always. The 15 players who never installed the plugin are not cheating and should not be locked out. Screenshot submission is your accessibility floor.
6. Push approved completions to Discord, and nothing else. Approval is the natural filter between signal and noise.
Assembling the above from separate parts means running a Wise Old Man group, a plugin key, a webhook, a submission channel, and a spreadsheet that reconciles all four. That is a real weekend of setup, and it is why most clans give up and do it manually.
An OSRSHub server ships the combination pre-wired: a Wise Old Man sync for countable tiles, structured screenshot submissions with an admin approval queue for everything else, a live leaderboard that updates as tiles are approved, and filtered Discord updates on approval. The sync is rate-limit aware by design, so a large clan does not get throttled mid-event. You define the board and the rules; the reconciliation is not your problem.
It is $12.10 a month, cancel anytime, and the board is live in under a minute. If you just want to design the grid first, the free board generator does that with no account at all.
No, and any tool claiming otherwise is quietly narrowing what counts as a tile. Hiscores polling cannot see item drops, and client plugins require every player to install them. A realistic target is roughly 60–70% of tiles resolving automatically, with the rest going through screenshot approval.
No. Wise Old Man reads the official hiscores, which record skill XP, boss kill counts, clue completions, and activity scores — never individual items. Use a RuneLite plugin or screenshot proof for drop tiles.
Only for plugin-detected tiles. Expect partial adoption and always keep screenshot submission open, or the members without the plugin — usually your newest and most casual players — cannot complete anything.
Force a group snapshot at the exact moment the event opens and use it as the baseline. Any earlier baseline lets pre-event grinding count, which is the most common scoring dispute in tracked bingos.
Hiscores polling is very hard to fake, because it reads Jagex's own data. Client plugins are trust-based and can be fabricated by a determined player. Route high-value tiles through admin approval regardless of how they were detected.
Automatic tracking decides how much of your event you spend playing versus refereeing. Get the buckets right and the mechanisms pointed at the right tiles, and a 25-tile board with 40 players is genuinely manageable by one person.
Next, tighten the rules those mechanisms enforce with the OSRS bingo rules and drop verification guide, or fill your grid from the 60+ tile ideas list — it flags which tiles are countable and which need proof.