And the sharing isn't even the real problem, is that the current compendium creation tools are not easy to use. If they where, there would exist a lot of more compendiums for sale, and Custom Compendiums for users would be much closer. Read Kenton's comment from the previous page(emphasis mine): Kenton said: I'm glad to hear that Compendium Selection resolved the issue for some of you. Some of you asked about the difficulty of implementing a feature like this. From a very high level, let me dig into that question. First, there two significant kinds of entering data into the compendium: Large Volume and One-At-A-Time. Since this thread was created, actually prior to supporting the Dungeons & Dragons 5e SRD, the purpose has not been limited to one or the other. The improvements to the Compendium software has been necessary to support the addition of 15 games systems , and more than 50 compendium books spread across those systems. Many of those have been in the last six months. The work has been supporting the Large Volume need. That's created very specific tools that Publishers can use to convert an entire book's worth of data, and add their game system. This requires significant planning and collaboration on how their games have been developed on and for Roll20. From a the other perspective, individual users are more likely going to add entries closer to the One-At-A-Time side of the spectrum. The big difference is the distance between doing all the planning for data/database/character sheet and being able to see, understand, edit, and use individual pieces. That work is detailed and nuanced - each game system is different and will have very specific needs based on the Character Sheet it uses. The One-At-A-Time side also is not likely to have or be able to produce changes to the display layer (like the character sheet, handout, or compendium entry). That "last mile" is making adding and editing compendium entries simple, intuitive, and easy to use. That's the phase we need to move into next. I hope that gives some insight into the problems we're trying to solve. We don't want to release something that's overly complicated or doesn't actually solve your problems. In an very summarized explanation, I expect that the first iteration if this request will be a way to save and retrieve a Handout or Character to a database shared by all your games. That gives you about 10% of the total feature power in the Compendium right now, but it solves the more common themes in this request.
