Confirm what goals_outside_box counts on FM26

Open
#48 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
pandas, python
Domain
data

Research direction

Read the issue and the linked CONTRIBUTING.md section, “Reporting a wrong value,” before collecting any observations. Compare a non-managed club player's season value in the game’s player or squad screen with the stored count, without sharing names or exact values. Done means reporting whether the screen’s count agrees with the stored value.

Written by the indexing model from the issue text.

Description

bug help wanted

PlayerSeasonStats.goals_outside_box is being withheld on FM26, as it already is on FM27, after #39. We need to find out what the stored count means before we can return it again.

What we know so far:

  • On FM26 career saves, about one in five non-zero values is above the player's goals for that row, and some are above shots_on_target. It never exceeds shots_outside_box. This shows up in every row kind.
  • For one managed club, the values matched the "Goals From Outside The Box" column on the game's squad screen for every player, and none of that club's rows were impossible.
  • One idea, not yet tested: the count is right for matches the game plays out in full, and means something else for matches it only simulates.

What would help: for a player at a club you don't manage, whose goals_outside_box is above their goals for a season, a description of what the game's player or squad screen shows for goals from outside the box in that season. Please leave out names and exact values.

How to report without sharing real data.

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.