Non-Vancian Wizards and Casting Mechanics as a "Hook"

[ZombieRoboNinja]

I can see the OP's problem, but I think 5e might be a system that works well for him - he can play a warlock or sorcerer (or whatever non-Vancian arcane casters are in 5e) with a Scholar background and Magic-User theme, and they'll have most of the classical wizardly tropes without the Vancian mechanics. That's with no house rules whatsoever - and while we don't have the other arcane classes to play with yet, it seems like it'd be easy enough to houserule them to make them more "wizardly" (rename some spells/powers, switch spellcasting stat to Int, etc).

 

[Kavon]

I can see the OP's problem, but I think 5e might be a system that works well for him - he can play a warlock or sorcerer (or whatever non-Vancian arcane casters are in 5e) with a Scholar background and Magic-User theme, and they'll have most of the classical wizardly tropes without the Vancian mechanics. That's with no house rules whatsoever - and while we don't have the other arcane classes to play with yet, it seems like it'd be easy enough to houserule them to make them more "wizardly" (rename some spells/powers, switch spellcasting stat to Int, etc).

While this may work for some people, it has some inherent problems.
If I want to play a non-vancian Wizard, I shouldn't be forced to accept the inherent class features of other classes, while also being forced into a specific background and theme to put more salt on the wound.
Also, there are people that prefer not to work with Backgrounds and/or Themes.

I, for one, completely agree with the OP - point for point.
I refuse to accept that they cannot make it work - that smacks of lazy design.
Should all casters be purely defined by their spellcasting system?
The Cleric certainly isn't. Each spellcasting class can have their own thing, without forcing them into a certain spellcasting system.
Give them their own spells, their own class features, their own identity.

I want the freedom to allow or restrict spellcasting systems depending on how I want everything to work in my campaign world, without banning interesting classes. These two things should be seperated from each other.
Also, I want players to be able to choose for themselves which way they want to play, and not have their character concept be soured by being forced to play in a way they would prefer not to.
This goes for all conceivable spellcasting systems, not just the Vancian one.

 

[ZombieRoboNinja]

If I want to play a non-vancian Wizard, I shouldn't be forced to accept the inherent class features of other classes, while also being forced into a specific background and theme to put more salt on the wound.

But the Vancian spells are the ONLY class feature of the 5e wizard (unless you count "spellbook"). Familiars, class skills, etc. are all handled through background and theme. I'm guessing that the other "pure" spellcasters will be similarly stripped down: spells as the primary component of the class, with minor class abilities handled through themes. (Or feat selection, if you're ignoring themes.)

I, for one, completely agree with the OP - point for point.
I refuse to accept that they cannot make it work - that smacks of lazy design.
Should all casters be purely defined by their spellcasting system?
The Cleric certainly isn't. Each spellcasting class can have their own thing, without forcing them into a certain spellcasting system.
Give them their own spells, their own class features, their own identity.

I want the freedom to allow or restrict spellcasting systems depending on how I want everything to work in my campaign world, without banning interesting classes. These two things should be seperated from each other.
Also, I want players to be able to choose for themselves which way they want to play, and not have their character concept be soured by being forced to play in a way they would prefer not to.
This goes for all conceivable spellcasting systems, not just the Vancian one.

I really don't get what you're asking for here. Are you saying they should do multiple complete versions of every class, like rewriting the 5e wizard with 4e-style AEDU powers or magic points, so that you can mix and match your favorite flavor caster with your favorite spell system? Because that's more or less a complete rewrite of the class, i.e. a LOT of work, and honestly I'd rather see them spend their time making, say, the Psion class than jury-rigging the Wizard class to use magic points.

 

[Dannyalcatraz]

I really don't get what you're asking for here. Are you saying they should do multiple complete versions of every class, like rewriting the 5e wizard with 4e-style AEDU powers or magic points, so that you can mix and match your favorite flavor caster with your favorite spell system? Because that's more or less a complete rewrite of the class, i.e. a LOT of work, and honestly I'd rather see them spend their time making, say, the Psion class than jury-rigging the Wizard class to use magic points.

