Whether multiple rolls (as in object generation, or with IMultipleRolls) .
Whether this table should be included in the initial oracle rolls when generating a game object. This is a somewhat arbitrary recommendation, and may not be appropriate for all implementations (or all game situations). Rather it's a reasonable starting point in most cases.
That said, the game itself recommends against rolling all possible results at once (see "Peeling the Onion", p. 293, Starforged). If your goal is to implement the game 'as-written', consider how you might include some means of "progressive disclosure" of oracle results.
May be deprecated in the future in favour of dedicated object template information.
The maximum number of rolls when using this oracle to create a game object. Assume it's 1 if not specified.
The minimum number of rolls when using this oracle to create a game object, if this oracle is rolled. Assume it's 1 if not specified.
Whether the table's standard use is iterative. Common examples are Feature, Opportunity, and Peril tables, which are most often used repeatedly to describe different areas of/events in a place, rather than being assigned as a description of the place as a whole.
Mutually exclusive with Max rolls. If undefined, assume false.
Describes the string values of this item that should be replaced with template strings and filled with the results of one or more oracle rolls.
Hints which attributes are set by this table.
Generated using TypeDoc
Describes the recommended usage of this item.