Reply to thread

Message

<blockquote data-quote="I'm A Banana" data-source="post: 6048705" data-attributes="member: 2067">It's then a question of DM authority.If what you want at your table is a strong association between class and mechanics, you can have it: you pick Mechanic X, tie it to Class Y, and tell players, &quot;If you want to be a Wizard, you use Vancian slots. That's what wizards are in my world.&quot;D&amp;D, if it's smart, isn't going to tell you that you have to do it one way or another. The game is yours, after all, not theirs. Identifying classes with mechanics can be a powerful way to create an identity or a unique twist on your world. When Billy (who loves to play wizards) plays a wizard in your &quot;Wizards are Vancian&quot; table, it's going to be a unique experience from when he plays a wizard in Erica's &quot;Everyone has AEDs&quot; world.D&amp;D isn't a game that must be played a certain way, so it'd be a mistake to say that a given class MUST be played with a certain mechanic at the level of the rulebooks.It's fine for individual DMs to say that, though, and if it's important to them, they should.It'll give you a default -- simple, basic, functional, and easy. Something that newbies and eight year olds and casual players can grasp and play quickly. And then it'll leave it up to advanced DMs (like us here on ENWorld) to tweak the system to the way they want it. DMs like us do that anyway, this just makes it easier. If what you want is a strong class identity at your table, I imagine D&amp;D5e has your back. If what you want is people you're not playing with to share that identity...that might be off the table for the basic game. But I also don't know why what other people do at their table would necessarily matter to you. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink&nbsp; &nbsp; ;)"&nbsp; data-smilie="2"data-shortname=";)" /></blockquote>

[QUOTE="I'm A Banana, post: 6048705, member: 2067"] It's then a question of DM authority. If what you want at your table is a strong association between class and mechanics, you can have it: you pick Mechanic X, tie it to Class Y, and tell players, "If you want to be a Wizard, you use Vancian slots. That's what wizards are in my world." D&D, if it's smart, isn't going to tell you that you have to do it one way or another. The game is [I]yours[/I], after all, not theirs. Identifying classes with mechanics can be a powerful way to create an identity or a unique twist on your world. When Billy (who loves to play wizards) plays a wizard in your "Wizards are Vancian" table, it's going to be a unique experience from when he plays a wizard in Erica's "Everyone has AEDs" world. D&D isn't a game that must be played a certain way, so it'd be a mistake to say that a given class MUST be played with a certain mechanic at the level of the rulebooks. It's fine for individual DMs to say that, though, and if it's important to them, they should. It'll give you a default -- simple, basic, functional, and easy. Something that newbies and eight year olds and casual players can grasp and play quickly. And then it'll leave it up to advanced DMs (like us here on ENWorld) to tweak the system to the way they want it. DMs like us do that [I]anyway[/I], this just makes it easier. If what you want is a strong class identity at your table, I imagine D&D5e has your back. If what you want is people you're not playing with to share that identity...that might be off the table for the basic game. But I also don't know why what other people do at their table would necessarily matter to you. ;) [/QUOTE]

Verification