Incenjucar
Legend
The simple class we need is the wizard.
it's not bad players... give a new class (call it warlord or warblade or swordsage) the power and options available to a caster while fulff stays martial and the problem solves itselfNo it's not. No rules will fix bad players.
if it wasn't a problem then 4e never would have been made... by the end of 3.5 (the worst edition for it) you find that more tables had the problem reported then didn't.That's been a given for, well, since forever. If it were a game design problem and not a player problem, then every game table from 1974 to 2000 would have experienced this problem. And we most assuredly did not.
no it isn't I have pushed my "break the fighter in 3" in like 20 threads just since 1D&D was announced and I started the idea a few years before thatYou can. That's what we have been saying the whole time. No one is saying we should only have simple classes. Rather it's the opposite. It's people like Incenjucar saying we don't need simple classes. I'm sorry, but the "side" that's advocating for exclusion is your side on this.
anything a fighter can choose to do as "outside the mechancis" so can the hexblade, the valor bard, the warcleric, and the bladesinger wizardIt's a very rare player that needs a simpler class to engage in Mother May I.
it's not bad players... give a new class (call it warlord or warblade or swordsage) the power and options available to a caster while fulff stays martial and the problem solves itself
if it wasn't a problem then 4e never would have been made...
by the end of 3.5 (the worst edition for it) you find that more tables had the problem reported then didn't.
I notice you tried to cut 3e out though...
Yes, it is. Just look at the past 3 pages. You've got folks like me explicitly making the effort to say we can have both, and advocating how liking the simple fighter doesn't mean we are taking away from the complex fighter, and then you've got folks literally advocating against having a simple class in the game. It absolutely is that.no it isn't
4e addressed the issue at hand "Caster supremacy" after years of organized complaint with 3.5That's a false assumption. 4e would have been made regardless if there was a simple version or complex version. Because 4e was made in no way proves or shows that it was a problem.
2000 is the start, the first 4-6 months of 3e so yeah by not saying "until now" you did cut out 3eI didn't cut out 3e. I specifically alluded to it when I said from 1974 to 2000. Because with 3e, we suddenly had all these skills and feats.
lol yeah players are the only problem got it....And coincidentally that's when I and many others started to see players look at the character sheet to see if they had a particular feat or skill before attempting something.
no it isn'tYes, it is.
and you have folks like me advocating for a more complex class (addative not replace) and being told it's not a mechanic issue but a player one... by the way its YOU saying thatJust look at the past 3 pages. You've got folks like me explicitly making the effort to say we can have both, and advocating how liking the simple fighter doesn't mean we are taking away from the complex fighter, and then you've got folks literally advocating against having a simple class in the game. It absolutely is that.
tbh I think a simple champion/slayer like fighter is a great idea for people that WATN simple martial, but I think a 4e fighter/3.5 warblade/ 4e warlord class is needed (but rettoled so they have options for all 3 pillars, warblades still didn't have much socal and very little exploration)To be accurate, I've advocated for the return of the slayer and the elementalist to the game so that the martial classes can be on par with the magic classes.
I don't think you're understanding me. The claim was made that it's always been a design problem and not a player problem. I disgreed, saying that if it was a design problem, then it would have been a problem for everyone from 1974 to 2000 (when the fighter was simple with not many options) and it wasn't. Not even close. So therefore, it wasn't a design issue but a player issue. I said up to 2000 because that's when 3e came out and more complex rules were added. That's not excluding 3e. That's literally including it.2000 is the start, the first 4-6 months of 3e so yeah by not saying "until now" you did cut out 3e
Again, you're not understanding me. I am not saying only the players are the problem. I said when 3e came out, with things like feats and expansive skills, I (and others) saw it happen a lot more when players would look at their sheet to see if they had a particular skill or feat before doing something. That's not saying anyone is a problem, that's an observation of how people reacted.lol yeah players are the only problem got it....
no it isn't
Me saying unreasonable DMs is a player and not design issue is NOT saying that complex classes should not be in the game. I was responding to the comment that simple classes are bad because you have to rely on mother-may-I DMs, and how that is a player issue, not a design issue, for reasons I already gave.and you have folks like me advocating for a more complex class (addative not replace) and being told it's not a mechanic issue but a player one... by the way its YOU saying that
and the modern wizard wasn't invented yet either... you DID have simple casters too... you had a couple of spells and had to prep them in the slot to use them. the fighter DID have as much or more flexibility and there were not skills or feats but there were non weapon profs...I don't think you're understanding me. The claim was made that it's always been a design problem and not a player problem. I disgreed, saying that if it was a design problem, then it would have been a problem for everyone from 1974 to 2000 (when the fighter was simple with not many options) and it wasn't. Not even close.
excapt those complex rules lead to (what we have now) caster suprmacy... I will admite 5e is better then 3.5 but not by a ton.So therefore, it wasn't a design issue but a player issue. I said up to 2000 because that's when 3e came out and more complex rules were added. That's not excluding 3e. That's literally including it.
it is bunkAgain, you're not understanding me. I am not saying only the players are the problem. I said when 3e came out, with things like feats and expansive skills, I (and others) saw it happen a lot more when players would look at their sheet to see if they had a particular skill or feat before doing something. That's not saying anyone is a problem, that's an observation of how people reacted.
the fact that only half (actually like 3 out of 12) the classes have to deal with it and the others don't shows the design flawMe saying unreasonable DMs is a player and not design issue is NOT saying that complex classes should not be in the game. I was responding to the comment that simple classes are bad because you have to rely on mother-may-I DMs, and how that is a player issue, not a design issue, for reasons I already gave.