Rules everyone plays
that were never rules
Not one of these appears in any published rulebook. All of them are played constantly. That gap is the whole reason this exists.
The box is lying to you
Every playtime here is recorded twice: what the box claims, and what it actually takes. Filter on the second one.
What should we play?
Nothing fits. Loosen a filter β these are real playtimes, so they run longer than you'd like.
Official rule,
or made up?
Ten rulings. You guess. Most people score worse than they expect, which is the entire point of the registry.
The museum of
rules that never were
Ranked by how certain everybody is. A rule played almost everywhere that appears in no rulebook sits at the top, because that is the one where both sides will fight you.
The family tree
Uno is Crazy Eights wearing a hat. Ludo is Pachisi with the interesting rule removed. House rules cluster by descent, which is why the same arguments keep reappearing in different games.
The same game,
played differently
Some of these rules are standard in one country and unheard of in the next. If you have ever played with someone from elsewhere and both been certain, this is usually why.
Scoring, settled
The same engines the command line uses, imported straight from the repo and running on your device. Nothing is sent anywhere.
Keep score
Round-by-round scoring for whatever you are playing. Saved on your device, survives a refresh, and works with no signal at all.
Add a couple of players to start a scorepad.
The wifi will not hold
The whole registry ships inside the package. No network calls, ever β because the moment you need a ruling is the moment everyone is waiting.
npx @mohitagw15856/rulebook uno "stacking"npm i -g @mohitagw15856/rulebook- 0 dependencies
- 0 network calls
- 68 rulings offline
- 5 scoring engines