Range Finder for Large Tokens

[Blackfoot]

Was there ever any sort of resolution for this problem?
The range to a large token is always off by one. (more if the token is larger than large or if there are 2 large tokens)... couldn't you beat this issue by factoring the space increment into the range finder?

[Blackfoot]

I'm seeing this as a particular problem in HEX mode.. but it is also a problem in SQUARE mode if you change the size after the token is added to the map.

[Callum]

As an aside, what is the rule for calculating range to or from a Large creature in 3.5E/PFRPG? I'm asking because I don't believe there is one!

[Blackfoot]

Isn't it pretty obvious that when 1 large creature throws a rock at another large creature and there are 2 squares between them that they are 10' apart? If the creature moved 10' they would be adjacent. To hit them would require a throw that covers 15'.

Or in scaled HEX that they are 2 scale inches apart. To hit them would require a throw that covers 3".

[Blackfoot]

This actually seems to mostly work right with SQUAREs as long as the scale for the tokens is set BEFORE they are placed, if you set it after it screws up.
In HEX it screws up both ways.

[Blackfoot]

Looking at this harder... this seems to be an error in my Champions ruleset but not in the live PF version. I don't think I do anything with scaling.. so am I breaking something somewhere or is there a file that I need to pickup or tweak to make this work using the Core?

Hrm.. although it does the scaling ... the distances seem to be off for HEX in the live version as well.

Wait.. is it assuming that a 10' creature is occupying 3 hexes? It won't let you place on vertices so that doesn't really work.

[Moon Wizard]

There is no support for targeting distance calcs in hex grids for large tokens. Distances are purely center to center point.

When I was looking at large token support for distance calcs, hex grids quickly became complex because it is unclear what a "large" token means (ie depends on system). Is it 3 hexes? Is it 7 hexes? Is it something else? Are large tokens always circular? If 3 hexes, then vertex placement of tokens is required, and makes token/pointer placement much more finicky. Since it wasn't clear, I left distance calcs on hex grids as center to center only.

JPG

[Blackfoot]

Seems like vertex placement would be a good option. Placement in general is a bit buggy right now. Relaxing the placement restrictions would actually help. I agree that the 3 and 7 question is out there, I would allow for both since both are valid considering a '10 foot' and '15 foot' footprint. 1, 3, 7, 12, 19...

[Moon Wizard]

Vertex and center placement support is available already, but only center placement is used by default. In the ruleset XML, you can specify that vertex and center snapping be used.

JPG

[Blackfoot]

Vertex and center placement support is available already, but only center placement is used by default. In the ruleset XML, you can specify that vertex and center snapping be used.

JPG

Where do I find this setting?