A list of the direct objects of this action that make it to the action stage.

set this property to true if you want to announce the object before the action result when there's more than one object. If the action routine summarizes the result at the end you don't want to do this so you should then set this to nil.

Flag: do we want the object name to appear before a check stage failure message if multiple objects are involved in the action. By default we do, otherwise it might not be clear which object the message referes to.

Flag, do we want to announce the object name before the verify message in cases where there's more direct object in the command? By default we don't since verify messages generally make it clear enough which objects they refer to.

The current direct object of this action

The current object being processed (in a TAction, always the curDObj; in a TI Action either the curDobj or the curIOoj).

Information to allow the DEBUG ACTIONS command to express a complete topic phrase

Set the current actor to the player character at the start of the game (to ensure we have a current actor defined).

This flag is used internally by the library to track whether the output of any text from a check() should stop the action, which it normally should. Game code should not directly override this property or change its value, other than indrectly via the noHalt() function.

Store the last verify failure message so that if we get several identical ones in a row, we don't keep repeating them

Flag: when a command processes multiple direct objects, do we want any failed attempts to be reported after successful ones?

A list of the direct objects of this action that make it to the report stage.

The signal (if any) )o be emitted by the direct object of this action. [SIGNALS EXTENSION]

A LookupTable containing the verify results for this action. This is keyes on the object being verified, with the value being the worst verify result encountered for that object so far.

Add a verify result to this action's verify table. This method is normally called by one of the macros (logical, illogical, logicalRank, etc.) use in an object's verify routine.

Call the check method (checkProp) on the appropriate object (obj). Return true to indicate that the action succeeds or nil otherwise

Run the check phase of the action, both on the direct object and on any preconditions.

Run the check stage on the preCondProp of obj

Return true to tell our caller we succesfully completed the action.

Modified in signals.t[347]:
If this action defines an associated signal, then have the direct object emit the signal after carrrying out out inherited handling. [SIGNALS EXTENSION]

Carry out the action phase on the direct object

Execute this action

Execute the command cycle for this action. This differs from the base Action class in not calling beforeAction directly, since the beforeAction() notifications occur within the execResolvedAction method.

Execute this action with a known direct object or objects. Call this method when there's no need to resolve the objects used in the command but we still want it to pass through every stage

Return a list of direct objects corresponding to the word ALL in the player's command. By default we return everything in scope that isn't a a Room.

Get a message parameter object for the action. We define 'dobj' as the direct object, in addition to any inherited targets.

get the verb phrase in infinitive or participle form

Given the text of the direct object phrase, build the verb phrase for a one-object verb. This is a class method that can be used by other kinds of verbs (i.e., non-TActions) that use phrasing like a single object.

'inf' is a flag indicating whether to use the infinitive form (true) or the present participle form (nil); 'vp' is the verbPhrase string; 'dobjText' is the direct object phrase's text; and 'dobjIsPronoun' is true if the dobj text is rendered as a pronoun.

A convenience method for putting every game object in scope, which may be appropriate for certain commands (not least, certain debugging commands). It's intended to be called from addExtraScopeItems when

reportAction() is called only after all the action routines have been run and the list of dobjs acted on is known. It only does anything if the action is not implicit. It can thus be used to summarize a list of identical actions carried out on every object in reportList or to print a report that is not wanted if the action is implicit. By default we call the dobj's reportDobjProp to handle the report.

Note that this method is usually called from the current Command object after its finished iterated over all the direct objects involved in the command.

Modified in sysrules.t[494]:
MODIFIED FOR SYSRULES EXTENSION

reportAction() is called only after all the action routines have been run and the list of dobjs acted on is known. It only does anything if the action is not implicit. It can thus be used to summarize a list of identical actions carried out on every object in reportList or to print a report that is not wanted if the action is implicit. By default we call the dobj's reportDobjProp to handle the report.

Note that this method is usually called from the current Command object after its finished iterated over all the direct objects involved in the command.

This modified version uses the reportRules rulebook to make it easy to insert differently worded summary reports.

Reset values to their starting state when an action is used to execute a new command.

Check whether the resolved objects for this action are in scope

install the resolved objects in the action