Well, to be honest, if you make a Vancian, Spell-point, AEDU, Fatigue-based, etc. lot of "spell" systems- and make 'em good- most people wouldn't have much of a problem changing the fluff & keywords so each and any one could be used for arcane, divine, Psionic or whatever.

(See HERO, GURPS, M&M...)

 

[Kavon]

But the Vancian spells are the ONLY class feature of the 5e wizard (unless you count "spellbook"). Familiars, class skills, etc. are all handled through background and theme. I'm guessing that the other "pure" spellcasters will be similarly stripped down: spells as the primary component of the class, with minor class abilities handled through themes. (Or feat selection, if you're ignoring themes.)

And that is a problem with the Wizard's class design.
Let's say I'd want to play the Wizard concept, but using the Cleric's spellcasting system (they're pretty similar, but I'm just using what we have, here). If I'd just need to take the Cleric and call it a Wizard to make it work, the following happens:

My Wizard has less spell slots, overall.
It can freely choose which spell to cast from the list of prepared spells (what I want).
It has.. "Channel the Arcane", which at first allows me to repel the undead.
I have spells not really fitting for a Wizard (such as cure light wounds).
I can now cast spells while wearing armor, and receive much more in the sense of weapon proficiencies.
I now suddenly use my Wisdom instead of Intelligence.

Now I can change some things, like making spells work off Intelligence, but overall, I get quite some things not befitting a Wizard.

You could say I shouldn't take the Cleric, because it uses 'Divine Magic', but that shouldn't matter - it's the spellcasting system we're talking about here, right? The point is, that the Cleric has all these other things that have nothing to do with its spellcasting system.

Also, what if I want to play a Cleric that uses Vancian spell memorization like the Wizard?

I really don't get what you're asking for here. Are you saying they should do multiple complete versions of every class, like rewriting the 5e wizard with 4e-style AEDU powers or magic points, so that you can mix and match your favorite flavor caster with your favorite spell system? Because that's more or less a complete rewrite of the class, i.e. a LOT of work, and honestly I'd rather see them spend their time making, say, the Psion class than jury-rigging the Wizard class to use magic points.

No, I'm not saying that at all. That would be exactly what I don't want.
I'm saying that spellcasting classes shouldn't be married to any spellcasting system.
Write the Wizard, or whichever spellcasting class, with its own special things, and then leave it open which spellcasting system you want to use.
Balance the different spellcasting systems so that it's internally balanced.
One class might simply get more spells, and that could be (part of) their special thing, but that doesn't have anything to do with the spellcasting system.

You're saying you'd rather want the Psion than having them force spell points as an option for the Wizard.
If the Psion is no more than a Wizard with spell points (as in, has no special features of itself that makes it different), than you have exactly what you thought I wanted to have.
But, if on the other hand, we have a Psion with its own special features, I can't make a Wizard with spell points by renaming the Psion into the Wizard, if that's what I want to play.
So, instead, I would say make the Wizard, make the Psion, but give both of them special things, and leave the matter of which way they cast spells open to the player.
The Wizard's 'thing' could be the collection of spells into the Spellbook, and getting more spellslots (or spell points, or whatever) than other classes.
The Psion could get something special that reinforces its mental prowess.

 

[Texicles]

I honestly think that a variety of spellcasting styles is one of the most important modules they can make for 5e, and I couldn't agree more with the sentiment people have expressed in this thread that a class should stand on its own, not being defined by its casting mechanic.

Each class should have features that define and differentiate it, and each class should have a significant number of its own unique abilities (and I feel that this applies to magic-users and martial characters alike). That's how you prevent homogeneity. Sure, there can be some shared spells, but it should be the exception, not the rule.

I almost think that using different casting systems in the core class designs is a bad idea. I'm not in love with Vancian casting, but I think that they would do well to make every caster use this system out of the gate. Making the module then becomes a matter of describing the different systems and listing the spells and noting whether they're A,E,D or U, how many points the spell costs, etc. etc. If you left out the descriptions and just gave the spell name and pertinent conversion info in table form, you're looking at a module that can change the game to suit a large variety of players and fit into an appendix of the PHB and/or DMG.

