Reply to thread

Message: <blockquote data-quote="chaochou" data-source="post: 5733662" data-attributes="member: 99817">Let's say I design a new game with four classes. But, as a designer I'm asked to ensure that each class can be just as effective as each other at the striker, leader, defender and controller roles. Okay, then.At 1st level each has identical defences, identical HP. Each gets to choose one of four powers:2d6 damage to one enemy1d6 damage to enemies in a 5*5 area1d6 damage to one enemy and +2 armour class for me1d6 healing and +2 armour class to allies within 5 feet.I've fulfilled the goal of making each class exactly as competent as each other in any role.In my game, what does 'class' mean?I'd say character class in my game is meaningless. It's effectively a point-buy design where you get one point at first level and four powers to choose from, each costing one point. What class you chose is irrelevant.So I can't see how the design goal of 'I can fulfil any role with any class' can't be anything other than in direct conflict with the implicit goal of class-based design which is to 'make classes unique'.Making classes mechanically equal across roles is, as far as I can see, the same as eliminating classes as the mechanical foundation for characters.</blockquote>