Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="Tonester" data-source="post: 4368556" data-attributes="member: 71788">The problem with doing a Fighter Paragon is the fact that EVERYTHING a fighter does through all 30 levels is strength-based.  So, at best, I could add 3 powers for a Paragon Path that allows a Dex-Based defender to be effective at both attacking and at their light armor defense.Based on many of the powers, feats, and utilities I've already written, it would be an awful waste, imo.  This class is meant to do LESS damage than a Fighter (not hit less often).  It is geared around immediate actions, debuffs, and guarding adjacent teammates.  There isn't enough flexibility in the Fighter core class to accomplish this without making the most powerful Paragon Path ever - not something I'm interested in doing for obvious reasons.The "general rule" is that Shield Weapons will inherit the +magical bonus (and the +crit bonus) of the user's normal weapon.  They don't inherit powers, however.  I will be including additional Magical Shields that may "specifically" alter the "Shield Mastery Feature" and "Shield Fighting Feature" of the class.  The reason for this decision was to make the class as easy to incorporate as possible for DMs without requring them to recompile treasure lists or retool already existing adventures or campaigns at all.  The new magical shields will just have "Mathorian specific" rules which will grant additional bonuses/powers/effects/damages in the hands of a Mathorian or operate as any other magical shield for other players.*edit*I may re-evaluate the Paragon Fighter issue but this would involve 1 of 2 things (which I'm not completely okay with) 1) Re-tooling quite a few of the existing Fighter Exploits or 2) Adding a ton of new Fighter Exploits.First off, WoTC would not like me releasing something that has all the Fighter Exploits word for word with 1 simple line added to each.  Secondly, having everything that pertains to your class in ONE document is essential for incorporation and adoption, imo.  It allows DMs to hole-punch and add it to a binder and be done with it without infringing on any copyright laws or changing documentation that exists for already existing classes.</blockquote>

Verification