Do these things and classes are unique on their own merits, and you are able to enfranchise more and more varied players from the outset. That, to me, is the whole point of modular game design.

 

[Crazy Jerome]

Do these things and classes are unique on their own merits, and you are able to enfranchise more and more varied players from the outset. That, to me, is the whole point of modular game design.

I'm not opposed to that strategy as a strategy. I have doubts about its execution. Namely, I want to see a prototype of this sample wizard class that is clearly a "wizard" from its class abilities, outside whatever spell module you then choose to use with it. And then I want to see the marketing plan that convinces the internet hordes that this is "still D&D".

It if it were totally up to me, what I'd do is have a traditional "wizard" class with nothing but Vancian casting. Then I'd do a "mage" class much as you guys have suggested, now secure that I don't have to sell this thing as a wizard, and thus I've got a shot at actually doing a good, clean design that will work.

 

[Kavon]

I'm not opposed to that strategy as a strategy. I have doubts about its execution. Namely, I want to see a prototype of this sample wizard class that is clearly a "wizard" from its class abilities, outside whatever spell module you then choose to use with it. And then I want to see the marketing plan that convinces the internet hordes that this is "still D&D".

It would still be D&D, because you can still have the Wizard be Vancian if that is what you want.

It if it were totally up to me, what I'd do is have a traditional "wizard" class with nothing but Vancian casting. Then I'd do a "mage" class much as you guys have suggested, now secure that I don't have to sell this thing as a wizard, and thus I've got a shot at actually doing a good, clean design that will work.

What would be the difference between the Wizard and the Mage, besides one being Vancian-only, and the other having freedom of choice?
If they are otherwise equal, why make them two different classes? Just because there are people that demand that Wizards be Vancian only?

I don't have a problem with people wanting their Wizard to have Vancian magic. I do have a problem with people demanding that it work only one way, because that's how they want it to work.
I want people to have the option to make every spellcaster Vancian, if that's what they want.

 

[Crazy Jerome]

Kavon, I think we might have got our wires crossed on that last exchange.

I like the idea as an idea. I don't like its chances in the furor that it would create. Or alternately, if it did somehow stagger through the furor, it would be so mangled as to not be so great in the final product. You don't have to convince me that it's D&D.

The difference in having two classes is that some people want whatever traditional, vaguely plausible, stuff that sounds good for their wizard, and other people want a good design, even if that steps on tradition. I say, let the first group have the "wizard" and give us in the second group a clean design, under some other class name, uncontaminated by all the short-cuts, contradictory demands, balance issues, etc. Those of us in the latter group are immediately going to ban the "wizard" anyway, in favor of the cleaner class. So if you play a "mage" at my table, you can call it a "wizard" if you want, as long as you use the clean mechanics.

I think they should do this for all the classes. I nominate wizard, fighter, cleric, thief, ranger, paladin, druid, bard, etc. for the first group. We'll take "rogue" as a consolation prize, and then have warrior, mage, priest, champion, skald, loremaster, etc (or whatever set makes sense in the design).

Bringing this back around the long way more on topic, I think this is one hidden reason for why they want different mechanics to reside in different classes. They get to neatly side-step a lot of flak. (The other hidden reason is that they get to write a lot more classes and then put them in books to sell.)

 

[Kavon]

[MENTION=54877]Crazy Jerome[/MENTION]:
Yeah, sorry, I guess you're right. This is one of the things I really feel they (WotC) should grow some backbone and actually do what they set out to do, and make it modular.

I understand that dividing the classes up like that would keep some of the potential rage down, but.. Well, let me take a shot at this.

Wouldn't it be okay if the base assumption for a certain class be that system that the first group of classes would use, and then have the options that your proposed second group of classes would have be covered afterwards - in one class writeup?
This way, people that really care will have the default be the traditional way, but people that want a variation can alter it to their preference. It would help in keeping redundancy down.

At the end of the day, if these options are implemented, there's nothing stopping the traditionalists from making things traditional.
If they have a problem with other people, at other tables, not playing the way they think the game should be played.. Well, what can I say?