• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Difference in Secondary Spell Requirements

frumple

Well-known member
Can someone explain the difference in how Hero Lab treats Req. Classes vs. Req. Schools for secondary spells.
 
SecSplMech.ReqClass means the class needs at least 1 SecClsAllw tag to generate it's candidate expression for the secondary spell table. Looks like this is most often used by Shaman Spirits. If I recall correctly, it used to be much more closely tied to domains, but then we switched from "Spell is tagged with something referring to which domains allow it" to the preferred method of "Each domain is tagged with what spells it allows for secondary spells". The former meant that users who wanted to make their own domains would have to either create redundant copies of spells to tag them appropriately, or have their new spells replace the older, while the latter lets people freely define new domains.

SecSplMech.ReqSchool means the class needs at least 1 SecSchAllw tag to generate it's candidate expression for the secondary spell table. It is still largely used for wizard specialized schools, because unlike with domains (which had 9 spells to associate with themselves), tagging each custom special with a huge (and ever growing) list of tags of the appropriate school is untenable.
 
Ok. Thanks.

This goes back to an earlier post. What I am trying to do is have a witch's patron spells be secondary spells (the class I am working on says explicitly that the patron spells do not add to the spellbook).

So it looks like SecSplMech.ReqClass is what I need. However since the spells from a witch's patron are boostrapped to the patron I figure I need to go through all the bootstrapped spells and assign the SecClsAllw tag with the appropriate spell id fairly early. Correct?
 
Must have missed that post. Is the witch patron going to be present on the hero as a pick, or will you be looking at it as a thing?
 
Something like this then?

PostLevel 10000
Code:
foreach pick in hero from BaseSpell
  ~ Is this bootstrapped by something?
  if (eachpick.isroot <> 0) then
    ~ Is that something a witch patron?
    if (eachpick.root.tagis[abCategory.WitPatron] <> 0) then
      perform eachpick.pulltags[ClsScAllSp.?]
      perform eachpick.assign[Hide.Spell]
      endif
    endif
  nexteach

~ Push the gathered tags to the class helper.
perform hero.childfound[cHelpWit].pushtags[ClsScAllSp.?]
 
Last edited:
Back
Top