Reply to thread

Message

<blockquote data-quote="mlund" data-source="post: 5933468" data-attributes="member: 50304">They'll be some confusion between Core Rules, Modules, and House Rules though. Some people are just ridiculously offended and defensive when you call anything in their personal home-brew scenarios &quot;house rules.&quot; They've kind of latched onto an &quot;everything is optional!&quot; mantra to reject this horribly traumatic label.There's Core Rules - the underlying premises on which you build your custom D&amp;D game as opposed to something like Vampire or GURPS. Modules are built to fit onto these premises - adding to or subtracting from them with a deliberate purpose and professional development and balancing.House Rules are things Players and DM's implement outside of Core and Modules in order to make their game more fun. Maybe they want to play historic Greyhawk so they don't have Dragonborn. Maybe they hate the idea of &quot;damage on a miss&quot; or &quot;unlimited magic&quot; so they start banning the Slayer feat and all Cantrip spells. These kind of a la carte changes to the Core Rules without the benefit of professional development, balance, or publishing are precises House Rules and they come with no warranties.If enough tables have to adapt House Rules to address a particular game feature that just doesn't work, then you probably have a design defect.&quot;This PHB comes with Dragonborn. I hate Dragonborn. People shouldn't call it a House Rules when I ban Dragonborn,&quot; is not a design defect. (Substitute whatever pet-peeve you want for the word &quot;Dragonborn&quot; - &quot;automatic damage,&quot; &quot;hit dice,&quot; &quot;clerics with shields,&quot; &quot;warlords,&quot; whatever.)- Marty Lund</blockquote>

[QUOTE="mlund, post: 5933468, member: 50304"] They'll be some confusion between Core Rules, Modules, and House Rules though. Some people are just ridiculously offended and defensive when you call anything in their personal home-brew scenarios "house rules." They've kind of latched onto an "everything is optional!" mantra to reject this horribly traumatic label. There's [B]Core Rules[/B] - the underlying premises on which you build your custom D&D game as opposed to something like Vampire or GURPS. [B]Modules[/B] are built to fit onto these premises - adding to or subtracting from them with a deliberate purpose and professional development and balancing. [B]House Rules[/B] are things Players and DM's implement outside of Core and Modules in order to make their game more fun. Maybe they want to play historic Greyhawk so they don't have Dragonborn. Maybe they hate the idea of "damage on a miss" or "unlimited magic" so they start banning the Slayer feat and all Cantrip spells. These kind of a la carte changes to the Core Rules without the benefit of professional development, balance, or publishing are precises [U]House Rules[/U] and they come with no warranties. If enough tables have to adapt House Rules to address a particular game feature that just doesn't work, [b]then[/b] you probably have a [U]design defect[/U]. "This PHB comes with Dragonborn. I hate Dragonborn. People shouldn't call it a House Rules when I ban Dragonborn," is [B][U]not[/U][/B] a design defect. (Substitute whatever pet-peeve you want for the word "Dragonborn" - "automatic damage," "hit dice," "clerics with shields," "warlords," whatever.) - Marty Lund [/QUOTE]

Verification