RPGeezer said: Not sure how you got blame placed out of that response… Incomplete testing of new features has been an irritating hallmark of Roll20 for as long as I've used it (2020). I gave up on my pro membership after 2022 and would have given up on Roll20 altogether except a friend was running a campaign that continues to this day (though it's been dormant for a year, we're trying to kickstart it into gear again). I'm sorry that this makes me so angry, but most of my civilian work life I dealt with software companies telling their clients disastrous results of updates were because of the clients' "niche" uses. I spent 30 years involved with computerized maintenance management systems or CMMS for a nuclear research site and later a university and hospital. One very large US company I dealt with was forever breaking their system with new releases. Some of the inopportune times that came to interfere with us was tracking the work we did to house passengers stranded by the US airspace shut down on 11 Sep 2001. It made it harder to do what should have been routine dispatching work and keeping track of expenses in order to open up a recently moth balled student centre to give those poor folks a place to stay, setting up internet and phone services and free computers for them to use and stay in touch with loved ones. Another time a broken coordination system made responding to the electrocution and death of a contractor. The software didn't cause 9/11 or the poor electrician's death and neither did the developers, of course. But they sure made responding to it difficult. Eventually, they set up a software QA program and the frequency of update disasters dropped steeply, thank goodness. But before they did, this company's tech folks would say exactly the same : Issues are found with "a handful of users". Meanwhile, a whole listserv of mostly US universities, schools, research establishments (and at one point the Canadian Coast Guard who gave up on the company before the latter's Software QA program improved things) would be seething. It was not "a handful". As far as I'm concerned, Roll20 saying the same and attributing it to "niche bugs" which is code for "they are not using it for what it's designed for" aka "it's their fault, not ours". Sorry for the rant, feel free to block me. -- Tim
