Confounding Shot (3.5e Feat)
 |
This page was marked as abandoned on 19:31, 25 October 2020 (MDT) because: Issue(s) unaddressed for over a year. (discuss) If you think you can improve this page please bring the page up to the level of other pages of its type, then remove this template. If this page is completely unusable as is and can't be improved upon based on the information given so far then replace this template with a {{delete}} template. If this page is not brought to playability within one year it will be proposed for deletion. |
 |
This page is of questionable balance. Reason: Needs to be rewritten to better use existing 3.5e mechanics.
|
Confounding Shot [Fighter]
3e Summary::You may draw an enemies attention solely to you with a shot.
Benefit: Once per round, if you reserve your action in combat, and an enemy makes a charge attack against one of your allies within the total range of your readied ranged weapon, you may make a ranged attack against that enemy, forcing him to stop his charge, and face you. If the enemy is carrying a weapon and your attack does more than 10 damage, he is disarmed; if he takes more than 20 damage he is both disarmed and prone. This enemy, whether the attack hits or misses, must attack you (and no one else) on his next action, or become shaken.
Back to Main Page → 3.5e Homebrew → Character Options → Feats → Fighter
gollark: It would be neat if they were cryptographically signed too, but it turns out I have no idea what actual algorithm the potatOS ECC library is implementing, oops.
gollark: So, progress on the potatoupdates™ system, I now have a script generating manifest files which are deterministically generated from the exact contents of a PotatOS version™.
gollark: > multiprocessing.pool objects have internal resources that need to be properly managed (like any other resource) by using the pool as a context manager or by calling close() and terminate() manually. Failure to do this can lead to the process hanging on finalization.> Note that is not correct to rely on the garbage colletor to destroy the pool as CPython does not assure that the finalizer of the pool will be called (see object.__del__() for more information).Great abstraction there, Python. Really great.
gollark: No, I mean I was reading from underneath the line it highlighted, which was the POST documentation.
gollark: Oh, never mind, the link was just being confusing.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.