Removing forbidden cantrips from spellbook
The wizard's spellbook gets auto generated complete with cantrips the wizard isn't able to cast due to the choices taken as forbidden schools.
Is there some way to remove those cantrips so as not to clutter the character with spells they can't actually cast. E.g. If you specialise as a Conjurer and have Enchantment and Necromancy as your forbidden schools, then Daze, Disrupt Undead, and Touch of Fatigue, will never be usable by that character and are pointless to be in the spellbook. |
Quote:
|
To be honest, I wish it didn't auto-add all 0-level spells. Or at least it could have an Auto-Add tag for those that want them auto added vs. those that are not. I've got a few personal research 0-levels that are not part of the common pool that would get auto-added to every spellbook if I input them into HL. I tried to add them once, but nothing I did would keep them from getting into all spellbooks.
|
Quote:
|
Quote:
The ancillary thing to this is personally researched spells. I don't like them being part of the pool of spells, but I have no idea how to make them available to only one hero and still be able to be disseminated without also being part of the common spell pool. Logically it just seems impossible, sigh. As I like to say as a programmer myself, 'It is what it is.'. :) |
Quote:
On other hand I was thinking about this and I think I know how to do this really easily. Just with the addition of a single tag and changing the <match> logic. If that is the case then this could get added with little work. |
Forbidden Cantrips Work Around
For opposition specialist school cantrips not allowed, I just renamed them "Not allowed - Transmutation" (or whatever). Takes care of the bookkeeping aspect.
|
As a work around I renamed not-allowed cantrips from oppositional schools, e.g. "Not allowed - Transmutation". Works for bookkeeping.
|
All times are GMT -8. The time now is 04:46 AM. |
Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.