PT: Pitcher Stamina Bug in Older <5 SP Formats

[lava]

Pitcher stamina appears to be bugged / not working as intended (this post is specifically focused on older, <5 SP formats, but I've seen some other strange behaviors in modern formats)


Typical deadball sequence is 3 SP rotating every 3 days, where each pitcher will be back to 100% by their next start.


Summarized observations:

• Starters gained stamina back at an inconsistent rate, sometimes gaining only 1% over multiple days, sometimes going back to 100% the day after starting
• 1st and 3rd starters appeared to gain each other's stamina at times (e.g., 3rd starter would pitch and be back at 100%, the 1st starter would gain 0 stamina back despite not participating in the game)
• The overall pattern / cycle of starts was the following (each starter was the only pitcher at 100% entering the game):
  • 1st -> 2nd -> 1st -> 2nd -> 3rd -> 3rd -> repeat

Some notes:
- Screenshots below are from the 5L Perfect Draft set in 1914
- No pitch counts, Aggressive Tiredness Hook On
- Rotation was Mikolas, Montgomery, Rea in order
- I started tracking mid tournament, so this is starting from Rea's spot in the rotation
- I manually selected the 100% starter each time, as the game had automatically selected a fatigued starter when I loaded each sim

Game 1 & 2

• After Game 2, Montgomery only gained 1% stamina from 44%->45%
• Rea started 2 days in a row

Game 3 & 4

• After Game 4, Mikolas went back to 100% after 1 day of rest
• Rea gained 0% stamina from 47%->47% despite pitching 3 days ago (I would expect Rea to start Game 5 under normal behavior)

Game 5

• Rea has only gained 1% stamina over 3 games from 47%->48%

Game 6

• Mikolas only gained 1% stamina from 53%->54%
• Rea finally back to 100% stamina after pitching 5 days ago

Game 7

• Back to the beginning of the cycle, Rea starts two games in a row and Mikolas and Montgomery gain 0% stamina
• The order will continue to follow the 1 -> 2 -> 1 -> 2 -> 3 -> 3 pattern mentioned above

[lava]

Following up, any update on this?

[Chris Marquardt]

Thanks for the report, we are currently investigating the bug.