No, it's a bug with the default state of the TurnOrder. TurnOrder on the Campaign object is a JSON string representing an object that contains the TurnOrder information. That string must be parsed by JSON.parse() to get the object. At one point, the version of Node.js that powers the API supported JSON('') returning Undefined, but sometime in the last 4 years, that changed to throwing an exception (the more correct response, honestly). However, this code is old enough that it assumes it will get a falsey value rather than just blowing up. =D I've fixed it and pushed 0.2.7. You can grab the latest here: <a href="https://github.com/shdwjk/Roll20API/blob/master/TokenLock/TokenLock.js" rel="nofollow">https://github.com/shdwjk/Roll20API/blob/master/TokenLock/TokenLock.js</a> I've sent a pull request so it should show up fixed in the 1-Click installs shortly.