DEV BLOG / 17
Making everyday management easier to navigate
Keeping my place, finding the right screen and knowing whether an action actually happened.

Adding departments and career information made the game deeper. It also made the menus busier.
This update is mostly the work between the larger features. It won’t sound as exciting as a new stadium addition, but being able to get back to the player I was comparing is something I notice every time I use the game.
What changed since the economy and biography work
- Section headers can pin naturally. Long pages keep their context without trapping the whole view behind a fixed header.
- Jump To is searchable. Player, team, historical and finance sections are easier to reach.
- Graphs explain their abbreviations. Exact values have a route alongside the visual summary.
- The Game Center has five tabs and a clearer return. Scoreboard context, strategy crests and Back to Results help tie the views together.
- Contracts have a consolidated index. Role, term, salary, guarantees, bonuses, happiness, boost and contribution scope can be compared.
- Match reports show the financial receipt. Income, expenses and balance distinguish itemized records from older bundled receipts.
- A forfeit is recorded honestly. Legality-gated 0–2 forfeits don’t invent player statistics or income from a game that wasn’t played.
- The Report Bug control has its own pixel creature. The squash interaction stays separate from copying a screen identifier, with accessible alternatives.
- Dynasties can be transferred manually. Export and import include archives, integrity checks, replacement review and interrupted-transfer recovery.
- Joe’s first-launch tour starts before coach creation. Existing historical teams, players and records provide something real to explore.
- Help works from a control. F1 or a deliberate long press requests an explanation; moving away cancels it without firing the normal action.
Back ought to mean back
A long press shouldn’t become an accidental signing. Opening help shouldn’t erase a form. Leaving a report should return to the place I came from.
I’m trying to make those expectations ordinary. Having an explanation for a confusing interaction doesn’t automatically make the interaction good. Sometimes the useful change is simply making the next step visible.
Joe’s help can replay even after a topic has been seen, while automatic guidance stays optional. His links point to the actual destination, so the answer can get me to the figures I need.
Transfers need care
Taking a Dynasty to another installation is a bigger operation than opening a menu. The package needs its history, and replacing an existing save needs an explicit review. An interrupted import should have a recoverable path.
Desktop transfer evidence and provisional Android document access are separate. There’s still platform-specific transfer work to verify. The design doesn’t require cloud sync.
Next I’m making the player engine something the manager can use directly: a custom player with a face, a background and a fixed ability budget.
