Open rsek opened 1 month ago
Consider: moves, as a hint for "for this step, make this move, then..."? Opens up some interesting possibilities, but it functionally turns the entity schema into a description of a multi-step "macro" operating in the Datasworn rules set -- that's some serious scope creep.
Might be best left for another library based on datasworn; worth keeping in mind and leaving conceptual "space" for when designing the schema.
FVTT has its own system for this. So does the obsidian plugin, and IIRC Crew Link and Stargazer do, too.
features might include:
tags
onOracleTableRow
s (similar to old Dataforged's oracle attributes), and use them to select the next roll (for entities that have a subtype)roll_template
property -- either incorporating it, or replacing it entirelyOracle rolls might be positioned as their own kind of
Attribute<T>
, alongsideAttribute<Int>
for stats, condition meters, and so on. Then, player characters and incidental vehicles might be described with the same system, and these properties could be assembled as desired to describe many kinds of 3rd party content.Example Entity Types