[code]An outcome is a kind of value. Some outcomes are defined by the Table of outcomes.
An outcome can be untested, possible, failed, or achieved. An outcome is usually untested.
Table of Outcomes
outcome outcome condition (outcome condition)
boring lack of results –
generic reusable event –
When play begins:
choose row 1 in Table of Outcomes;
showme outcome condition entry;
now boring lack of results is possible;
showme outcome condition entry;
now outcome condition entry is outcome condition of outcome entry;
showme outcome condition entry;
Test is a room.
[/code]
It also shows, interestingly, that a definition table dynamically reflects the properties of a value. Very cool!
Unfortunately, if I change the “–” entries to “possible,” the source no longer compiles:
Is this a bug? Or is there some reasonable explanation why it doesn’t work?
Object/value conditions are a special case, and there’s no way to refer to them as values in their own right. They can only ever be adjectives applied to the object/value.
If you want values, you need to define a kind-of-value.
(I’m not sure it’s deliberate that a definition table dynamically reflects properties of a value. It’s not true for properties of an object, and the behavior for values is linked to a known bug. It may change in future releases.)
Material is a kind of value. The materials are defined by the Table of Materials.
A stiffness is a kind of value. The stiffnesses are brittle, hard, and soft.
A material has a stiffness called the stiffy.
Table of Materials
material stiffy (stiffness)
metal hard
ceramic brittle
polymer soft