← Back to the dev blog

DEV BLOG / 18

Create your own player, with a face and a story

The Player Engine grows into a three-step creator, with ordinary game rules around the finished player.

Development post 18: Create your own player, with a face and a story. Pixel artwork from Idleball.
Pixel artwork from Idleball.

The early player engine generated the population behind the league. Now I’m giving the manager a way to use those same systems to make an individual player.

It brings several earlier jobs together: stable identity, code-drawn portraits, backgrounds and ratings. That’s satisfying to see. It also means a mistake in one step has several new places to introduce itself.

What changed since the navigation work

  • Create Player has three steps: Appearance, Background and Abilities.
  • Appearance uses the shared portrait controls. The preview follows the game’s normal drawing rules.
  • Background fields can be edited. Name, position, hometown, college, height, weight and uniform details sit beside editable or generated biography text.
  • Ability allocation has a fixed target. The creator uses an exact Current Ability target of 75 rather than an unlimited ratings slider.
  • Potential and Superstar status are rolled once. The confirmed result is saved; reopening the preview isn’t a way to reroll it.
  • Confirmation makes one in-game payment. It produces a lasting receipt and places the player in a vacancy or league free agency as appropriate. This isn’t a paid microtransaction.
  • Biography routes expanded to forty college stories. The shared generator supports the preview while preserving custom and authored writing.
  • Outlooks use appropriate language. An individual and a collective defensive squad don’t need the same pronouns or career description.
  • The live-game flow has clearer checkpoints. Skip reaches a saved manual Pregame state before explicit kickoff, with a visible next-game countdown.
  • Financial failure has an explanation. Bankruptcy preserves records and a farewell; Joe’s shortfall review points to finance lessons and valid loan quotes.

A preview shouldn’t be a second game

Changing a hairstyle is a preview action. Confirming a player is a permanent transaction. I need those boundaries to remain clear, otherwise a character creator can accidentally become a talent lottery with an unlimited number of free tickets.

The generated biography needs restraint too. Refreshing older generated sentences should leave somebody’s own writing alone. More variety is useful only if the game doesn’t lose the identity it already saved.

Keep the football moving deliberately

The broadcast work adds coach-linked matchups, limited scrolling commentary, exceptional highlights and clearer feedback around required actions. A countdown can show the next kickoff without forcing a manual manager straight through it.

Bankruptcy belongs in the game as a possible franchise outcome. Trapping a solvent team behind an incorrect bill would be a bug. I still need to check those calculations with different balances and commitments.

This is a larger update because older pieces are finally meeting in one place. I’m pleased with that. I still need to make sure the ordinary decisions remain understandable when I’m not standing beside the screen explaining them.

Next is the move toward a phone and a compact desktop view, with all the extra save and navigation work that entails.

All blog posts