Bob said: What is not working is the global pad list. Here is the error below. I would like a way to just delete all telepad data and start over. TypeError: Cannot read property 'get' of undefined TypeError: Cannot read property 'get' of undefined at apiscript.js:3535:73 at Function.each (/home/node/d20-api-server/node_modules/underscore/underscore.js:188:9) at apiscript.js:3531:35 at Function.each (/home/node/d20-api-server/node_modules/underscore/underscore.js:188:9) at apiscript.js:3524:23 at Function.each (/home/node/d20-api-server/node_modules/underscore/underscore.js:193:9) at padGlobalDisplay (apiscript.js:3521:15) at msgHandler (apiscript.js:4062:21) at eval (eval at <anonymous> (/home/node/d20-api-server/api.js:154:1), <anonymous>:65:16) at Object.publish (eval at <anonymous> (/home/node/d20-api-server/api.js:154:1), <anonymous>:70:8) The global teleport pad list doesn't work because some pads are attempting to show the name of a linked pad that no longer exists, i.e: invalid data. I apologize for this oversight. This should also follow for showing the pad list for the page that has the invalid data, and for trying to edit the individual pad. Finding out which one this is would allow you to delete or modify the individual teleport pads that are the source of the invalid data. This has been corrected in the gist associated with the one-click, but not in the one-click yet. The corrected one-click (version 1.2.1) will be available on Tuesday; if you need it corrected right away, you can disable the one-click version and paste in the content from the gist, as mentioned here . The gist version has a catch for invalid data (data that does not point to a graphic token anymore, a token that has been deleted). The defect you're pointing to above specifically means there is a token that has a deleted token id on its own target list. There is not a global purge for this; instead the version in 1.2.1 catches for this and substitutes the text "invalid data" which can be corrected on the individual pad by resetting or re-selecting its target links. Individual token links are not kept in a global object; instead the individual tokens are used as the data store and have all of their associated information encapsulated. I could listen for "destroy" events as well, and remove destroyed graphic tokens designated as teleport pads from any link lists - I'm concerned if there is an "undo" that the damage has been done. It would be better if I presented a button in chat to optionally remove the deleted token id from any link lists it might be on; with the invalid data catch, this would allow a GM to undo with no consequence, and either bypass the check, or click the chat button to remove the deleted tokens from any lists it might be on. My only concern is a multi-delete: does the event present a list of all elements deleted, or a series of delete events? Testing this now, and as I have a function for pulling the full global teleport pad list (and since it is "live" and the deleted token is already off it) I should be able to present the chat button (one per deleted teleport pad token) to remove any references and prevent the "invalid data" issue; however I'll still keep the invalid data check, as deletion isn't the only way to get invalid data into a token's link list. Tested and it works - I'll put in a confirmation message to chat with the number of references removed for confirmation and a link to the main menu, and then put it up on gist - I'll ask folk test it; I'm not sure if I want to push it instead of the current 1.2.1 without more testing, so it will probably go in the Tuesday after next (if anyone is working then - we're getting into the holidays) Version 1.2.2 with deletion clean up Edited to add: the undo function actually spawns a new token with a new token id, so delete with undo will result in invalid token references.
