OSRS bingo rules, scoring and evidence
There is no single ruleset that suits every RuneScape bingo. A weekend bossing event and a month-long mixed-account competition need different boards. Use this checklist to settle the decisions that most often cause confusion, then make sure your chosen game mode supports them.
Define what a completed tile means
Give each objective an exact item, activity or result and a required quantity. “Get a unique” needs a list of eligible items; “complete a raid” needs any difficulty or participation restrictions. State whether several players can contribute towards the same quantity.
Avoid objectives that overlap without an explicit rule. If one drop could satisfy both “a raid unique” and “a Twisted bow”, decide whether it can count for both before play begins. Moderators should apply the same interpretation to every team.
Choose a scoring system your mode supports
Equal weights keep progress easy to compare: each approved objective contributes the same value. Weighted scoring lets organisers reward longer or rarer hunts more heavily. Weights should be visible before the event, rather than changing after a team gets lucky.
Choose the winner condition alongside the scoring. Completing a line is different from having the most approved points at a deadline. Some modes have fixed progression rules: reaching tile 100, completing a final Prestige challenge or comparing Tycoon net worth. Do not promise a different winner calculation unless you are deliberately tracking it separately.
Set drop eligibility and duplicate rules
Specify whether loot belongs to the person receiving it, the raid group or a team under your event rules. Agree how splits, untradeable rewards and players from different teams sharing a group are handled.
State whether duplicate items count towards quantities, whether collection-log entries obtained earlier are excluded and whether alternate accounts can participate. A sensible default for a fresh-drop event is that only results obtained during the event qualify. Check the stricter timing rules of contract-based modes as well.
Make evidence easy to review
Ask for the player identity, the qualifying drop or completion message, and enough context to identify the result. Decide in advance if you require an event phrase or another timing check. An image of an item already in a bank is usually poor evidence of when it was obtained.
Players should submit evidence against the correct task. Moderators can then review the proof consistently and ask for clarification when necessary. A completed or pending tile is not the same as an approved result; use the approved standings when checking the winner.
Write down deadlines, corrections and ties
Publish the start and finish times with a time zone. Separate the drop deadline from any submission or review deadline, and explain how late evidence is treated. Clarify whether the event may be paused and how organisers will communicate changes.
Select a tie-breaker compatible with your mode before you need it. Also identify who resolves disputes and how mistaken approvals are corrected. Keep rulings consistent and visible to the affected participants. OSRSBingo provides event tools, but your group still needs to agree on its playing rules.
Put your next board together
Create an account to organise your event, choose a game mode and prepare your team’s objectives.
Create your OSRS bingo event