parse error from Path Math api

Thought I'd post here first just incase anyone else has seen it before I send it to Help Centre. Situation: I've copied an existing game (including resources and API mods) and made it a Jumpgate game. I then added a new map and drew transparent lines on it, this went ok. Maps has daylight and tokens have vision I then moved an existing character onto the map and I'm getting an odd problem when I try to move character (happens with a newly created character as well), I get the following error; (From Path Math): An error was encountered while trying to parse the JSON for a path. See the API Console Log for details. and all it shows in the console log is "Error parsing Roll20 path JSON: "

Hey, Norman... Yeah, Jumpgate broke paths for existing scripts... with rather unapologetic, "We have come to liberate your paths" energy. Scripts like PathMath (and all of those that would rely on PathMath) will therefore not function properly in Jumpgate. This is a known issue that is not likely to be resolved anytime soon, since I think most scripters are waiting to see the extent of the required changes once Jumpgate settles into a finished product. Jumpgate games will, in the meantime, have to operate without those scripts, something that will -- predictably -- lower user satisfaction. I've said before that scripts are a low-investment, value-add for Roll20 (they don't have to write them, they just have to reap the rewards of the Pro sub fees of people wanting to use them). This all could have been so easily avoided with a little outreach to the scripting community, soliciting feedback and sharing plans for breaking changes.

Thought it might be something like that - now to figure which of my scripts uses it :) and see if I can substitute something else. Unfortunate that they trashed the paths functionality, as you say all it's going to do is piss of users.

What timmaugh said. API treatment Paths is truly messed up on Jumpgate because of this change and may not be able to be fixed. And they didn't have to be. Or if they did, no explanation or justification has ever been given.

Dang it.  On the one hand I love finding an answer on the forums.  On the other hand I hate that the answer isn't one I like. Is there anyway to encourage them to look at this?  Seems like it should be on the Priority Fixes list and it isn't.  

It isn't on a "Priority Fixes" list because it isn't on *any* fixes list. It's actually on the "we like this so much, we've built all of this other stuff around it" list. They're too far down this road, apparently. Roll20 has ever had two cardinal sins: 1) a lack of standard protocols (or at least, not following them) around QA testing new features *before* they get released 2) silo-ing themselves in an ivory tower of development, writing the tools people don't need, never understanding how people actually use their product In the case of paths in Jumpgate, it's a collision of those two sins at the same time. And, in an unfortunate turn for the user experience, it happens to hit while Roll20 is also trying to push Beacon, which fundamentally breaks scripts in other ways.

I'm having exactly the same problem. I gave into the constant nagging to try Jumpgate and now regret it, I am a pro member exactly because I use many API scripts. I regret it because I have new content in the new version, so even though I have a back up, it is out of date. No wonder Roll20 is losing former fans. Does anyone have a handy list of popular APIs that use PathMath - it's very frustrating getting a beep and an error everytime I - or a player - move a token.

Here is a quick list just scanning the GitHub repo for references to PathMath: AreaOfEffect checkLightLevel CustomStatusMarkers DoorKnocker Gruntfile Hexploration ItsATrap KABOOM LightCrumb LineOfSight OneWayDynamicLighting PageNavigator PathSplitter This would just be the start, though. To get an exhaustive list, you'd have to search for each of these to see if they are referenced in any other scripts. Some, like OneWayDynamicLighting, I think are outdated just with the dynamic lighting update. But others, like checkLightLevel, is referenced... by at least Fetch, which is referenced by the Metascript Toolbox. So, the effects of this continue to compound.

Amazing how it's only paying customers that are affected by this.  It pretty much locks us out of JumpGate.