prestige class question

I've been dealing with this topic a lot lately and yes, "+1 level of existing spellcasting class" features should do exactly that. A wizard level 6 + prestige class which adds +2 level of spellcasting class could cast an 8d6 fireball.

While a level 6 wizard who took 2 levels in another class or a prestige class without +1 level of existing spellcasting class features, would only cast a 6d6 fireball, even if both classes have fireball as a spell.

Examples that I got from WotC were things like a 6th level wizard / 6th level sorcerer casting a fireball would either cast from the wizard list at 6th level or the sorcerer list at 6th level.

We have added in support to the Feature Library to handle prestige classes that stack levels as well as general "stacking" rules for house ruled games which allow classes to stack levels.

Below is an image from the soon-to-release feature library configuration of a 3.5/Pathfinder fireball:



The multiply effect node holds the stacking and variable dice rules. In this case we've selected "All" for the classes, this is because that's the easiest to test with on our end.

A production version of the spell would have only spellcasting classes who get Fireball as the selected classes. Again, this logic is still being worked on, so it'll get refined further for handling prestige classes and such.

Additionally, we've been working on prestige classes and class variants so you'll actually be able to specify a prestige class for a character or a variant of a class.



Double clicking on this field will present a list of variant classes which are available to Wizard and allow you to add it to your character. We're still working on testing this system as a mechanism to handle prestige classes and may opt to keep them on a second line as tracking level in a prestige class separately is very helpful -- either way, "we're working on this problem" is the short answer I was attempting to offer!

 

There will be. We're working on logic to handle variable caster/spell level while still leaving the feature with a default value set in the currently-unnamed level node (in the fireball example, it's the value node with a 3 in it).

I have a solution that works for 5e but I want a variable solution that works for any system. Honestly, if we were just building for a single game system, we'd have been done a long time ago

 

So the way the prestige classes will work is slightly different than the variant bit I detailed above.

You'll still be able to take a prestige class (or several) through the normal -- add a class -- mechanic. The difference is that a prestige class will have classes they can augment listed in their descriptions.

In other words, this solution should work for you just fine

The real magic sauce comes from the features define for traits. These are were we'll get solid blending between classes and prestige classes.

I'm currently working on a new AC mechanic which is holding up some other work, so I had to take a break from prestige and variants. Hopefully I'll be back on task for this topic in the next week though!