Confirmed - my issue is done. MANY thanks!
Printable View
Apologies everyone. I made a major error in the last update. I introduced data corruption into the movement data (only data that I store). It has been fixed now so no more NEW corruption will be introduced.
But if you get a creature behaving strangely in any of the ways that Walk this Way or Step Counter does (moving strangely, reporting weird numbers on distance traveled, speed numbers and types giving strange results), delete the CT entry and then recreate it. That will remove all the corrupted data.
Again, apologies for the inconvenience caused. Hopefully it will be minimal for you.
Cyberpunk Red is Core RPG ruleset. It uses meters for movement. 2m/map square and each character can move a number of squares equal to their MOV stat.
So, Step Counter will work with all coreRPG rulesets already. But there are some features of Step Counter that need Walk this Way to work properly. Walk this Way is not currently set up for Cyberpunk Red, because I don't own it. In order for me to get Walk this Way going on Cyberpunk Red, I would need to know, at minimum, where the MOV stat is stored in the db.xml for both PCs and NPCs. With just that much information I can make some educated guesses and maybe get it going without actually testing it because I've set up so many other rulesets. But really, for me to make it work properly, I would need to own the ruleset so I can do testing.
As far as the meters goes: WtW and SC are already setup to use the units of your choice, and however you have the map set up (respectively).
I wouldn't know where to start to try and locate the MOV stat in XML files. Figured it couldn't hurt to ask. Thanks for the quick reply.
I can probably find it if you can give me a copy of a db.xml from a campaign running that ruleset?
Hi there! Caught an error when adding an encounter to the combat tracker. Just walk this way and step counter loaded. Does not matter if the NPC's are on a map or not. Thanks for your time and attention creating this wonderful extension!
Attachment 64659
Thank you for reporting. I also got this error one time when adding an encounter to the CT, but then it never happened again. I made some changes to protect against this type of error but honestly not sure how it happened in the first place. But it shouldn't happen again.
Thanks! I'll give it a test later on and see how it goes.
Edit: It's working like normal now, no more error on add to combat tracker. Perfect!