Library Modules and Extensions

[Valarian]

Thinking of starting to look in to the CoreRPG. With the base of CoreRPG, do we have the ability to "lock" library modules to only show up for certain extensions?

[Trenloe]

Thinking of starting to look in to the CoreRPG. With the base of CoreRPG, do we have the ability to "lock" library modules to only show up for certain extensions?
I don't think you can lock for extensions, but you can for the layered ruleset name.

[Valarian]

"Layered" ruleset name. I'll have to look in to that one. Thanks.

Good start here probably:
https://www.fantasygrounds.com/forums/showthread.php?19530-Ruleset-layering-summary

[Trenloe]

"Layered" ruleset name. I'll have to look in to that one. Thanks.
Open one of the 3.5E or PFRPG modules that come with the Fantasy Grounds and you'll see it has specifically the name of the ruleset (3.5E or PFRPG) and can be opened in these rulesets only. both of these rulesets are layered on top of CoreRPG but can't be opened in CoreRPG.

Having said that, PFRPG is a little bit different as it is layered on top of 3.5E, which is layered on top of CoreRPG. As such, PFRPG can generally use 3.5E modules (and older d20 modules) and therefore it has the following code in PFRPG.pak base.xml:

<importinfo>
<acceptfrom ruleset="d20" />
<acceptfrom ruleset="3.5E" />
</importinfo>
This allows the PFRPG ruleset to use modules tagged as <ruleset>PFRPG</ruleset> as well as 3.5E and d20.

[Valarian]

So do the rulesets using the new "merge" tags to import from CoreRPG, rather than doing an extension on top of CoreRPG. Then can specify as normal. Now have to go and try it out.
CoreRPG awaits ...

[Trenloe]

So do the rulesets using the new "merge" tags to import from CoreRPG, rather than doing an extension on top of CoreRPG.
In the layered ruleset base.xml file they have the "importruleset" tag to indicate which ruleset is loaded before this one. Here is an example from the 3.5E ruleset:

<!-- Layers -->
<importruleset source="CoreRPG" />
The approach is very similar to an extension - with, as you say, merge rules taking over depending on what object is being merged. JPG gives more info in post #2 here: https://www.fantasygrounds.com/forums/showthread.php?19530-Ruleset-layering-summary and a "Merge rules" section has been added to the ruleset modification guide: https://www.fantasygrounds.com/modguide/templates.xcp

But, instead of the ruleset being an extension you select to run on top of another ruleset, the layered ruleset is seen by FG as a completely separate ruleset with modules and extensions being available specifically for this ruleset only by using the <ruleset> tag in the module or extension.