Undo Output Control

version 3/110717 by Erik Temple

  • Home page
  • Beginning
  • Next

  • Documentation

    Undo Output Control patches the I6 template routines Keyboard(); and Perform_Undo(); so that we can use I7 rulebooks to hook into the UNDO command. These allow us to do anything we like--write new messages for UNDO responses and error text, keep track of variables (partially) independently of the game state as restored by UNDO, and even suspend UNDO programmatically.

    Undo Output Control is compatible with Conditional Undo by Jesse McGrew, which provides a more flexible framework for undo prevention. Using the extension with Conditional Undo does change some aspects of usage; see below.

    Section - Output rules

    The basic rulebooks provided by Undo Output Control are:
        (1) before undoing an action rules
        (2) after undoing an action rules
        (3) report undoing an action rules

    These rulebooks provide hooks into the following "moments" in the UNDO process: (1) before testing whether UNDO is allowed/possible; (2) after an action has been _successfully_ undone; and (3) after an action has been successfully undone but immediately before it is reported, optionally allowing us to replace Inform's default output with our own. The report undoing an action rules should end explicitly in either success or failure. The rulebook will end in failure by default, which means that Inform's default reporting for UNDO will be printed. If you want to substitute Inform's reporting with your own, end your report undoing an action rule with "rule succeeds" or equivalent (see the example for a demonstration).

    The same is true of the more specialized rules:

        report prevented undo rules
        report interpreter-undo-incapacity rules
        report interpreter undo failure rules
        report nothing to be undone failure rules

    All of these also require a rule to end explicitly with "success" in order to replace the default output.

    A number of rules are provided as "before" and "after" counterparts of these rules:

        before prevented undo rules
        after prevented undo rules
        before interpreter-undo-incapacity rules
        after interpreter-undo-incapacity rules
        before interpreter undo failure rules
        after interpreter undo failure rules
        before nothing to be undone failure rules
        after nothing to be undone failure rules
    The before, after, and report prevented undo rules apply only when Inform's built-in use undo prevention option is enabled.

    It should be emphasized that, though these rules look like standard action rulebooks, they are not. UNDO is not an action, and these rules are limited to imitating the appearance of action rules. This is why "check undoing" and "instead of undoing" rulebooks are not provided. We have hooks into the output, but little else.

    However, it should be noted that when the before undoing an action rulebook ends in explicit failure, undo will be prevented from occurring; this is one way (perhaps the simplest) of disabling UNDO. An example:

        Before undoing an action when the player is tired:
            say "You are too tired to bend space-time to your will.";
            rule fails.

    The "Breaking Glass" example provides examples of ways to use both the before and after undoing entry points to accomplish interesting effects.

    Section - Undo suspension

    Undo Output Control provides a second mechanism for suspending UNDO. To turn UNDO on and off at will, we simply use these phrases:

        suspend undo
        reinstate undo

    Note that these will not function if we have used Inform's built-in undo prevention, which functions globally.

    We can also test whether UNDO is disabled using the "if undo is suspended" condition.

    Finally, a rulebook is provided that allows us to control the reporting of a failed attempt to UNDO while undo is suspended:

        report attempt to undo-while-disabled rules

    By default, these rules print the message "That action cannot be undone."

    Be warned that if the player types UNDO immediately after you have reinstated it, there may be unexpected behavior, as the game can revert to the suspended state, but in such a way that the report attempt to undo-while-disabled rules do not fire.

    Section - Removing the option to UNDO at the end of the game

    Note that the "before undoing an action rule" is NOT consulted after the game has finished, so we will not be able to use it to block UNDO at that point. Instead, we should simply remove UNDO from the list of options that are presented at the end of the game ("Would you like to RESTART, RESTORE a saved game, QUIT or UNDO the last command?"). We can do so by removing it from the Table of Final Question Options, like this:

        When play begins:
            choose row with a final response rule of immediately undo rule in the Table of Final Question Options;
            delete the final question wording entry.

    This can be done conditionally if needed. We just need to delete the table row before the command to end the game.

    Section - Temporary suspension of game state saving

    Each turn, after the player has entered a command but before the command is parsed, Inform saves the state of the game into memory. This is the saved state to which the next UNDO command will revert. We can stop the game from saving the undo state, if desired. Once we've disabled saving, an UNDO typed later will revert back to the last saved state. If there are no saved undo states available, a message will print ("You cannot undo any further" by default).

    Undo Output Control provides the following phrases for controlling undo saves:

        disable saving of undo state
        enable saving of undo state

    See the "Purgatory" example below for a demonstration of how this feature might be used.

    Section - Using this extension with Conditional Undo by Jesse McGrew

    Jesse McGrew's Conditional Undo extension is compatible with Undo Output Control. It provides an activity-based interface to undo suspension which some authors may prefer. If Conditional Undo is included in our project, the "suspend undo" and "reinstate undo" phrases provided by Undo Output Control will not be available. IMPORTANT: The directive to include Conditional Undo must appear in your source text before the instruction to include Undo Output Control, or the extensions will not function as expected.

    Instead of using the "report attempt to undo-while-disabled" rulebook to respond to suspended UNDO, users of Conditional Undo should use the "rule for deciding whether to allow undo" activity (see the Conditional Undo documentation).

    Section - Changing vocabulary for UNDO and OOPS

    As was mentioned above, UNDO is not an action. Along with OOPS, it is handled before the player's command is actually parsed. To decide whether the player has typed either of these commands, Inform looks at the first word--only!--of the player's input and compares it to a character string (defined as an I6 constant). Because there is no I7 type that is exactly equivalent to this I6 type, it is quite difficult for I7 writers to add to or change the vocabulary associated with these commands.

    Undo Output Control makes providing new vocabulary for UNDO and OOPS a bit easier. Each command has three "words" associated with it. These are, with their initial values:

        UNDO OOPS
        undo word #1 "undo" oops word #1 "oops"
        undo word #2 "undo" oops word #2 "o//"
        undo word #3 "undo" oops word #3 "oops"

    We can thus add up to two vocabulary words for each command, in addition to the standard "oops" and "undo", or we can replace all three slots for each word if we like. Note that oops word #2 is a single-letter abbreviation; two forward slashes are required after single-letter words for Inform to understand them.

    To change one of these vocabulary words, we need to define a phrase. For example:

        To decide which value is undo word #3:
            (- 'revert' -)

    The word must be placed within single quotes, and only a single word can be matched. If your text contains a space, it will never be matched.

    Section - Change log

        v3 - Removed unnecessary check of the "before undoing an action" rulebook at the end of the game. This caused an UNDO typed at the end of the game to fail silently.

        v2 - Added suspension of game state saving and the Breaking Glass and Purgatory examples. Also added the ability to change word constants. Fixed minor bug in operation of undo suspension.

        v1 - Initial release.