search

rsek / datasworn

The successor to the original Datasworn repository and Dataforged package, which provide game rules from the Ironsworn and Ironsworn: Starforged TTRPGs in JSON.
https://ko-fi.com/r_sek
123 stars 27 forks source link

Add a new `RulesPackage` subtype for `Ruleset`-agnostic content #71

Open rsek opened 4 weeks ago

rsek commented 4 weeks ago

While Moves and Assets are very sensitive to rules changes, many Datasworn node types are functionally Ruleset-agnostic. It'd be cool to allow RulesPackages that are explicitly Ruleset-agnostic, and can safely be imported in just about any environment.

Node types friendly to this:

Schema design/composition here is trivial; I think the hardest part here will be coming up with a descriptive name for the subtype

rsek commented 4 weeks ago

Excellent use case for this: describing rollable tables from non-Ironsworn games. WWN, SWN, and Perilous Wilds would all be great candidates.

cwegrzyn commented 3 weeks ago

Tag only packages have crossed my mind a few times. The interesting thing is how you then apply that tag-- i guess you enhance all the things you want to tag?

rsek commented 3 weeks ago

Tag only packages have crossed my mind a few times. The interesting thing is how you then apply that tag-- i guess you enhance all the things you want to tag?

at the moment it'd be that or adding the tags to the target package, yeah -- not ideal. another possibility is having a tag-only "library" package.

what I think would be most useful is some kind of "patch" format to apply modifications recursively. that could be a way to apply changes to any JSON value that exists in datasworn... but restricting it to tag changes might be a better idea. that way, conflict resolution won't be a problem (since any data changes will occur within the "namespace" of a tag)