|
|
Post by Phil-Cornwall on Mar 3, 2023 7:43:11 GMT -5
I don't think he said "WOULD" lol.....but I like how you are jumping on the Glenn = Supervillain bus.
|
|
|
|
Post by Glenn-Philadelphia on Mar 3, 2023 9:31:10 GMT -5
From what I have seen so far, it only seems like it was impacting players who were suspended for a large number of games (>10). These will be adjusted accordingly.
As stated prior any future suspensions will be reviewed with the new debug data to see what caused this to happen. It seems like its related to translating games suspended to days (given a teams schedule) and then re-applying that number as games again to determine days missed.
|
|
|
|
Post by Joe-Adirondack on Mar 3, 2023 14:25:49 GMT -5
Days and not games would make a hell of a lot more sense
|
|
|
|
Post by Glenn-Philadelphia on Mar 4, 2023 11:56:00 GMT -5
OK, this section of the code should be fixed now. There is a suspension frequency multiplier that wasn't being calculated correctly because of a set of misplaced parenthesis. The problem really manifested itself with these larger number of games suspended that occurred recently.
Here is an example of how this can occur:
100 + (0 *.25) = 100
the multiplication would occur before the addition
whereas
(100 + 0) *.25 = 25
the addition is handled prior to the multiplication because it is in the parenthesis.
The active suspensions have been reduced significantly and each suspension moving forward is subject to review (using the new debug code) until I have an added level of comfort that things are working as expected.
Apologizes to the impacted GMs. There is no way to take those games back/replay them but for the remainder of this regular season, any future suspension that deals with a player from a team that had a player miss at least 4 games prior to this fix during this season will be subject to a slight reduction if petition is made to the league. This seems to me to be a fair and reasonable, albeit partial, remedy to teams impacted.
|
|
