Minimal fix to the training engine.
There really aren't any minimal fixes in BuzzerBeater.
I hope there is a wide adoptions of tables and parameters, not everything cabled inside the source code
In training, I guess the algorithm should:
- check which is the training
- initiate a list of weights: position [0] is primary, then 100%, others have weight (you can make your list as long as you want, from no secondary -case of FT training- to N)
- take a player
- check played minutes in appropriate role against training
- apply calculation on primary skill, weight 100% * minutes/48:
- cycle for i:=1 to N (number of secondaries), re-applying calculation
Effort to fix: add one secondary to JS training.
May be something more, not too much.