Look into serialization of the action stack

[LeCodex]

Currently games that never empty the stack will never have more than one "starting point" for reverts, which may lead to long delays as the game has to replay every action. Serializing and saving the stack (or finding an alternative method of handling actions) would allow for saves to happen at any point

[LeCodex]

Some of those actions include callback functions for them to be more generic. This makes them very hard to serialize and parse properly
Those could be bundled into new classes that contain the callback

[LeCodex]

Necessary to allow for failed reloads to use a "final state" that doesn't require saving on an empty stack

[LeCodex]

Currently impossible since effects have been reworked to be actions with callbacks