[jmknpk2]

I think a generic undo "anything" button would be an extremely overwhelming task. It would require catching-before-implementing, or temporarily-holding of each action, or recording-in-a-reversable-manner every action that the game performs. Which would affect basically everything the game does (and nearly all the underlying code involved). Not to mention an extreme level of complexity that it might introduce behind the scenes.

The mention of a transaction log in a database is a good analogy. But I think all of the actions that the game performs, especially with underlying files, etc. are too varied to generalize in a database transaction log model, without completely rebuilding the entire game with that goal in mind.

On the other hand, I think the most common situation where people want the undo button is on the in-game roster changes. I think we have all done something like accidentally dropping a relief pitcher onto our backup catcher's lineup slot when the starting catcher has already been expended, leaving us in a heck of a mess. If I try to imagine schemes where this might happen in real life (like assigning the task to a foolish coach or something like that), I come up empty.

I think the ability to have a big green button at the top of the lineup changes screen that says "accept changes" and a red button that says "undo changes" is something that the developers might be able to get their hands around? Seems like isolating just that portion of code and re-writing would not necessarily be a monumental task?

Is version 12 too far ahead to start hoping for something along these lines?

As far as undo for other items in the game, I, personally am satisfied with the ability to make and recover from backups. If I screw up enough, I can just go back to my most recent backup and "do over". Once I overcame the massive learning curve involved with the game, I rarely make a mistake that causes me a big enough headache, except for the in-game lineups. Sometimes I forget to set the scouting budget or something along those lines, but depending on the circumstances the "undo" button wouldn't adequately fix that kind of problem in a simple or straight-forward fashion anyway.