David F said: Is this still a known error? I thought I saw in an earlier post that an update was sent to Roll20 that was going to go live this past Tuesday that would fix this? Is my only option to try and do a manual copy/paste install? An update was submitted by me that could have potentially fix the issue in the one-click, but it clearly didn't. At least the API's description page now includes info on the ongoing issue, as well as a link directly to Vicberg's latest version of the script to be used, as well as to this thread: I pinged the Roll20 repo manager on the issue here . Guess I could make a mini-update and explicitly state to use the direct script if it doesn't, and that it's a know issue, in case there won't be a real fix next week. EDIT: comment from Roll20: Reonin: Yeah, I noticed when the changes hit live this week these cases didn't get resolved.
I believe we will be doing a deeper dive on what's breaking these one
clicks but I don't have a firm timeline on when that will be just yet.