Printable View
I'm sorry. I told you the wrong thing. Once you pull the hotkey onto your hotbar, it doesn't know what map to apply to anymore. So then the only way it works is if you are currently "carrying"/"dragging" a token. The selection thing is for using the button on the mapQuote:
Originally Posted by Ludd_G
Unfortunatley, I do not own DCC either :-(Quote:
Originally Posted by *Neuro*
But again, for clarity, the only functions that shouldn't work is the maximizing movement limitation and settings peeds with effects. Prone reminders and the all the other movement stuff should work.
Cheers for the info! I'm going to be trying this out tomorrow night to see if my players like it, and if so I can lose FG Movement Lock.Quote:
Originally Posted by Farratto
Cheers,
Simon
Indeed - use the extensions Aura Effects and Walk this Way, and just drop an „Object“ token with an effectQuote:
Originally Posted by rhagelstrom
and adjust size and form as required.Code:Difficult Terrain Center; Object; SKIPTURN; AURA: 10 all,cube; Difficult Terrain; SPEED: difficult
Oh hey, here I am popping into a thread for another one of your extensions.
QOL question; my players usually have free token movement on big world maps, and we ran into some issues last sess of trying to navigate with the system in play. It seems like "Enable Step Counter" option in the settings is pretty seamless for turning it off and on without performance hitches (even when its mid-use), but could there maybe be a button on the Combat Tracker or part of Image Controls (like clear all indicators, toggle indicator visibility) to enable/disable the counter ala the vanilla FG token lock?
Currently you can just toggle no limitation and also no visibility and then you only have the recorded distance at the top, which can also be cleared easy with the button on the map.Quote:
Originally Posted by metaldm007
I do agree would be nice to have that "No tracking" option, for when the GM wants to have 100% free movement.
I would second this, some way to quickly enable or disable it would go a long way in terms of QoL. Sometimes this extension isn't necessary, but other times it becomes a life saver, so being able to quickly toggle it would help.Quote:
Originally Posted by metaldm007
Lol. I litterally wrote this in at around the time you all posted these messages. Expect it in the next patch.
Step Counter v1.3.0
- FIXED: traveled distance displayed with too many digits with certain conversions
- Added chat messages to help inform on usage.
- Added hotkey-able toggle to map that toggles StepCounter on and off
- Clearing all inits will now automatically clear movement indicators
- New option to auto turn SC on/off with init rolling/clearing, respectively. defaulted to off to avoid confusion. Recommend turning on.
New option explained: Signaling an init rolls automatically turns Step Counter on. Clearing all inits, turns Step Counter off.
Step Counter recognizes 3 methods of signalling an init roll: either by roll all inits, roll PC inits, or by requesting an init roll for at least all (visible) PCs in the Requested Rolls extension. I put "visible" in parenthesis because it respects invisible actors through the Combat Groups extension.
It does not work anymore with the Call of Cthulhu v7 ruleset and the Alien RPG ruleset.
Please update and try again. I made an error, I apologize.Quote:
Originally Posted by Egheal
It works now and one digit after the comma is perfect! thanks a lot.
So 2 questions as a PFrpg player.
1- Is Walk this Way required for Step Counter to fully work? (and if so, what is lost without Walk this Way)
2 - Walk this Way only lists as 5E compatible, so... PFrpg?
I am assuming Wal this way is either Not required or it is not labeled fully on the systems it works on, or Step counter is missing a few things without it.
Oh, I need to update Walk This Way. It is no longer only 5E compatible. Walk this Way is basically split into 2 functionalities: 1> it tracks prone condition and conditions that disallow a person to stand up. On that creature's turn it will ask if they want to stand, if they are able. 2.> It parses and tracks a creature's speeds. 1.> will work on any ruleset, but I may not have all the conditions that affect it in any particular ruleset, see the readme or this thread. 2.> works on any ruleset based on DnD or Pathfinder.Quote:
Originally Posted by Morenu
Every aspect of Step Counter works in any ruleset EXCEPT for one feature: Limiting movement speed of creatures to their current maximum speed. That feature requires the second functionality of WtW.
TLDR; Both WtW & Step Counter are fully functional under Pathfinder and you only need WtW to get the movement limitation feature.
Thx, purchased
I am seeing many of the following in the console logs. I did however not notice any impact in-game.
Similar, a few of the following is also in the console log (again: no noticeable impact):Code:[3/22/2025 7:50:48 PM] [ERROR] Handler error: [string "StepCounter:scripts/manager_movement.lua"]:333: attempt to perform arithmetic on local 'xStart' (a nil value)
Thought I should pass this on.Code:stack traceback:
[string "WalkThisWay:scripts/manager_speed.lua"]:956: in function 'parseBaseSpeed'
[string "WalkThisWay:scripts/manager_speed.lua"]:99: in function 'onRecordTypeEvent'
[string "CoreRPG:scripts/manager_combat_record.lua"]:562: in function 'onBattleButtonAdd'
[string "C:battle_buttons:addct"]:3: in function <[string "C:battle_buttons:addct"]:2>
[3/22/2025 5:50:53 PM] s'SpeedManager.parseBaseSpeed - not nodeCT or not host'
I also have a question on your implementation :)
I like the option of enabling/disabling the Step Counter on combat start/end, and would like to have the same trigger in my Realtime Tracker extension.
I guess that disabling the Step Counter is bound to onCombatResetEvent(). What event is enabling it? onInitChangeEvent(), onRoundStartEvent()?
Thank you for letting me know. The WalkThisWay traceback is a benign old diagnostic that I forgot to take out. I solved that problem months ago. It will be removed in the next patch.Quote:
Originally Posted by Arnagus
The nil error on xStart means that it's trying to process the speed on a token (or CT entry) that is no longer present. It should never happen. Any chance you remember what you were doing when you got this error? Maybe deleted a token or moved it to a new map or teleported or changed token or I dont know what else?
You're right about hhaving Step Counter triggered to auto-turn-off. I do that with this command during onInit(): "CombatManager.setCustomCombatReset(handleClearIni ts);".
I have Step Counter triggered to auto-turn-on in two ways: by piggy-backing into CombatManager.rollTypeInit and making sure we're only signalling combat initiative by rolling all and by rolling all PCs since often we roll NPCs with encounters. I do that with this if statement: "sType == nil or sType == 'pc'".
The second way is by piggy-backing into a Requested Rolls function (since this is how I start combat in my games and I know other DMs do this as well). Same situation where we dont always roll for NPCs. So I have a check to see if we're asking for init on all the PCs that are "visible" in the combat tracker (since many people use combat groups extension). The applicable part of that function looks like this:My getVisCtEntries() function reports all "visible" entries on the CT (gives you a list of all CT entries that are present in the CT after combat groups has filtered out the others). It is as follows:Code:--if option selected, check to see if all visible PCs are being asked to roll init
if OptionsManager.isOption('SC_auto_toggle', 'on') and #aParty > 0 then
local bMissing;
for _,nodeCtTmp in ipairs(WtWCommon.getVisCtEntries()) do
if ActorManager.isPC(nodeCtTmp) then
local bFound;
for _,rActorTmp in ipairs(aParty) do
if ActorManager.getCTNode(rActorTmp) == nodeCtTmp then
bFound = true
end
end
if not bFound then
bMissing = true;
break;
end
end
end
if not bMissing then OptionsManager.setOption('SC_enabled', 'on') end
end
Code:function getVisCtEntries()
local winCT = Interface.findWindow('combattracker_host', 'combattracker');
if not winCT then
winCT = Interface.openWindow('combattracker_host', 'combattracker');
winCT.close();
end
local tNodes = {}
for _,win in ipairs(winCT.list.getWindows(true)) do
local nodeWin = win.getDatabaseNode();
table.insert(tNodes, nodeWin);
end
return tNodes;
end
Many thanks, will try this out!Quote:
Originally Posted by Farratto
Okay, thanks. I will look into it to see if it's GAL token creation/deletionQuote:
Originally Posted by Arnagus
Hello Farratto,
I have a small feature request: Step Counter adds nice litte icons on the map to toggle the Counter, make indicators visible or invisible, and more.
Is there a way to also indicate the current state (enabled/disabled) by different colors, similar to the token vision, token movement, or overall map lock?
This would be great!
https://www.fantasygrounds.com/forum...8&d=1743246066
That is a good idea. I tried to do it when I originally made the buttons, but I failed. There is a complicated reason why it's harder than it seems like it should be. This is why I added the chat messages when you hit those buttons. There's probably a better way of donig this but I just haven't gotten around to it yet. I've been busy adding new features to WtW, SC, and the old Size Matters extension. I'm sure I'll get around to cleaning these buttons up and making them more aesthetic.Quote:
Originally Posted by Arnagus
Thank you for the suggestion. If I knew an easy way, I'd slap it on there, but I don't know an easy way.
If you look at ImageManager script in CoreRPG; the default image buttons have a few "toggle" buttons that you can see as examples (up/down tracked while window open but not database bound); and the WindowMenuManager script has a couple "field" buttons (i.e. database bound).
Regards,
JPG
Thank you for your help. The problem I'm having is that the setting that the button controls is not specific to an individual image window. For the field button: I don't know how to link the field button to a DB entry that is not underneath that specific image window. For the toggle button: if I use the button on one image window, the other image window doesn't "know" it's been toggled somewhere else, so they get "out of sync".Quote:
Originally Posted by Moon Wizard
Yeah, there are no built in buttons that are not tied to the specific image database record, or just not database bound.
You might be able to register a "toggle" style button; and use the fnOnInit and fnOnValueChanged function registrations to set/fix elsewhere; and then manually update the state on other image windows/panels as needed.
Regards,
JPG
I did a little bit more digging into your scripts and figured out a way to make it work. I believe what I did is pretty close to what you're describing above. I copied your field button script and made a couple tweaks so it would use a DB entry outside of the window it's placed in. It's working. Thank you for your help :-)Quote:
Originally Posted by Moon Wizard
Can you link this to my smart watch so it counts my steps?
Only if your creature token has a smart watch ;-)Quote:
Originally Posted by Jiminimonka
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
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
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?Quote:
Originally Posted by Ludd_G
This is news to me. I'll take a lookQuote:
Originally Posted by Ludd_G
Hi,Quote:
Originally Posted by Farratto
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.Quote:
Originally Posted by Ludd_G
Excellent! Thanks muchly!
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,Quote:
Originally Posted by Moon Wizard
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
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.Quote:
Originally Posted by Ludd_G
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.
Not a problem, as i said it's much appreciated what you've done so far.
Thanks again,
Simon