We've made changes to the API Server along with this morning's update. Main and Dev Are Now Aligned The Main API Server now has the same code that the Dev server was running, including this update: <a href="https://app.roll20.net/forum/post/1884507/api-upda" rel="nofollow">https://app.roll20.net/forum/post/1884507/api-upda</a>... This means that some of your scripts may need to be updated (basically, if there was a "Dev" version of the script, you probably want to start using that now). New Functionality We've added two new pieces of functionality to the API: You can now pass an additional parameter to sendChat() for messages which are not intended to be saved to the long-term chat archive for the campaign. For example, if you are a script that is sending a "menu" in the chat using the API Buttons, this will allow you to do that without cluttering the chat archive for the campaign (and also saves storage space for us :-). To do so, just do this: sendChat("Name", "Message", null, {noarchive: true}); Note that you should pass "null" as the third parameter if you aren't going to use a callback function to receive the output of the sendChat(). You can now generate 3D Dice rolls using the sendChat() function. The syntax is simply: sendChat("Name", "Mesage", null, {use3d: true}); If you pass a player ID to the name parameter, such as sendChat("player|-ABC123"...) the player's color will be used for the dice. Otherwise a default white color will be used. Note that clients can only show the result of one 3D roll at a time, so making a bunch of separate 3D rolls in a row is not useful. Also note that using 3D rolls does place a bit more strain on the QuantumRoll server, so use your judgement and don't perform 100 3D rolls in the space of a second. Use 3D rolls when the roll will "matter" to the player and make an impact on the game.