Most football games start with the same question: how good is this player?
A career game has to answer a harder one: what does this player's life feel like from the inside?
I work on Copero, a free browser football career game. Players start at 16, make decisions through their career, and finish with a shareable career story. Building it has changed how I think about sports games and narrative systems. The interesting part is not the match engine. It is the structure that turns hundreds of small decisions into a story that feels specific to one player.
Here are five lessons from building that system.
1. Model a career as a state machine, not a pile of articles
The obvious way to build a career game is to write a lot of content and show the right page at the right time. That becomes brittle quickly. A transfer decision in season three depends on age, contract, form, club reputation, country and earlier choices. Screens become disconnected and the player notices the seams.
The better model is to treat the career as a state machine:
- The player has persistent state: age, club, contract, form, fitness, reputation and history.
- A season is a sequence of decision points.
- Each decision changes state and writes a memory.
- The final result is generated from the accumulated state, not from a single ending screen.
That structure lets us add content without rewriting the whole game. More importantly, it lets the same event feel different depending on what happened before it.
2. Localisation is not translation; it is context
A football career does not mean the same thing in every country.
An academy decision in Brazil has a different emotional weight from the same decision in Germany. A move to a nearby league may be normal in one region and a life-changing break in another. Supporters care about different competitions. The media asks different questions. Even the definition of a successful season changes.
That is why Copero uses country and league narrative packs instead of one global story translated into several languages. The goal is to make the decision context feel local, while keeping the core game understandable everywhere.
The practical rule is simple: translate the interface, but do not translate away the culture. A culturally neutral game is easy to ship and easy to forget.
3. Keep a run finishable
A career simulator can easily become a spreadsheet with a story attached. More seasons, more stats, more tabs, more systems. The problem is that most players do not begin a browser game with three free hours.
We designed two rhythms:
- a shorter run for people who want a complete story in one sitting;
- a longer career for players who want to follow every season and decision.
The important part is not the number of seasons. It is that the player can always see the finish line. A career should feel like a story with a destination, not an infinite retention loop that punishes you for leaving.
This also affects UI. The current state, the next decision and the likely consequence need to be legible without opening five panels. If the player cannot explain their own career back to you, the system is probably hiding too much.
4. Failure should produce a story, not a dead end
Sports games often treat failure as a reset button. You lose, you reload, you try again.
Career narratives are more interesting when failure changes the story. A serious injury, a bad transfer or a lost dressing room should close one path and open another. The player's final verdict should be able to say something like "talented, but never settled" rather than only "you lost."
That requires the simulation to remember negative events as part of the player's identity, not as errors to be deleted. A career with no setbacks has no shape. The lows are what make the final triumph, or the tragic near-miss, mean something.
5. Shareable output is part of the game design
The end of a run should not be a dead screen with a score. It should be a compact artefact that another person can understand in a few seconds: the player, the clubs, the defining choice, the final verdict.
We treat the result card as part of the game's language, not as a marketing add-on. It forces us to decide what actually mattered in a career. If the card cannot explain why this run was different, the underlying simulation probably did not create enough meaningful variation.
The lesson I keep coming back to
A football career game is not a collection of football facts. It is a machine for producing remembered decisions.
The engine, the art and the localisation all matter, but the core is the relationship between choice, consequence and memory. Once that relationship is clear, adding another league or another event becomes meaningful instead of decorative.
I am building Copero in public and learning as I go. If you are working on narrative-heavy games, browser games or sports simulations, I would be interested to hear how you model player history and consequence in your own projects.
You can try the game at copero.games or grab the short version of the concept from the press kit.
Disclosure: I work on Copero. This post is a build note about the design approach, not an independent review.
Top comments (0)