Searching through this forum is a graveyard of failed suggestions along this vein, but I'd like to make a more in-depth case for this feature. Please hear me out. Background I've been using roll20 for a long time, and I finally decided to get a pro subscription to get access to lighting and scripts. There are a bunch of amazing scripts that I want to use, and they are all very well integrated into the two D&D 5E character sheets via the API. However, as time has gone on, more and more of my players have been buying content on D&D Beyond. This makes sense; DDB is platform-specific and allows players to share their content with the rest of us. Obviously this creates the problem of data fragmentation: Now my players' data is all on another server that the API doesn't have access to. All those scripts I've collected and this community has spent so much time building are now pretty much useless. From my perspective as a D&D player and DM, that tanks the value proposition of a subscription. From Roll20's perspective, the prior sentence should be cause for concern. Workarounds Don't Cut It Many are familiar with the Beyond20 browser extension, which allows players to use DDB character sheet data to generate rolls in Roll20. Beyond20 is great! It does not, however, integrate with Roll20 at all. No access to the character in API, (generally) no character sheet for things like GMSheet to latch on to. If your DM wants to do anything fancy, they have to essentially tell their players that they have to duplicate their sheet between two sites with two different source pools. This adds a lot of work and frustration, the things Roll20 scripts are designed to mitigate. The Importer Script (github repo here) The other available integration method is a community script designed to take the character JSON data from DDB and generate a character sheet based on that data. This is a great solution, and when it works it works more or less perfectly. The problem is that the script is (obviously) a volunteer effort and maintenance and bug squashing are left to the devices of those with the knowledge of Roll20 and DDB and scripting, and who have the free time to volunteer their efforts for the benefit of the community. The problem with that approach is obvious. At the moment, the script does not work consistently and currently has no maintainers or contributors to fix whatever issues have arisen over the past 16 months. The framework is there, most of the work is done, but I can't rely on it because sometimes things break and since the behavior is inconsistent I can't work around the problem. Make The Script Official I understand this is asking to put more on the developers' plate. On the other hand, isn't that what this forum is for? There are also few suggestions that would benefit both users and developers like this would: Most of the work on the script is already done. DDB already provides character data in an easily digestible format. Keeping interoperability as a script wouldn't compromise the core program in case DDB shuts data export down. It's an easy way to greatly enhance the D&D experience in Roll20 while keeping the site platform-agnostic. It would be a great help for players who have invested in the official D&D database service but want to support and use Roll20 to actually play the game. It would (in my opinion and experience) be a huge selling point for Roll20 subscriptions. I love Roll20 and DDB and think they both do different things extremely well. It would be great to be able to use both tools to their full potential, and I think that official maintenance of the import script would be an elegant and useful tool to get us there.
