Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

noarchive:true bug is back with a vengeance

1456234614
Lucian
Pro
API Scripter
In a new campaign, I added a single script with this content: on("ready",function(){     'use strict';         on('chat:message', function(msg) {              log(msg);              if(msg.type !== 'api') return;             sendChat('DynamicLightRecorder', 'This is a response', null, {noarchive:true});         }); }); After sending a few messages in the chat window, some with '!' at the front, and some without, the chat window starts to fill up with "This is a response" messages even without any further input. Looking at the log, it appears that the API is getting fed spurious chat:message events that replay previous chat messages for which events have already been received.  This bug seems to have been reported numerous times, and never completely squashed. The above testcase seems pretty straightforward, so maybe this time we can properly deal with it!
1456249552

Edited 1456249564
Phil B.
Forum Champion
Sheet Author
Hey Lucian, I'm sorry this is causing you problems. I was easily able to recreate the issue, and have created a bug report for it. It should get fixed in a future update.