kenton h. said: We're very interested in Custom Compendiums. However, there are several issues preventing us from implementing them right away. The largest blocker is how difficult it is to add data to the compendium. There is a secondary issue of preventing this from becoming a piracy-focused tool. We're currently improving data entry to make this process less difficult in coordination with 3rd party developers who would like their systems here in Roll20. Once we've streamlined that process, we'll solve certain data storage and sharing issues before development can begin. An initial plan for Personal Compendiums would include: User will have many Systems (to keep one game system from interfering with unrelated rule sets) Systems would have Categories (Bestiary, Class, Weapon, Spells, etc) Categories would have Entries This is criticism based on what you requested under "examples of quality moderator replies". I bear no ill-intention towards this and this is purely aimed at further improving the quality of user to developer relationships. The above post does not address the main problems that this thread is facing. First, your answer does not debunk, deny, counter or clarify what has already been said in this thread. The threat of piracy has been brought up before, but we have not received any valid methods or reasoning as to why it is an obstacle when compared to the current systems of uploading images and text to your own game. Second, power users already know you have a method of inputting data and creating custom compendiums. At least I know from what I saw with BurnBryte, which is a home made compendium given access permissions or copy and pasted to each available user. This tells us the following: You have a UI to create compendiums You have the methods of inputting data through said UI (otherwise the staff responsible for populating it would need specialized knowledge) You have methods of giving permissions and/or moving compendiums as desired. I do not know which format you use for compendiums, but I would have to assume either XML or JSON, based on what comes up in the search and how your filtering works in the in-site browser. Though I am not a whole lot of a specialist in this field, this brings us to the next problem. You can't fool those that know. Many power users will be able to understand from your responses that you have other motivations as to why custom compendiums are not happening, despite the technological foundations already existing. Perhaps your sales of official sourcebooks will dwindle, perhaps you wish to monetize utility. Regardless of what they are, my personal recommendation would be to come out clean and instead ask us, the users, as to what a better way to carry your motivations are. I understand this is a hard thing to do, but this is the minimum required to recover lost faith in the suggestion forums.