Well, it's good (and bad, lol) to see I'm not the only one experiencing the issue. And it seems we all experience it in the same place. I, too, had run the script in terminal and was informed the error was on like line 369 or some where around that point and had glanced at the script briefly to see if it was malformed and it looked about right to me, I simply didn't know the calls it was using so I couldn't be certain. I will try that fix for the script that AMSTraute proposed.