Script error after changing and then changing back camera info

I have this level I'm working on, and I was unsatisfied with the default positions of the camerapaths or however you call them, the pathnodes that are positioned in a circle around the level to give you that preview before you press play. So I went into the code and changed the Z position on all of them so that they're all 410. Then when I opened up PQ, I got an error saying something like "because of an error we can't have the panning camera shots". Weird, but I thought no problem, I'll just revert the code back to how it was before. And if that doesn't work, I'll just delete the whole camera section of the code of my .mis (since I know there are levels without that section in there). When I tried both of those options and pressed play on my level, I ended up getting the error you see in the pic below, and no panning shot of the level. The weirdest thing about this is that I got the code back to exactly how it was before the whole mess started, and for some reason it's still being stubborn. Pls help me know how to get the camera stuff working again, how to be able to play the level again, AND how to change the camera paths to my liking. Mac OS Sierra 10.12.5.

EDIT: I managed to narrow down where the problem lies. I decided to create a 'new mission' (which automatically generated camerapaths into the code btw), and then copy stuff into it one piece at a time from the pre-existing mission file I was working with before. I found that the level loaded up fine until I copied the "new ScriptObject(MissionInfo)" section. That's when I started getting the script error. So now I'm able to load the level up and play it fine, but I'm still not getting the spinning camera preview. So now that's all that needs to be fixed.

New mission info:


Old mission info:

At least in your old description you're missing a semicolon after the startHelpText. Here are a few other issues you may run into:

- TextEdit on Mac likes to use “smart quotes” instead of "basic quotes," make sure to disable them in the edit menu
- Check for missing semicolons and matched quotes. If any of the strings in your info have double quotes in them, make sure to put a backslash \ before them so it doesn't end the text too soon
- Check for matched curly braces { } and that objects end with };
- Check the console.log and see where it highlights the error. Also check the line that it displays in the error box.