+1 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 leve, 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. Honestly, I would be happy with access to this. I'm perfectly happy building out a "private compendium" book and uploading it, then adding it to the game via Compendium Selection. I'd happily put together a .csv or whatever format is needed with the required information. My recommendation would be to set up: 1. Give DMs of appropriate subscription level the ability to have "Private Compendium" entries that function exactly like the books purchased form the Roll20 marketplace in terms of importing them into a game. These Private Compendium objects are monolithic objects: all or nothing imports into a game. 2. Give DMs the ability to upload a state file of some sort in a standard format to overwrite the Private Compendium" for a game. This could be as simple as a preformatted .csv, xml, or json file with url links to any images and all text necessary for the compendium entries. Should be able to support all current compendium entry types for the current system. Should also be able to support tokens for monster entries. 3. Design a workflow for updating a Compendium (either private or public) and how to update game content with the updated compendium, probably using a versioning system - I'm sure the publishers would like to be able to submit errata through this mechanism as well. 4. As a "stretch goal", once such a system is polished and in place, it could also be opened to allow homebrew creators to publish their compendiums to the marketplace - probably using a dependency system such that if I for example use an Eladrin from "Mordenkainen's Tome of Foes" to make an Eladrin Bandit creature, then that creature can't be used unless the purchaser also owns "Mordenkainen's Tome of Foes". I'd happily sit down and create a marketplace compendium for ennamed 5E humanoid NPCs of various race and class levels to allow DM's to quickly whip up chance encounters with something more interesting than "Human Bandit L 3." Obviously, that step 4 would be a massive undertaking (but would also constitute an additional revenue source), but items 1-3 don't seem like they'd be too large of a project considering the level of demand for such a feature.