So I can define a kind of action in the way that WI 7.15 says:
Include conversation framework by Eric Eve.
Answering someone that something is speech. Asking someone about is speech. Asking someone for is speech. Consulting someone about is speech. Implicit-asking is speech. Implicit-imploring is speech. Implicit-informing is speech. Implicit-quizzing is speech. Implicit-requesting is speech. Implicit-telling is speech. Imploring someone for is speech. Informing someone about is speech. Quizzing someone about is speech. Requesting someone for is speech. Saying goodbye to is speech. Saying hello to is speech. Saying no is speech. Saying sorry is speech. Saying yes is speech. Telling someone about is speech.
Easy enough. What Iād like to do is to re-use the speech
definition when defining another kind of action later on:
Factory Floor is a room. Factory Entrance is north of Factory Floor. Human Resources is east of Factory Floor.
The player is in Factory Entrance. The player wears an employee ID badge. Frosty the Supervisor is in Human Resources.
Working is a scene. Working begins when the player is in Factory Floor. Working ends when Getting Fired begins.
Getting Fired is a scene. Getting Fired begins when the player has been in Factory Floor and the player is not in Factory Floor. Getting Fired ends when Frosty the Supervisor holds the employee ID badge.
Workday is a scene. Workday begins when Working begins. Workday ends when Getting Fired ends.
Examining something is Being On-Task. Waiting is Being On-Task. Listening is Being On-Task. Wearing something is Being On-Task during Working. Taking off something is Being On-Task during Working. Going is Being On-Task.
Before doing anything other than Being On-Task during Workday, say "You glance guiltily around, checking to see if you're being watched. Technically, you could get your pay docked for being off-task.".
That all works, but if I try to say Speech is Being On-Task during Getting Fired
, I get the olā
The sentence āSpeech is Being On-Task during Getting Firedā appears to say two things are the same - I am reading āSpeechā and āBeing On-Task during Getting Firedā as two different things, and therefore it makes no sense to say that one is the other [ā¦]
error.
The scenario that this is a reduced form of has a larger scene with many small scenes occurring as part of it, some of which can occur in a variable order, and speech
is a type of action that should be warned in some situations and prohibited in others, and is sometimes perfectly OK. Iām leery of needing to redefine Answering someone that something is Being On-Task during Machine Test
, Answering someone that something is Being On-Task during Lunchtime
, Answering someone that something is Being On-Task during Board Meeting
, etc., and having to do that for all twenty āspeechā actions for possibly more than a dozen different scenes.
I do realize that a ākind of actionā isnāt a ārealā kind, in the sense that object
and, say, real number
are kinds, and that Iām not subclassing something in the way that standard OOP models would subclass classes, but it seems like there should be a way to re-use speech
inside of other tests. Am I wrong about this?