Optional Expanded Spell List and Spell Learned Cap Override

Comments

7 comments

  • Avatar
    Jlambert3852

    I too would like this feature. I would like the to see a potential way to select the spell list associated with a class. I am running a game with all bards. After we got going, I had the thought of using a different spell list for each of them. Same class, but swapping the spell list would help make them all feel different!. They are all different sub-classes, but being able to change the spell list in some way would be great. 

    In the past, I have just created a copy of A spell (also to change the flavor of it) and tag it with the appropriate class I want to allow to use it. However, the number of spells that would require to do that, would be ridiculous. If they would just allow us to create custom base classes, this would be completely possible in that regards. Copy a base class and then select which spell list to use. 

    But some way to do this would be great! Even if some way to turn off/override the rules for the list.

    0
    Comment actions Permalink
  • 0
    Comment actions Permalink
  • Avatar
    Brandon Cimino

    I have found that Feats, despite being leveraged pretty rarely in actual campaigns, are perhaps the most flexible homebrew data type and allow for features such as this (in a round about way). There are limitations, though, as the spells granted by a feat don't interact with the spell slot system.

    You could also make a custom background, which, as of Ravnica, can expand a spell list. However, that doesn't solve the "extra slots" feature.

    There actually is a modifier for extra slots, but it doesn't have any subtypes available, and so validation prevents the modifier from being used.

     

    Edit: I misread; you were talking about spells learned, not spell slots. Also, side note, the "Spell Slot Increase" modifier (which doesn't work) is available for Feats but not Items.

    1
    Comment actions Permalink
  • Avatar
    Eric Dittert

    This post describes two requested features.  I like them both, but I think it would be better to separate these into two feature requests, as we're more likely to get dev attention for requests that can be dealt with as single work items.  If the OP could make the appropriate edits, I think that would be helpful.

    0
    Comment actions Permalink
  • Avatar
    Jlambert3852

    Not really 2 seperate features. Really just the ability to edit the spell lists in some way. The things described are just possible ways the devs could do it.. 

    Additionally, to get the Devs attention, it is best to have it in one thread and upvote it. The more votes on a feature, the more likely the devs will give it attention. 

    0
    Comment actions Permalink
  • Avatar
    Eric Dittert

    Ok, well, I don't want to start a war about this or anything, but for clarity here's what I was referring to.  The OP's title has two parts: "Optional Expanded Spell List" and "Spell Learned Cap Override".  As I read the OP, the first of these, "Optional Expanded Spell List" is the ability to add spells to the spell list from classes other than the classes that the character has in its build.  So this has to do with which spells can be added to a character's spell list.  The second, "Spell Learned Cap Override" is not very clearly described in the OP, which may be the source of our disagreement.  I assumed (mainly because of the use of the word "Cap") that this referred to allowing override of the number of spells that a character can know.  I still think that is the most likely correct reading of the OP, but as I said it is not very clear so I could be wrong.

    Anyway, whether or not those are what the OP intended, those are certainly two different features.  You could implement one, or the other, or both, and they would be useful for different purposes either separately or together.  Also, I am pretty sure they would affect distinctly different parts of the code.

    As to the the issue of the number of threads and dev attention, I agree that if you have a request that describes minor variations on one basic function, then that request should not be split.  However, if we are talking about multiple separable pieces of functionality (as I think this request does) then it should be split up.

    0
    Comment actions Permalink
  • Avatar
    Greg Craill

    I see it as the same thing - override spell limitations. I have noticed the paladin class can prepare more spells than is allowed by the class rules, but a bard cannot do the same thing. For custom in house reasons we have cases for this to happen, and while we can load up a feat that is only partially successful as it does not allow casting feat spells at higher levels using spell slots available.

    0
    Comment actions Permalink

Please sign in to leave a comment.