Almost every clan bingo argument traces back to a rule that was never written down. Someone submits a bank screenshot, someone else got the drop twenty minutes after the deadline, two teams finish on the same score, and suddenly the host is making judgement calls under pressure with half the clan watching. None of that is a scoring problem — it's a documentation problem.
This page covers the four scoring systems clans actually use, what each one does to player behaviour, and the rules you need written down before the event opens. There's a copy-paste ruleset at the bottom you can drop straight into your Discord.
Scoring is not just bookkeeping — it decides what players spend their time on. Pick the system that rewards the behaviour you actually want from your clan.
| System | How it works | Rewards | Watch out for |
|---|---|---|---|
| Flat | Every tile is worth 1 point | Volume and consistency | Nobody touches the hard tiles — they cost ten times the effort for the same point |
| Weighted | Each tile carries a point value by difficulty | Effort proportional to reward | Requires you to price every tile, and mispriced tiles get farmed |
| Lines | Tile points plus a bonus for each completed row, column or diagonal | Board strategy, not just grinding | Bonus set too high makes tile values irrelevant |
| Blackout | Big reward for completing the whole board | Sustained team-wide effort | Only viable if the board is genuinely completable in the time given |
For most clan events the sweet spot is weighted tiles plus a modest line bonus. Weighting means a Twisted bow tile isn't worth the same as a Barrows helm, and the line bonus gives teams a reason to think about board position instead of just chasing whatever they happen to be killing. On The Birdhouse you can set per-tile point values, line bonuses, diagonal bonuses and a blackout bonus independently, so you can dial in any of these combinations without doing the maths yourself.
Pricing weighted tiles quickly: assign points in a 1 / 3 / 8 pattern for easy / medium / hard rather than 1 / 2 / 3. The wider spread means a single hard tile actually matters, which is the whole point of weighting. If hard tiles are only worth double, players will always grind two easy tiles instead.
The line bonus is the single most powerful dial you have, and it's the one hosts most often set carelessly. Consider a 5×5 board with easy tiles worth 1, medium 3, and hard 8. A row of five tiles is typically worth somewhere around 15–20 points of tiles.
Diagonals deserve a slightly higher bonus than rows and columns on larger boards, since there are only two of them and they're harder to plan around. Blackout should be worth more than any two lines combined, or nobody will bother going for it.
This is where most disputes happen, so be specific to the point of being pedantic. A proof standard that works:
On The Birdhouse every submission goes into an approval queue rather than marking the tile directly, so an admin sees the screenshot before anything scores. Players who would rather not screenshot manually can use the Dink RuneLite plugin, which posts qualifying drops automatically with a client-generated screenshot at the moment they happen — that removes both the timing question and the editing question at once. The setup is covered on the OSRS Bingo page.
Write these down in a specific timezone with a specific clock time. "Sunday evening" is not a deadline.
Alt accounts are the most common source of quiet resentment in clan bingo, because one person running three accounts has three times the drop chances on the same tile. The standard fix is one declared account per player, registered before the event starts.
If you do allow alts, decide and publish two things: whether alt drops pool into the same player total, and whether an alt can be shared between players. Both answers seem obvious to you and are genuinely ambiguous to everyone else.
Ironmen need separate consideration. Any tile that can be satisfied by buying an item from the Grand Exchange is not the same tile for an ironman. Two workable approaches: keep the board entirely drop-based and skilling-based so buying never helps anyone, or ban purchased and traded items outright for all players — which is cleaner and generally makes for a better event anyway.
You cannot audit everything, and you don't need to. Most cheating in clan bingo is opportunistic rather than determined, so removing the easy routes handles nearly all of it.
What doesn't work: relying on trust alone in a large clan, accepting proof over Discord DMs where nobody else can see it, or letting a single overloaded admin eyeball hundreds of screenshots at 2 am.
Ties are much more likely than hosts expect, especially with flat scoring or small boards. Pick one of these and write it down:
Two principles cover almost every situation. First, the host's ruling is final, and saying that up front is what makes it stick. Second, never change a rule retroactively — if you discover a tile is broken on day three, fix it going forward and leave already-approved proofs alone.
When you do change something mid-event, post the change publicly with a timestamp in the same channel every time. Silent edits, or changes announced only to the team that complained, are what turn a fun event into a grudge. If a tile turns out to be genuinely impossible, swapping it and announcing the swap is far better than letting a dead square sit on the board dragging everyone's score down.
For rejected submissions, give a reason. "Rejected" with no explanation generates three follow-up messages; "rejected, chat message not visible" generates a corrected resubmission.
Fill in the bracketed parts and post it wherever your clan will actually read it. This covers every dispute described above.
Most of the bookkeeping above disappears if you aren't tracking it manually. On The Birdhouse, tile points, line bonuses, diagonal bonuses and blackout are all configured when you create the room and calculated automatically as proofs are approved. Submissions queue for admin review with approve and reject actions, quantity tiles count themselves, and the leaderboard updates live for every player and spectator. Deadlines are enforced by the room rather than by someone watching a clock.
What the platform can't decide for you is the alt policy, the proof standard and the tie-breaker — those are judgement calls about your clan, which is exactly why they belong in a written ruleset before you start.
Four systems are common: flat (every tile worth one point), weighted (points by difficulty), lines (tile points plus bonuses for completed rows, columns and diagonals), and blackout (a large reward for the full board). Weighted tiles with a moderate line bonus suits most clan events because it rewards both grinding and board strategy.
A screenshot showing the drop, the in-game chat message, and the player's username together. Bank and inventory screenshots should not be accepted on their own because they can't establish when the item was obtained.
Most clans restrict players to one declared account, since alts multiply drop chances on the same tile. If you allow them, require every account to be declared before the start and state whether alt drops pool into the player's total.
Earliest completion by approval timestamp is the cleanest option. Most tiles completed, most lines, or highest single tile value also work. The important thing is choosing before the event, because ties happen more often than hosts expect.
That's your call, but decide in advance. If your board has both "any Zulrah unique" and "Tanzanite fang," state clearly whether one fang scores once or twice. The template above defaults to once.
Swap it and announce the change publicly with a timestamp, without touching already-approved proofs. A dead square left on the board is worse for the event than an announced mid-event fix.
With your ruleset written, the remaining pieces are the tiles themselves and the event format:
© 2026 The Birdhouse — Free OSRS Bingo Board Generator