Upgrade your account to a Community Supporter account and remove most of the site ads.
Enchanted Trinkets Complete--a hardcover book containing over 500 magic items for your D&D games!

Reply to thread

Message: <blockquote data-quote="CRGreathouse" data-source="post: 2870925" data-attributes="member: 474">First of all let me say that IK agree with ehren37: feats that happen to require abilities of two classes aren't bad, and can be very good for some effects.  I'm talking only about feats that are used to 'patch' multiclassing, like Ascetic Rogue.As below, feats aren't the proper mechanic for the job.  The idea behind multiclassing is that a character who wants to combine archetypes or class abilities simply takes different classes.  If this isn't feasable, then the essential goal of multiclassing is lost.  Attempts to 'patch' the system with feats is problematic, because:<ul> <li data-xf-list-type="ul">Not every combination will be addressed</li> <li data-xf-list-type="ul">Only some of the archetypes within certain class combinations will be addressed</li> <li data-xf-list-type="ul">Additional base (and even prestige classes) lead to a combinatorial explosion</li> <li data-xf-list-type="ul">Requiring feat(s) for effective multiclassing limits certain archetypes which lack for feats</li> </ul>Don't get me wrong, I like the 3.x multiclassing over the 2E dual/multi rules.  Even so, I admit that the system has problems, most famously multiclassing spellcasters.  I think that changes need to be directed at the system itself.  An example of such a change is UA's <a href="http://www.d20srd.org/srd/variant/magic/magicRating.htm" target="_blank">magic rating</a>.  I'm not saying this is the solution (even to just this part of the problem), just that it's addressing the issue at the heart and not the periphery.</blockquote>

Verification