Reply to thread

Message

<blockquote data-quote="Kraydak" data-source="post: 4553933" data-attributes="member: 12306">Doesn't matter.&nbsp; Even if it can't be used as a melee weapon, it still *is* a melee weapon.&nbsp; Similarly, if someone has an attack that blows up melee weapons for AoE damage, and I'm in in Sword God Beta's AoE, my axe can still go boom.In the javelin case, the only way to remove the melee-weaponness bit is by doing something drastic enough to remove it from the table of melee weapons (and boosting/reducing its weight out of the improvised categories if you want to tie things to the object instead of the table entry, which I strongly advise against).&nbsp; As that is where it is picking up the &quot;heavy thrown&quot; property, you then can't throw it.&nbsp; Which is the line of argument that says that it must stay a melee weapon:if it EVER stops being a melee weapon, then the javelin entry in the simple melee weapons, 1-handed ceases to apply, so the &quot;heavy thrown&quot; goes away, and you can't throw it.Now, if the javelin had two different entries, one in the melee table (without heavy thrown) and one in the ranged table (with heavy thrown), THEN we would be arguing about whether more than one table entry can apply at the same time.&nbsp; And life would be more complicated.To rephrase a last time:Is there anywhere in the rules that it says that to be a melee weapon, you need to be able to make a melee attack with it?&nbsp; I sure hope not, because there are circumstances where you may be unable to make a melee attack with a weapon yet it should still count as a melee weapon, but such a rule would give you the argument.</blockquote>

[QUOTE="Kraydak, post: 4553933, member: 12306"] Doesn't matter. Even if it can't be used as a melee weapon, it still *is* a melee weapon. Similarly, if someone has an attack that blows up melee weapons for AoE damage, and I'm in in Sword God Beta's AoE, my axe can still go boom. In the javelin case, the only way to remove the melee-weaponness bit is by doing something drastic enough to remove it from the table of melee weapons (and boosting/reducing its weight out of the improvised categories if you want to tie things to the object instead of the table entry, which I strongly advise against). As that is where it is picking up the "heavy thrown" property, you then can't throw it. Which is the line of argument that says that it must stay a melee weapon: if it EVER stops being a melee weapon, then the javelin entry in the simple melee weapons, 1-handed ceases to apply, so the "heavy thrown" goes away, and you can't throw it. Now, if the javelin had two different entries, one in the melee table (without heavy thrown) and one in the ranged table (with heavy thrown), THEN we would be arguing about whether more than one table entry can apply at the same time. And life would be more complicated. To rephrase a last time: Is there anywhere in the rules that it says that to be a melee weapon, you need to be able to make a melee attack with it? I sure hope not, because there are circumstances where you may be unable to make a melee attack with a weapon yet it should still count as a melee weapon, but such a rule would give you the argument. [/QUOTE]

Verification