Issues with "range" on melee weapons
See original GitHub issueMelee weapons in equipment currently say "range": { "normal": 5 }
, which is iffy in some regards:
- Technically melee weapons don’t have range (unless they also have thrown), they are specifically not ranged.
- The numerical data currently doesn’t reflect Reach property.
My first thought was to bump this by 5ft on Reach weapons, but after a closer look range isn’t accurate at all. For the record there is also a separate throw_range
property for thrown.
As far as I can see, the default reach is a rule, not an aspect of any specific weapon:
A melee weapon is used to attack a target within 5 feet of you
So rules-wise this is strictly binary (does weapon have Reach property), not numeric (weapon has X feet reach).
Issue Analytics
- State:
- Created a year ago
- Comments:17 (10 by maintainers)
Top Results From Across the Web
Problems with Extended Melee Range | VS Battles Wiki Forum
Now, the main issue involves the melee weapon parts. In "Standard Range," weapon examples are listed as "Knives/daggers, gauntlets, ...
Read more >Why doesn't melee weapon show range ? : r/Warframe - Reddit
The problem is that the range will be different for each attack, and will potentially vary with stances. A single "range" stat isn't...
Read more >Why dont they show melee weapons range? - Warframe Forums
False, range is the length of the weapon. A Dakra Prime does not magically change length when you do a slide vs combo...
Read more >Melee weapons range/reach stat in 40k? - Forum - DakkaDakka
Having recently started an aos army, I've been wondering if melee weapon ranged could, or should, be added to 40k.
Read more >Now that ranged can not escape melee range
Melee leaves no room for ranged to do damage, which is why ranged ran away in the first place. The time to kill,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, as above, there are API convenience considerations. I think it might be best to just bite the duplication and have both derived effective reach property at root (5 or 10 in feet, I vaguely remember magic weapons might extend this? even if there aren’t any like that in SRD) and Reach entry in properties list.
To be clear my concern isn’t making API minimal, my concern is making language of the API consistent with that of the rules. 😃
P.S. against having reach in range because we get full circle to initial problem of melee weapons not having Range. 😃
Oh right. We were just renaming that to
range
?