It was just some code that was attempting to match an attack trait with "range" in it, and ignore the range info after. I've fixed the code in the ruleset. Hopefully in time to go out in the next release. Thanks again for reporting.
EDIT: It did make it into the FG update cycle in time. So this should be fixed in Release 17b, available Tuesday next week (August 11th).