Can Modules include elements (feats, spells) from different rulesets?

[Tempered7]

My module will be universal ("any ruleset" ticked). Original campaign files are in CoreRPG.
I created 3 solo variant feats for D&D 5E and PF1.
I'm trying to keep them in one page so that if a player opens it in PF1 or 5E, they can use the appropriate feats.
I have 2 versions of the campaign/module; one for 5E and the other for PF1 (I edited the ruleset tag in db.xml)

But how do I add PF1 feats back to the 5E campaign files to continue writing from there?

[Zacchaeus]

I’m not exactly sure what you are doing, but to add more stuff to a module go back to your original campaign and add the stuff there and then re-export into the same module.

I’m also not sure if it’s a good idea to include data from different rulesets in the same module. I would assume (but I don’t know) that the format of feats is different between 5e and pf1. It will probably be less confusing to create a campaign for each rules and create the feats in that and export to two different modules.

[Tempered7]

Ah, yes. I was confused a bit.

- I add 5E feats to the 5E module,
- make a copy, then edit ruleset tag in db.xml to PF1
- Open it in pf1, add feats
- Make another copy and edit ruleset tag back to 5e
Voila.

Thanks.

NOTE: To anyone who wants to add multiple ruleset elements (feats, spells, items) to one module. Be careful with file names, if you have 2 same file names for different elements, campaign gets borked.

[Tempered7]

Heck yeah! I did it! Thanks Zac.

I borked the campaign files at first but I have backup.

This is what I wanted to do:

NOTE: To anyone who wants to add multiple ruleset elements (feats, spells, items) to one module. Be careful with file names, if you have 2 same file names for different elements, campaign gets borked.

[Tempered7]

I’m also not sure if it’s a good idea to include data from different rulesets in the same module. I would assume (but I don’t know) that the format of feats is different between 5e and pf1. It will probably be less confusing to create a campaign for each rules and create the feats in that and export to two different modules.

Oh, I didn't consider that hmm. Dang. When I check the 5e feat in pf1, it just show " [] ".
But yeah, maybe it borks something that I don't foresee.
Back to 2 versions, then.

[Moon Wizard]

You will not be able to build one module that works in multiple rulesets; because each ruleset has it's own data structures for every record type.

Regards,
JPG

[Tempered7]

You will not be able to build one module that works in multiple rulesets; because each ruleset has it's own data structures for every record type.

Regards,
JPG

Even for text & table record types?

I created the campaign in Core RPG to make it universal, then changed the ruleset tag in db.xml to 5E, would that break the module? Everything is now working, it exports etc. But would that be a problem later?

Oh and, is there a way to quickly copy paste the whole text from one campaign folder to another? This is in case there is a possibility of breaking the module. And to carry the text to PF1.

Oof, I should've created it in 5e.

[Marmus]

Anything created in CoreRPG can be opened in 5e. I assume same for PF. So why not keep it Core RPG?

[Tempered7]

Anything created in CoreRPG can be opened in 5e. I assume same for PF. So why not keep it Core RPG?

It is for adding 3 solo variant feats but 5e & pf1 have different styles of feat records. If those 2 rulesets can recognize feats made in Core RPG, I'll keep it. But there's no player category > feats at the right menu in Core.

[Moon Wizard]

If the records are unique (i.e. not in CoreRPG, such as Feats, Backgrounds, Classes, etc.), then they are defined differently in every ruleset, with potentially different fields and different data types for those fields.

Only modules with the Any Ruleset button checked while exported can be opened in rulesets other than the one they are built in; and the above caveats apply, including console popup errors (data type mismatch), missing data, etc.

Regards,
JPG