Rules

Here's the whole game on one page. If something's unclear, ask in #hideout on Slack.

Seasons and rounds

  • A season is 8 weeks, split into 4 rounds of 2 weeks.
  • Week one of a round is for building. Week two is for breaking.
  • You can keep working on the same project every round, or start a new one.

Shipping

  • To ship you need a public GitHub repo, a demo link (or steps that get it running in under 5 minutes) and a README that says what the project does and how to run it.
  • Shipping freezes your project at that commit for the round.
  • A reviewer checks it (README included), gives it a tier and approves your hours. If the README is too thin to go on, they'll send it back.

Tiers

  • Tier 1: a static page or a simple script.
  • Tier 2: real features, stored data, logic.
  • Tier 3: logins, a backend, multiplayer, anything with real attack surface.
  • Higher tiers put more points on the line, and earn more if nobody breaks in.

Breaking in

  • In break week you get 3 other people's projects. Never your own.
  • A bug is anything you can reproduce that doesn't work the way their README says, crashes, or is a security hole.
  • Every report is a fix. Open a PR to their repo, then hand it in here with a severity.
  • Only new PRs opened during break week count, and PRs that only change docs or text don't.
  • You can send up to 3 fixes to each project per round.
  • Track your break time in a separate Hackatime project for each target.

Severity

  • Minor: a broken layout on mobile, a dead link, a typo in a key flow.
  • Major: something the README says works doesn't, a crash, data that doesn't save.
  • Critical: a security hole (other people's data visible, XSS, bad password storage), data loss, or the whole thing going down.

Answering fixes

  • The builder has 24 hours to accept or dispute a fix. No answer counts as accepted.
  • A reviewer settles disputes within 24 hours, going by what the README says.
  • A fix counts once the builder merges it. If a builder sits on a good fix, a reviewer can approve it instead.
  • Merges count until 24 hours after break week ends.

Acorns

  • 1 acorn is worth $0.25 in the Shop.
  • Every approved hour of building or breaking gets you 10 acorns.
  • Each round also has a bonus pool with 10 more acorns for every approved hour anyone logged.
  • When the round ends, the pool is split by points. Your bonus is capped at 3 times your hourly acorns for that round.
  • Whatever's left rolls into the next round, and after round 4 it goes to end-of-season prizes.

Points

  • A merged fix gets you 5 (minor), 15 (major) or 40 (critical).
  • Your project starts with 0, 20 or 40 points for tier 1, 2 or 3.
  • Each bug found in it takes off 2, 6 or 16. If you merge the fix yourself, it only takes off half.
  • If nobody gets in and a reviewer agrees people really tried, your project earns 1.5 times its points. That's the Unbreakable bonus.

Fair play

  • Planting bugs for friends, splitting work across accounts or faking hours gets you removed.
  • Never send a fix that adds anything harmful. Builders, read every PR before you merge, especially ones that touch CI, dependencies or install scripts.
  • Reviewers spot-check fixes, and a person checks every critical one.

An example round

Say a round has 100 people and 1,600 approved hours. The pool is 16,000 acorns. Everyone earns 3,200 points in total, so each point is worth 5 acorns.

Maya logs 10 hours building and 6 hours breaking, which is 160 acorns. Two of her fixes get merged, a major (15) and a minor (5). Her tier 2 project had one minor bug, and she merged that fix herself (20 − 1 = 19). That's 39 points, so 195 bonus acorns.

Her round: 355 acorns, about $89 in the Shop, for 16 hours.