Reply to thread

Message

<blockquote data-quote="D'karr" data-source="post: 5732726" data-attributes="member: 336">BINGO.&nbsp; That is exactly the issue.&nbsp; A player should start the &quot;build&quot; of his character with a concept, not a class.&nbsp; Then he can choose mechanical add-ons that support that concept.&nbsp; These mechanical add-ons can be themes, class, race, etc.When the player starts with the idea I want to be a fighter, the DM should explore what the player actually expects this &quot;fighter&quot; to do, so he can recommend a mechanical fit that will fulfill that concept.If as a player I came to the game and said, I want to play a fighter.&nbsp; I want to be able to kick creature ass, with a hammer, smash them to the ground with my god's righteousness and charge into combat with abandon.&nbsp; The DM needs to look at the concept and see if&nbsp; FIGHTER, the class, is the right fit, or whether PALADIN, the class, is a better one.Trying to take a class and apply a concept it does not support is just going to lead to frustration.&nbsp; If a player wants to play a fighter that cast spells there are multiple ways of supporting that concept, but a hybrid rogue/barbarian is not a recommended build for that concept. That is not a problem with the classes, its a problem with unrealistic expectations.</blockquote>

[QUOTE="D'karr, post: 5732726, member: 336"] BINGO. That is exactly the issue. A player should start the "build" of his character with a concept, not a class. Then he can choose mechanical add-ons that support that concept. These mechanical add-ons can be themes, class, race, etc. When the player starts with the idea I want to be a fighter, the DM should explore what the player actually expects this "fighter" to do, so he can recommend a mechanical fit that will fulfill that concept. If as a player I came to the game and said, I want to play a fighter. I want to be able to kick creature ass, with a hammer, smash them to the ground with my god's righteousness and charge into combat with abandon. The DM needs to look at the concept and see if FIGHTER, the class, is the right fit, or whether PALADIN, the class, is a better one. Trying to take a class and apply a concept it does not support is just going to lead to frustration. If a player wants to play a fighter that cast spells there are multiple ways of supporting that concept, but a hybrid rogue/barbarian is not a recommended build for that concept. That is not a problem with the classes, its a problem with unrealistic expectations. [/QUOTE]

Verification