| Matterhorn731 |
Anchoring says that it can be put on a melee or a thrown weapon. However, its primary use (immobilizing an enemy) requires a melee attack. This seems to negate any benefit of putting the property on a thrown weapon.
- Is the "or a thrown weapon" line an error (i.e. the property can only be put on melee weapons)?
- Is the "with a melee attack" line an error (i.e. the property can immobilize on both melee and ranged attacks)?
- Is neither in error, with the property only working on thrown weapons if they can also be used for melee attacks (such as the javelin, or by using them as an improvised weapon)?
- Is neither in error, with only the "immovable rod" aspect of the property working for thrown weapons? (This seems like a terrible use of a +2 bonus.)
Feedback on how this should be interpreted (or what I'm completely missing) is appreciated! Or maybe a FAQ if I'm not the only one wondering about this?
Source. And FWIW, the property also appears on both the Melee Weapon and Ranged Weapon property tables.
CBDunkerson
|
RAW a thrown weapon with the property can use the 'immovable rod option' normally, but the 'immobilize enemy' option only if used for a melee attack.
That said, it seems possible that RAI was to allow the 'immobilize enemy' effect on a ranged attack. The exclusion of projectile weapons suggests that they didn't want to allow this effect on something like a bow (or arrows) where you could quickly immobilize a group... basically you can immobilize one target at the cost of losing the use of the weapon. That logic works with either melee or thrown. However, thrown has the added advantage of immobilizing them at a range where they can't make melee attacks on you... so that'd be a possible argument for limiting it. It could also be argued that the weapon might need to be in hand to trigger the immobilization effect.
I could see it either way, but I'd lean towards allowing it on thrown attacks.