Add the days and sessions of a training week

Aperta
  • Qualcosa non va?
#46 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
55/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
data

Direzione di ricerca

Start at training(), which the issue identifies as returning weeks, and read how its current training data is represented. Check the existing enum and CodedValue patterns before deciding how to represent days and their three sessions. Done means training weeks expose the days and stored session codes, including unnamed codes; the issue notes that some names and FM26 behavior remain unverified.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

training() returns weeks, but not what happens on each day. The game shows three sessions a day, on a calendar.

How the results compare with the game

The comparisons below used a local build, because 0.8.0 refuses this on FM27. This table needs a change on either edition, but the check below was on FM27. I compared the first team's calendar on the 23 July save with the Training screen.

  • All 21 days from 13 July to 2 August match, for all three sessions of each day.
  • That includes rest, recovery, travel and match sessions.
Suggested approach

Add a days field to a training week, with each day holding its sessions, and a TrainingSession enum whose value is the stored code. CodedValue can then carry a session the enum does not name.

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.
  • Session names come from one screen, and some are cut off there, so a few member names may be incomplete.
  • Some sessions read UNKNOWN on later days, which are past the screen I have. I do not know which sessions those are.
  • The meaning of the day fields is unconfirmed on FM26, because I compared them on FM27 only.
Versions
  • fmsave 0.8.0 (main at 418c837), Python 3.13.13, macOS 27.2
  • FM27 build 27.0.0+2486695
Lingua principale
Python
Stelle
28
Fork
8
Merge medio
42m
PR unite (30g)
33

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di rhiever/fmsave

Tutte le issue di rhiever/fmsave

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.