FM27: add the club balance and scouting budget to ManagedClub

Open
  • Is something wrong?
#47 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
57/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
data-engineering

Research direction

Start by locating the ManagedClub record and the finance-row parsing and tests; check how the existing finance row differs by club kind. Add optional balance and scouting-budget fields, with None when the build has no layout for them. Done means the managed-club values match the Finances screen and tests reject the other record shape.

Written by the indexing model from the issue text.

Description

No save files or real data
  • I have not attached or linked a save file, screenshot, or any real player data
What is missing

ManagedClub has no current club balance and no scouting budget. The Finances screen shows both. FinanceMonth.balance is a different figure on the same save, so it does not answer this.

How the results compare with the game

The comparisons below used a local build, because 0.8.0 refuses this on FM27. I compared the 13 July save with the Club > Finances screen.

  • ManagedClub.balance matches Overall Balance, to the precision the screen shows.
  • ManagedClub.scouting_budget matches the Scouting Budget.
Suggested approach

Add both fields as optional, with None on a build that has no layout for them. Keep a test that refuses the other record shape, because the finance row differs by club kind.

What remains uncertain
  • I checked one career, from the start of the first season to early August. I will send the saves and matching screens by email.
  • This rests on one club on one date. I have not seen how the balance moves over a month, and balance stays unconfirmed.
  • It covers the managed club only. It does not cover clubs with no finance chain.
Versions
  • fmsave 0.8.0 (main at 418c837), Python 3.13.13, macOS 27.2
  • FM27 build 27.0.0+2486695
Dominant language
Python
Stars
28
Forks
8
Avg merge
42m
Merged PRs (30d)
33

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rhiever/fmsave

All issues in rhiever/fmsave

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.