Reply to thread

Message: <blockquote data-quote="Sword of Spirit" data-source="post: 6501238" data-attributes="member: 6677017">Yes, but I'd absolutely house rule that they get another cantrip. It's absurd to have isolated situations where it matters what order you take something in, simply because they didn't specify that it doesn't. It seems to violate design philosophy by penalizing a choice that provides no benefit (ie, you aren't making a trade off, you simply lose out on something because you took it in the wrong order). Even when multiclassing weapon, armor, and skill proficiencies--the rules where they actually say that order matters and how it matters--you get something for the choices that seem weaker. For instance, if might be overall superior to take fighter and then wizard (better starting hit points and heavy armor). But if you really want the saving throws from wizard, you can sacrifice the hit points and armor and get the saves you want. (Even that I don't like, but at least it's something.)Class based weapons, armor, and skill proficiencies are spelled out as dependent on the order in which you take them on one hand, and skill and tool proficiency choices are generally spelled out as not dependent on order on the other hand. Then we have scenarios that could fall into either category and they neglect to tell us which. It seems to me that the multiclass rules are intended to address a balance issue that doesn't apply to the other situations, therefore it makes the most sense to take the more generous interpretation in the unspecified situations.I'd take the opposite position simply because I think the multiclass rules work best as the exception rather than the rule.Practical effects:In 3e, unless I was playing a wizard, I would always take the highest Intelligence score I ever intended to have when I created a character. The fact that extra skill points for Int are not retroactive was offensive to my sense of gaming (hit points from Con are retroactive, but Intelligence gets the shaft?) and I refused to deal with it as a player by always avoiding the issue.If a 5e DM was ruling that I didn't get the skill proficiencies or cantrip from gaining levels in another class (not counting the 1st level proficiencies) I would create the character in such a way as to not suffer a penalty, or I'd shelf the concept and play a completely different character. I wouldn't interact with that rule. The thing is, I think 5e's philosophy of PCs is to let character be cool and not weigh them down with stupid, and I will interpret anything from perspective.To clarify my overall position: Because the rules are not crystal clear in these areas, I'll interpret everything according to my understanding of overall 5e design philosophy as represented in the rest of the game--which is very generous towards players and leans more often on the side of "yes, you get cool" than "no, you can't do that."</blockquote>

Verification