Radar API problem in Jumpgate

Hi! I use the Radar api in my game, but I migrated the games to a jumpgate version. All of my API-s working properly but the Radar API is not. When I try to use a Detect Magic macro, I got "Unhandled exception: Unexpected end of JSON inpot" error. With some investigation I found the core of the problem. The problem is with the Line of Sight function of the Radar API. If it turned on, the API is not working. The function responsable for checking, the found element is in line of sight, or can't see, because blocked by a wall. This error occurs only if I want to use the API on a map, where I used the jumpgate tools for creating the dynamic light walls.

Hi, Pivi... Jumpgate significanty... changed... ...the way it stores and handles paths objects (like lighting lines). Any script built to use paths (like Radar) will need to be updated. Not to speak for David M. (who is aware of this breaking change, I know), but there is significant flux for the scripting community, currently, with Jumpgate and Beacon functionalities in various states of readiness but enthusiastic states of release, and I think every scripter is taking their own approach to when/how/if they are going to update a given script... or even at what point things will have settled down enough for them to answer those questions.

Most of the API changes from Classic to Jumpgate have been minor, but path handling was a sea change that should never have been done. It breaks scripts that use paths to the level of sabotage. I cannot fathom why the coordinate system was flipped.