Edited Mark Brown (June 19, 2016 06:32:20 PM)
Due to the amount of information that may become available to players and might affect their play, backups are regarded as a solution of last resort, only applied in situations where leaving the game in the current state is a substantially worse solution.
A good backup will result in a situation where the gained information makes no difference and the line of play remains the same (excepting the error, which has been fixed). This means limiting backups to situations with minimal decision trees.
Backups involving random/unknown elements should be approached with extreme caution, especially if they cause or threaten to cause a situation in which a player will end up with different cards than they would once they have correctly drawn those cards. For example, returning cards to the library when a player has the ability to shuffle their library is not something that should be done except in extreme situations.
Originally posted by john bai:
Is the card draw the only action that prevent a simple back up?
Originally posted by john bai:
Is the card draw the only action that prevent a simple back up?
Originally posted by Bryan Prillaman:john bai
Is the card draw the only action that prevent a simple back up?
Please remember a “simple backup” is a term defined and used by the IPG in fixes. A simple backup is backing up a single action. So the only thing preventing a simple backup here is that a lot more than one thing happened.
Simple backups are used/referenced in HCE and GRV
Replies have been disabled because this topic is closed.