|5 people marked this as a favorite.|
Sean K. Reynolds on the Paizo forums basically admitting to there intentionally being trap options because it's "admirable" to play a character that is going to die in an adventure.
I'm not sure what game Sean is talking about though. D&D/PF is freaking hard. 90% of the game from the bestiary through the environment section is dedicated to making the game harder for everyone involved. It is a game about conflicts and rising above those conflicts. I don't see any of the pregens in the APs running around as 12 Int wizards.
This post hurt me pretty bad and I lost a lot of faith in the design team after it. If I'm buying products from Paizo, I'd rather not have page count wasted on stuff that's only going to hurt my players if they try it, or give them ideas that I'm going to have to homebrew an option that works instead of just letting them take what's in the book.
Vow of Poverty for example drastically hurts the viability of a character (worst of all it hurts monks >:O) which not only means that character is probably going to die pretty easily to the dangers of adventures due to being severely under geared, but it also makes them a drag on the party. In Magic the Gathering, if your deck is loaded with sucky cards your system mastery affects no one else. If you're playing a gimp your decisions can cost someone else their character.
I initially trusted the designers to not feed my players options that are going to hurt them. Someone who takes Vow of Poverty is someone who lacks the system mastery to understand why it's a bad idea, and the idea of punishing people for "roleplaying" as an abominable one from a designer standpoint.
It was a dark day.
I have been saying this for years. If you have hundreds of pages and millions of options and only 10-15% of those options are "optimal" or useful in most situations, then one player at a table who chooses to play optimal style creates an arms race of players. The reason everyone else has to go along is to keep from being irrelevant. And the end result is that 85-90 percent of rules content is useless.
The "average" game table does not consist of gamers like many of the employees at Paizo like to present themselves...as players who make great characters for story and not math. Because as game designers they understand (or should) that game mechanics is just a bunch of numbers and math and the GM can wipe them out at any time. Creating the story is the fun part of RPGing. However, most players are concerned with showing off their intelligence or system mastery or showing off to their friends how uber a hulk they build, or just stealing the spotlight.
So every time the rules team puts out some powerful rules option that is usually the "best" choice it pushes all the "not best choices" into the realm of obscurity. This is why balance in rules options are so important. Not just with every feat or spell, but the combinations of spells and feat and magic items. The correct combinations are much more dangerous to game imbalance than a single feat, item, spell usually are.
This mentality has been present since 3.0 came about and it hasn't ended with Paizo. There is already starting to be an outcry from GMs who have the inability to say "No" to players in regards to published options that Paizo puts out, leading them to desire a reset with a new edition. I personally don't plan on buying another rule line supplement by Paizo. And by requiring me to do so with the Mythic Adventures guarantees I won't be buying Mytic Adventures either. And if the APs go the way of "we have to support our rule line," I'm not such a fanboy that I can't do without the APs either. Put a gun to my head and say buy the rule line or you won't be able to play the AP line, and I'll say I don't need the AP line either then.
It's a cyle. And half the customers who bash me for this stance will feel foolish in a couple of years when they finally realize the rule line has gotten too out of control for them too and wonder how they got sucked in so far. It happened with fans of 3.0 and it happened with 3.5. And it is happening with Paizo.