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

[rsek]

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:

• AtlasEntry + AtlasCollection
• Npc + NpcCollection
• OracleRollable + OracleCollection
• Truth
• Tag - opens up some interesting possibilities for tag-only packages...

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

[rsek]

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

[cwegrzyn]

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]

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)

[cwegrzyn]

Just as a practical example, in Iron Vault I have it accept a ruleset of '*' to indicate that it shouldn't enforce the ruleset.

I needed this for two reasons.

The first is that I wanted people to be able to make a collection of oracles that they could use across all of their campaigns, regardless of the base set. This is handled effectively by your proposed additional rules package type.

The second reason is perhaps more IV specific: for Datasworn content people embed in their campaign, I basically wanted a way to tell Iron Vault to skip the ruleset check, even though the field is required in Datasworn. In that case, I do want moves and assets to be allowed, so I might still need an alternative mechanism for this-- but it is also purely internal, so I can use the weird hack I have in place.