npcDeferredMessagesDirectobject

Deferred NPC messages. We use this to report deferred messages from an NPC to the player. A message is deferred when a parsing error occurs, but the NPC can’t talk to the player because there’s no sense path to the player. When this happens, the NPC queues the message for eventual delivery; when a sense path appears later that lets the NPC talk to the player, we deliver the message through this object. Since these messages describe conditions that occurred in the past, we use the past tense to phrase the messages.

Some messages will never be deferred:

commandNotHeard - if a command is not heard, it will never enter an actor’s command queue; the error is given immediately in response to the command entry.

refuseCommandBusy - same as commandNotHeard

noMatchDisambig - interactive disambiguation will not happen in a deferred response situation, so it is impossible to have an interactive disambiguation failure.

disambigOrdinalOutOfRange - for the same reason noMatchDisambig can’t be deferred.

askDisambig - if we couldn’t display a message, we definitely couldn’t perform interactive disambiguation.

askMissingObject - for the same reason that askDisambig can’t be deferred

askUnknownWord - for the same reason that askDisambig can’t be deferred.

npcDeferredMessagesDirect : npcDeferredMessages

Superclass Tree (in declaration order)

npcDeferredMessagesDirect
npcDeferredMessages
` object`

Summary of Properties

(none)

Summary of Methods

ambiguousNounPhrase askMissingObject commandNotUnderstood emptyNounPhrase insufficientQuantity noMatchCannotSee noMatchForAll noMatchForAllBut noMatchNotAware singleObjectRequired uniqueObjectRequired wordIsUnknown zeroQuantity