Mean Liar wrote:Seriously - you think multiclassing into an explicit "This is for NPCs that make baskets" class and getting a poor result for the effort is a product of bad design?
Yes. Duh.
If taking a level of a class does not put you on the same
level as someone who takes levels in another class, then those levels aren't level. And then your levels don't mean anything. You're making the argument that it's OK for a 12th level Fighter to be worse than a 12th level Druid because obviously he doesn't have magic to make him as awesome at 12th level as someone who does. The moment you concede that, the terminology "12th level" doesn't mean anything at all.
Taking a level in "basket maker" needs to give you
as much character power as taking a level in "Storm Wizard." Because that's what levels
mean. Storywise, you can have the NPC basket makers gain levels much more slowly to explain why people regard storm wizards as frightening (at least, more so than basket makers). But it's totally unacceptable for a 15th level basket maker to be less powerful than a 15th level storm wizard. Just as it is unacceptable for the 15th level Barbarian to be any weaker than the 15th level storm wizard.
If your power level is 9000, then that's what your power level
is. If the thing you do is something that people normally rank at power level 6000, that means that you're pretty good at that thing. If the thing you do is something normally rated at 20,000, that actually means that for the thing you are, you suck. If the thing you do is something normally rated at power level 2 to 3, then you're a fucking god of whatever that thing is.
That's how power levels work. And if you intentionally make them work some other way, your use of leveled nomenclature is an active hindrance to good game design.
-Username17