2026 season

Rules

All of it, in plain language. If something here is unclear or seems unfair, tell me and I'll fix it.

Entering

Scoring

You predict the final score of each NC State game. Score error means both teams' misses added together — if you say 24–20 and it finishes 27–17, that's 3 + 3 = 6.

What you didPoints
Picked the winning team+10
Off by 5 or less+25
Off by 6–10+20
Off by 11–15+15
Off by 16–20+10
Off by 21–25+5
Off by 26 or more0
Exact final score+20 bonus
Submitted a pick that week
Awarded for entering, however it turns out
+5

Winner points are awarded on their own, so a rough prediction on the right team beats a close one on the wrong team.

A perfect week is 60 — 25 for the band, 20 for the exact score, 10 for the winner, 5 for entering. Participation points count toward the season total like any other point. They're deliberately small: 5 can't decide a week between two people who both showed up. What they do is stop a bad week reading as elimination.

The bands are locked for the whole 2026 season. They will not move once entries open. Changing the scoring after points are on the board would retroactively rescore weeks people have already played, and that's the fastest way to make a leaderboard worthless.

Your score prediction is where almost all of it comes from — 55 of a possible 60 in a week. The other 5 is for showing up.

Preseason Bonus — Predict the Record

Before the season starts, predict NC State's final regular-season record — wins and losses across all 12 games. You get 10 points just for submitting a prediction, and 25 bonus points at the end of the season if you nail the exact record.

What you didPoints
Submitted a record prediction
Awarded for entering, however it turns out
+10
Exact final record+25 bonus

It locks before Game 1, so it has to be in before the season starts — that is the whole point of it. Make your prediction.

Weekly winner

Highest total that week — your score prediction plus the 5 for entering. Every game has a weekly winner, all twelve of them, including UNC week.

Winners Circle

The weekly winners of the eleven games before UNC week qualify. On November 28 those qualifiers compete against each other on the North Carolina game for the top prize.

Top prize: a Yeti Roadie cooler.

Season champion

Most points across all twelve games — every week's score prediction plus the points for entering, added together.

The two races are genuinely separate. You can win five weeks and lose the season, or never win a week and take the season on consistency.

Grand prize: a Blackstone 22″ tailgate griddle.

Who can win

Three entries appear in the standings all season for comparison, and none of them can win anything:

EntryWhat it isCan win
ReadersYouYes
The ModelThe model I'm buildingNo
PackPredictionsMe, picking as a fanNo

The site operator and all automated entries are ineligible for prizes. Numbered ranks count readers only, so those three never cost you a place. My own picks lock and reveal on exactly the same clock as everyone else's — I have access to the database, and that shared clock is the only thing that makes my row worth anything.

Ties

Everything below is worked out from what's already recorded — your scores, your combined error, and when you submitted. Nothing is decided by hand, and nothing needs a judgement call from me.

Weekly winner

One prize per week. If entries finish the week level on points, these are applied in order, stopping at the first one that separates them:

  1. Most points that week.
  2. Lowest combined error on the game.
  3. Earliest submission of the pick that counts.

That always ends at exactly one winner, so the weekly prize is never shared.

Changing your pick resets your tiebreak time. You can still change your picks as many times as you like right up to the lock, and it never costs you points. But the pick that counts is your last one, and its submission time is what the third tier reads — so a revision moves you to the back of that queue. It only ever matters if two entries are level on both points and combined error.

Qualifying for the Winners Circle is decided before any of that runs. Everyone tied on points qualifies — the tiebreakers above only decide who receives the prize. So a week can have four qualifiers and one prize. That is correct, not a mistake: the Circle field is set by how well you scored, and the hat is a physical object that has to go to one person.

Wherever a weekly winner is shown, the tie depth is shown with it — how far down the cascade the week went and how many entries were level at that point.

Why this changed on August 19, 2026. Weekly ties used to be co-winners, with every tied entry getting a hat. The prizes are self-funded. At 8 users a duplicate hat cost $30; at 200+ users a tied week could mean five or six hats. The cascade keeps the weekly prize to one hat without changing how points are earned or who qualifies for the Circle. See Updates for the full note.

Season champion

If two entries finish the season on the same points, these are applied in order, stopping at the first one that separates them:

  1. Most points across the season.
  2. Most weekly wins.
  3. Lowest combined error across the season.
  4. Most exact final scores.
  5. Still level? Co-champions.

Winners Circle

The Circle is decided on the North Carolina game alone, so its cascade is shorter:

  1. Most points on the UNC game.
  2. Lowest combined error on that game.
  3. Still level? Co-champions.

Combined error is both teams' misses added together — the same number the scoring bands are built from. The season title and the Circle are unchanged: both are decided by the cascades above, and a tie that survives every tier there is shared rather than settled arbitrarily. Only the weekly prize runs to a single winner.

Why combined error does most of the work. Points come in six bands, so plenty of entries land on the same total. Combined error is the raw number those bands are built from, and it almost never ties — if you were off by 7 and someone else by 9, you both scored +20, but you were closer, and that's what settles it.

When things go wrong

They will. Here's how I'll handle it.

Still to be decided: what happens if the site is unavailable at lock time. I'll publish that policy before entries open rather than inventing it after an outage.