You have to have a comma after each function definition in the map script (other than the last one), like in the attached.
@Miscreant The persist.js map script syntax is a bit weird, basically the whole file is a big object literal which is eval()'d. It was done that way as a necessary evil because otherwise, with traditional JS, all the functions in the file would be global. Putting them into an object which can be eval'd gets around that limitation.
Also, I can infer that zones and triggers would still be need to coded internally in the map file. Looking through the 1.5 api file(which I started this project with) it does not appear that the zone or triggers can be created externally with coding.
I'm going to attempt to port the project maps to use the persist functionality. At over 400 maps this could take some time. I think the levels will be the most time consuming to port over.
Another benefit to persist.js which I'm sure you've seen already is that you can use the debugger to step inside the map scripts.
Quote from: Miscreant on September 25, 2017, 11:06:10 amI'm going to attempt to port the project maps to use the persist functionality. At over 400 maps this could take some time. I think the levels will be the most time consuming to port over.I could pull all the scripts out with a script I have if you want me too... Let me know if you want the help.