HomeGamesUpdatesPricingMethodology
Steam News3 May 20262mo ago

Baseball Scouter v1.0.1

(The following content is provided by AI translation. In case of any discrepancies, please refer to the Traditional Chinese version.) Adjustment Items Added a manual save button within the Settings menu.

Full notes

Full Baseball Scouter update

Read the full published notes in a cleaner layout. The original post stays linked below.

What changed

2 fixes3 additions3 changes0 removals
  • UI and audio
  • Gameplay
  • Events
  • Fixes
addedAdded a manual save button within the Settings menu.
addedPlayers can now manually save once per week in-game.
changedThe maximum number of save slots has been increased from 10 to 20.
fixedFixed an issue where item information would remain on screen if the Esc key was pressed while hovering over an item in the Event or Data-Item interfaces.
fixedFixed a phrasing error in a specific line during Mercury's final story segment.
changedHowever, during my own playtesting, I encountered a frustrating situation. I already knew the events for the coming week, but I accidentally clicked the wrong option during the opening event. Because of that one mistake, I had to redo all my actions from the entire previous week. It was a very discouraging experience.
maximum number of save slots1020maximum number of save slots increased, buff

(The following content is provided by AI translation. In case of any discrepancies, please refer to the Traditional Chinese version.)

Adjustment Items

  • Added a manual save button within the Settings menu.

  • Players can now manually save once per week in-game.

  • The maximum number of save slots has been increased from 10 to 20.

  • Fixed an issue where item information would remain on screen if the Esc key was pressed while hovering over an item in the Event or Data-Item interfaces.

  • Fixed a phrasing error in a specific line during Mercury's final story segment.

Developer’s Note on Manual Saving

This game was originally designed to discourage a "save-loading" playstyle. My hope was for players to keep pushing forward even if a match is lost or training doesn't reach its maximum value. For this reason, the game initially only featured an auto-save function.

However, during my own playtesting, I encountered a frustrating situation. I already knew the events for the coming week, but I accidentally clicked the wrong option during the opening event. Because of that one mistake, I had to redo all my actions from the entire previous week. It was a very discouraging experience.

Based on these conflicting thoughts, I originally chose to stick with full auto-saving before the game’s launch. I felt that manual saving might tempt players to constantly reload to "min-max" training results or specific player scouts—a way of playing that I feel isn't very fun and goes against the game's intent.

But while fixing the Event UI bug, I had a sudden inspiration: by limiting manual saves to once per week, I could protect the hard work of dedicated players while still discouraging excessive "save-scumming" for random outcomes. So, I decided to add the feature.

That’s the gist of it. I am not a developer who wants to lecture players on "the right way to play." It’s more that I wasn't sure which approach was better, so I’m trying this middle ground first. If there is consistent feedback from players and the reasons are reasonable, I am also open to adjusting the system to allow fully unrestricted manual saving.

Lastly, since the manual save feature utilizes the same process as the auto-save, my internal testing and code review suggest it should work correctly. However, as this feature has not undergone large-scale testing, please do not hesitate to report any issues you encounter. I will fix them as soon as possible.

Thank you for reading and for your support.

Source

Steam News / 3 May 2026

Open original post

Changelog.gg summarizes and formats this update. How we read updates.