3.5e Rules

Back to Main Page 3.5e Homebrew

Variant Rules

Supplemental Variant Rules

A supplemental variant rule can be implemented into a campaign with little or no change in the core dynamics. These rules cover an area that the core rules do not cover or do not cover well.

{{#dpl: debug=1 |category=3.5e |category=User |category=Variant Rule |category=Supplemental Variant Rule |notcategory=Supplement |notcategory=Psychic Powers Subrule |format=,* [[%PAGE%¦²{#replace:²{#replace:²{#replace:%PAGE%¦(3.5e¦}²¦(3.5e¦}²¦Variant Rule)¦}²]]\n, |order=ascending |columns=6 |rowcolformat=width=100% }}

Transformational Variant Rules

A transformational variant rule, when implemented into a campaign, will change the core dynamics. These rules change the core rules to make them more playable or more realistic while staying within the d20 framework.

{{#dpl: debug=1 |category=3.5e |category=User |category=Variant Rule |category=Transformational Variant Rule |format=,* [[%PAGE%¦²{#replace:²{#replace:²{#replace:%PAGE%¦(3.5e¦}²¦(3.5e¦}²¦Variant Rule)¦}²]]\n, |order=ascending |columns=6 |rowcolformat=width=100% }}

Radical Variant Rules

These are variants which completely overhaul the mechanics of the game both large and small, and often bear only a resemblance to the d20 system.

{{#dpl: debug=1 |category=3.5e |category=User |category=Variant Rule |category=Radical Variant Rule |notcategory=Supplement |format=,* [[%PAGE%¦²{#replace:²{#replace:²{#replace:%PAGE%¦(3.5e¦}²¦(3.5e¦}²¦Variant Rule)¦}²]]\n, |order=ascending |columns=6 |rowcolformat=width=100% }}

Not-Categorized

These have yet to be categorized for how they implement into typical D&D rules. Please help and categorize these.

{{#dpl: debug=1 |category=3.5e |category=Variant Rule |notcategory=Transformational Variant Rule |notcategory=Supplemental Variant Rule |notcategory=Radical Variant Rule |notcategory=Supplement |format=,* [[%PAGE%¦²{#replace:²{#replace:²{#replace:%PAGE%¦(3.5e¦}²¦(3.5e¦}²¦Variant Rule)¦}²]]\n, |order=ascending |redirects=include |columns=6 |rowcolformat=width=100% }}



View recent changes for all variant rules

gollark: <@498244879894315027> What are you trying to access it *from*?
gollark: Look, it says there, > By design, the POST request method requests that a web server accepts the data enclosed in the body of the request message, most likely for storing it.
gollark: The urlencoded MIME type/format doesn't mean it's sent in the URL, just that it uses similar encoding to query strings.
gollark: POST data isn't in the URL though, it's sent as the body.
gollark: The reason they *do* is probably just consistency with other methods (it would be very annoying if they worked very differently to GET routing-wise) and so requests can be routed to the right handler more easily.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.