The blog, from now on

A short one today, about this blog itself.

Why we went quiet

For most of this year we've posted when something big shipped — a new screen, a new system, a milestone. That pace made sense while the game was being rebuilt piece by piece. But it had a side effect we kept hearing about in messages from players: the changes were arriving faster than the explanations, and half the questions you send us are answerable already — the answers just live in the wiki and the guide, and nobody finds them.

What changes today

From now on, the blog has one job: explaining the game, properly. Each post takes one system or one decision and pulls it apart with the real numbers from the engine — not a stream of announcements, but pieces you can keep and come back to.

• How-to posts — one system per article, pulled apart with the real numbers. That's where the answers go when a ten-minute conversation in Discord deserves to become a page you can keep.
• Notes from the workshop — the occasional look at what we're building next and why.
• Design posts — the reasoning behind choices you can see in the game. There are several we've never properly explained, from stadium growth to why fan mood ignores ticket prices.
• Honest answers — when something is rough, half-built or deliberately unfinished, we'll say so rather than let you discover it.

A post only goes up when it answers something worth answering — we'd rather explain one system well than fill a calendar.

How to use it

We write the posts for players, in the order a player runs into the problem. If you're brand new, start with the first training week. If you've got a season under your belt and want to stop guessing at the details, ask us directly — the Discord is the fastest way. If one manager is asking, a hundred are thinking it.

If you're mid-season right now: there's a press conference you probably haven't answered.