Power Range tag for export template?

[Heroman]

Is there an export template tag for attack power's range (or if a general 'range' which could be shared by movement, etc)?

[Simon]

Yup.

Under POWERS, you have "POWER_RANGE" (as well as "POWER_DMG")

Under EQUIPMENT, you have "EQUIPMENT_RANGE" (as well as "EQUIPMENT_DMG")


Hope this helps!

[Heroman]

Mostly helps, except I think Limited Range is wrong. The help says 'This Limitaton represents a Ranged Power which does not work at Range'.
It should 'This limitation represents a ranged power whose range is less than normal.' It also needs to allow the GM (or I guess character creator) to specify the range of the device.
In example: Artificial gravity is based on a TK, but most AGs only are good for a hex or 2 (1 level).
Also, is there a tag for range units (inches, km, etc)?

[Simon]

I'll get the definition fixed on Limited Range.

As for setting the actual range when taking that Limitation, you should simply include it either in the Limitation's display value (e.g."Limited Range (10")") or in the Power's notes.

There is no tag for range units. The application assumes inches (Hero System inches). If you want to include the units in your template, then just include them after the tag.

[Heroman]

True, but I was hoping to build an export template for equipment which generated an overall eqipment table (Name, Real Cost, Range, etc) for quick reference followed by the full text. It works with the POWER_RANGE, but that will be invalid for powers where I want to limit the actual range with Limited Range. Is there any way to force a given power to be a specific range during it's creation (or at least override the POWER_RANGE value)?
Also, the only thought about range units is because of the whole megascale. I just cannot tack on 'inches' since the power may be adjusted up. No biggie tho.

[Heroman]

Oh, also, is there a new PDF with the tags like POWER_RANGE? I did not see that in the distributed PDF or on the zipped verion available on the website...

[Simon]

Check the update page for the release notes on each update. We're only going to be updating the PDF documentation with each major build (v1, v2, etc).

The update page contains all of the additions for each version.