Step Counter

[Farratto]

Hi Farratto,

thanks for this extension, my players are really enjoying it, and prefer it over FG Token Lock.

There is one issue we're all struggling with though, and that's that I'm unable to find the settings or combination of options that will allow diagonals to treated as '1st diagonal Move = 5ft, 2nd Diagonal Move = 10ft'. The way it is now with every diagonal square taking 7.5ft of movement, we are very often left with 2.5ft of movement unavailable when hitting the enforced movement limitation (which I always have toggled on), which usually leaves the token between squares.

I understand that the optional rule, as it is written in the DMG, should even stick to this if there is non-diagonal movement between 2 diagonal moves and this may be hard or impossible to code for, but for my table I'd rather have it just treat every 2nd diagonal in a direct sequence as 10ft, and just register any errant random singular diagonal moves as 5ft (this is the way we rule it at my table anyway).

I hope this makes sense?

TLDR: would it be possible to code an option for diagonals to run 5ft -> 10ft rather than 7.5ft -> 7.5ft?

Thanks for all your work, it's much appreciated.

Cheers,

Simon

You're using 5E? I already have that type of diagonal handling set up for rulesets that use it by default. 5E defaults to counting diagnols as 5 feet. I can maybe through in an option to allow it on rulesets that don't normally use it?

[Farratto]

Hi Farratto,

I've also just discovered that this extension seems to be stopping FG from dropping the built in Death Marker blood splats. Tested with only this extension active, and cycling through the various options.

Cheers,

Simon

This is news to me. I'll take a look

[Ludd_G]

You're using 5E? I already have that type of diagonal handling set up for rulesets that use it by default. 5E defaults to counting diagnols as 5 feet. I can maybe through in an option to allow it on rulesets that don't normally use it?

Hi,

yes we're using 5e (sorry I meant to say that in my original post). The 5ft/10ft/5ft/10ft diagonal rule is optional in the DMG but I think widely used. In options 'House Rules' I set the 'Map: Diagonal Distance' to 1.5x, which Step Counter interprets as 7.5ft per diagonal square which isn't correct to the wording of the rule, but FG interprets correctly as 5ft/10ft/5ft/10ft (please see attached).

I hope this makes sense?

Thanks for looking into this.

Cheers,

Simon

[Farratto]

Hi,

yes we're using 5e (sorry I meant to say that in my original post). The 5ft/10ft/5ft/10ft diagonal rule is optional in the DMG but I think widely used. In options 'House Rules' I set the 'Map: Diagonal Distance' to 1.5x, which Step Counter interprets as 7.5ft per diagonal square which isn't correct to the wording of the rule, but FG interprets correctly as 5ft/10ft/5ft/10ft (please see attached).

I hope this makes sense?

Thanks for looking into this.

Cheers,

Simon

Oh, interesting, I didn't notice that FGU was not actually using 1.5x. I wonder if this is just 5E or some weird oversight. I'll get this going for you, one way or another. Look for it in the next version, which will likely be next week.

[Ludd_G]

Excellent! Thanks muchly!

[Moon Wizard]

Every ruleset has a distance diagonal multiplication default of 1 or 1.5 usually. There is an option (HRDD) to change that from ruleset default to 1x, 1.5x or Raw.

Regards,
JPG

[Ludd_G]

Every ruleset has a distance diagonal multiplication default of 1 or 1.5 usually. There is an option (HRDD) to change that from ruleset default to 1x, 1.5x or Raw.

Regards,
JPG

Hi Moon,

we are using the 1.5x house rule in 5e to correctly give us every first diagonal as 5ft and every second diagonal as 10ft, but this extension, Step Counter, with all the same settings, is incorrectly treating every diagonal square as 7.5ft which is not correct to the optional rule (please see the screen grab attached to the previous post). I'm hoping Farratto can change this behaviour to mimic FG's implementation of 5ft, then 10ft, then 5ft, then 10ft etc. This will allow us to use Step Counter instead of FG's Token Movement Lock, as this would be my player's preference.

Cheers,

Simon

[Ludd_G]

Hi Farratto,

I just tried the new version of Step Counter and it works perfectly at 1.5x for a single movement (without dropping a 'step' indicator), so thanks very much for that! But if the GM or player moves one or more diagonals, then drops a 'step' indicator as they decide their next move, then decides to continue on a diagonal this is treated as a new movement so doesn't reflect how many, if any, diagonals were traversed during the same turn, previously, if you see what i mean? The present implementation will happily cover both me and my players for 95% of our diagonal requirements, and is a great improvement on the previous version, so we'll definitely be sticking with it, but I just thought I'd let you know my initial impressions.

Thanks loads for all your work, it's much appreciated.

Cheers,

Simon

[Farratto]

Hi Farratto,

I just tried the new version of Step Counter and it works perfectly at 1.5x for a single movement (without dropping a 'step' indicator), so thanks very much for that! But if the GM or player moves one or more diagonals, then drops a 'step' indicator as they decide their next move, then decides to continue on a diagonal this is treated as a new movement so doesn't reflect how many, if any, diagonals were traversed during the same turn, previously, if you see what i mean? The present implementation will happily cover both me and my players for 95% of our diagonal requirements, and is a great improvement on the previous version, so we'll definitely be sticking with it, but I just thought I'd let you know my initial impressions.

Thanks loads for all your work, it's much appreciated.

Cheers,

Simon

What you're describing is working exactly as intended. You control when it starts counting again. If you dont want it to restart, dont drop a "step". If you mistakenly dropped a step, hit the "undo step" button.

Giving the extension more "smarts" to try to interpret what your intention is instead of doing literally exactly what you tell it, would take a great deal of coding. I'm not prepared to embark on that particular project at this time. When I'm ready to start a new big project, I will likely be attacking difficult terrain.

[Ludd_G]

Not a problem, as i said it's much appreciated what you've done so far.

Thanks again,

Simon