Reply to thread

Message

<blockquote data-quote="Jack Daniel" data-source="post: 8415066" data-attributes="member: 694">The problem with either of these ideas is multiclassing. A fighter10/wizard10 should probably always have about the same total number of hps regardless of the order in which the levels were taken, but if you cut hit dice off at 10, the player who takes all fighter levels first is at a big advantage over the player who takes all wizard levels first; and if you go for Steampunkette's idea, then suddenly there's a massive difference between an even multi that goes fighter–wizard–fighter–wizard… and wizard–fighter–wizard–fighter… for no good reason.Maybe just… reduce the hit die sizes back down to the original d4, d6, d8? Or cut hit dice in half — instead of d4, d6, d8, d10, and d12, determine classes' hit points with fixed values that simulate d2, d3, d4, d5, and d6? (Really, it'd be 1.5, 2, 2.5, 3, or 3.5 – plus ½ Con mod – hps gained per level above the 1st. Something like that.)</blockquote>

[QUOTE="Jack Daniel, post: 8415066, member: 694"] The problem with either of these ideas is multiclassing. A fighter10/wizard10 should probably always have about the same total number of hps regardless of the order in which the levels were taken, but if you cut hit dice off at 10, the player who takes all fighter levels first is at a big advantage over the player who takes all wizard levels first; and if you go for Steampunkette's idea, then suddenly there's a massive difference between an even multi that goes fighter–wizard–fighter–wizard… and wizard–fighter–wizard–fighter… for no good reason. Maybe just… reduce the hit die sizes back down to the original d4, d6, d8? Or cut hit dice in half — instead of d4, d6, d8, d10, and d12, determine classes' hit points with fixed values that simulate d2, d3, d4, d5, and d6? (Really, it'd be 1.5, 2, 2.5, 3, or 3.5 – plus ½ Con mod – hps gained per level above the 1st. Something like that.) [/QUOTE]

Verification