• The VOIDRUNNER'S CODEX is coming! Explore new worlds, fight oppressive empires, fend off fearsome aliens, and wield deadly psionics with this comprehensive boxed set expansion for 5E and A5E!

Heroes of the Feywild Excerpts

WalterKovacs

First Post
That would be a plausible excuse if they werent wasting their time rehashing the same old content over and over(essentials) and expanding oversupported classes into roles that are already covered by other undersupported classes(Mages/Bladesingers vs. Sorcs/Swordmages).

This depends on the definishing of wasting time.

Essentials created new classes, which automatically had a lot of support in the form of old utility powers, feats and paragon paths (amongst other things), while still doing something new. If, for example, the runepriest had been a new type of Cleric, it would have at lot of existing content to supplement it's initial write up. Ditto if the seeker had been a ranger variant.

The mage, even the evoker/pyromancer, isn't much of a replacement for the sorceror. The bladesinger (and hexblade) while functionally similar to a swordmage fills different purposes. It would be like saying that a warlord and a fighter are the same thing just because both can be a sword and board in heavy armor.

Also, essentials recovered old terrain because the purpose was as a second launch, intended as an easy entry into a game that had gotten pretty complicated, while also making some more "iconic" versions of the iconic classes.

Also, if there is a Goldy Locks amount of support for a class ... what is easier to accomplish? Get EVERY undersupported class up to that Goldy Locks level, or create a variant of an existing class that can do a similar job? Since it's PART of an 'oversupported' class, it already has better support than undersupported classes on day 1. So, if they are going to do a new class, attaching it to an existing class (especially one with tons of support) is a way to avoid creating another class that will end up being undersupported.

And, is anyone actually making an argument that they should not put out any new classes until all the old stuff is brought up to snuff?

What they are doing now is trying to go with fluff first, crunch later. This means, the books are focused on an idea, like the Feywild or Shadowfell, instead of "Splat book for characters of this power source"

Obviously, WOTC have a reason to stop doing the PHB, MM, DMG, AV, XPower, etc books. If those were selling well, they would have kept doing it. Instead, they have moved towards a more fluff dictates crunch area instead of "let's make a power source with a class for each role; let's make a book with 2 new builds for each class of this power source; let's have 1 feat for each class + race combo" area.

Ultimately, any book they put out has to consider what is going to sell, and what the target audience is. For players, you are most likely to buy something that either helps an existing character, or interests you for a new character. In terms of existing characters, WOTC has the Character Builder data to give them a good idea of what people are playing. It's a bit harder to guess what people will be interested in playing, but something NEW is probably a better chance of catching someone's interest than a new build of something that already exists. Unless that new build is something out there enough to be considered new, it's target audience is for the people already playing the class, and people that were interested in playing the class, but need that little extra push before they do it. I don't have the numbers, but the target audience of "people we failed to convince the first tme" seems like one that isn't predisposed to liking what you are offering, while the people who liked the last 5 books with new wizard schools/spells are probably going to want book 6.

The reason why Dragon is a perfect place for content for undersupported classes is that, not only is it something you either get every month or you don't, so you don't need to 'sell' it in the same way you would a book, but also because access to a new runepriest article is paired with the previous runepriest content (i.e. the character builder). On the other hand, if someone who doesn't subscribe to ddi picks up a new book, and it has a runepriest build it in that is awesome enough that they want to play it, and they are a newer player ... they have to go out and find a PHB3. Which, a lot of stores probably aren't stocking any more.
 

log in or register to remove this ad

Marshall

First Post
This depends on the definishing of wasting time.

Yes, designing a new class, or a new build for an existing class, that covers the exact same design space and the exact same fluff as an already existing class that could use the support is the definition of wasting time.

Essentials created new classes, which automatically had a lot of support in the form of old utility powers, feats and paragon paths (amongst other things), while still doing something new. If, for example, the runepriest had been a new type of Cleric, it would have at lot of existing content to supplement it's initial write up. Ditto if the seeker had been a ranger variant.

The Runepriest introduced many new mechanics that arent supported by the Clerics support and the Seeker has nothing to do with the Ranger so throwing them together would have been just as worthless. Its almost as worthless as the current Wizard support is for a Bladesinger....

The mage, even the evoker/pyromancer, isn't much of a replacement for the sorceror. The bladesinger (and hexblade) while functionally similar to a swordmage fills different purposes. It would be like saying that a warlord and a fighter are the same thing just because both can be a sword and board in heavy armor.

The Mage, combined with all the striker support the Wizard has, is easily on par with the Sorc for DPR and still has superior levels of control available. Bladesingers, Hexblades and Swordmages are all the same niche or, more accurately, they are all best represented by the existing Swordmage. Whats the difference between a Hexblade and an Assaultmage? Swordbond only calls the blade to you instead of creating it out of arcane substance? Bladesingers are nothing more than a different take on at-wills, completely undeserving of its own class and incapable of fulfilling the 'role' they are assigned.

Also, essentials recovered old terrain because the purpose was as a second launch, intended as an easy entry into a game that had gotten pretty complicated, while also making some more "iconic" versions of the iconic classes.

No. Its 4.5 without calling it 4.5. Its a new on-ramp alright, the problem is its not the same highway...

Also, if there is a Goldy Locks amount of support for a class ... what is easier to accomplish? Get EVERY undersupported class up to that Goldy Locks level, or create a variant of an existing class that can do a similar job? Since it's PART of an 'oversupported' class, it already has better support than undersupported classes on day 1. So, if they are going to do a new class, attaching it to an existing class (especially one with tons of support) is a way to avoid creating another class that will end up being undersupported.

Creating a brand new class with the same name as an existing class but with unique features that are incompatible with ALL previous support is even worse than making a new undersupported class....especially when you connect that class to one that has "Goldy Locks" support instead of one that mechanically and thematically already exists and could really use the support.

And, is anyone actually making an argument that they should not put out any new classes until all the old stuff is brought up to snuff?

No one is making that argument. OTOH, why the heck would you waste creating new classes that not only cover the same niche, but cover it with the same thematics and similar mechanics.

What they are doing now is trying to go with fluff first, crunch later. This means, the books are focused on an idea, like the Feywild or Shadowfell, instead of "Splat book for characters of this power source"

So?!? The problem isnt fluff, its mechanics. Its the waste of time designing 3 arcane swordsman classes all with their own incompatible mechanics all attached to a different and usually worthless set of support for that build.
 

Remove ads

Top