Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account
This post has been closed. You can still view previous posts, but you can't post any new replies.

Export and Import modules/campaigns

I understand that a lot of analysis and compromise has to be done before marketplace or even managed sharing can be implemented, but a simple export and import facility would provide an intuitive and simple way for GMs to manually and explicitly share their own creations with others. There is no danger of accidentally or mischievously sharing copyrighted campaigns/modules since the only way for Mary to touch Joe's campaign is if Joe manually exports it. And since the export file format isn't even defined yet, at the beginning there will be no copyrighted export files in existence. If somebody wanted to copyright an export, or apply a copyright to a backwards-engineered port from another game or system, then protection of the files they create will be their own responsibility (until such time as Roll20 works up a sharing portal, marketplace, or whatever). Without any idea of when current modules will be shareable with other GMs, and whether campaigns I create now will be compatible at that time, I am wary of investing the time to really optimize a module.
It's a real problem. On one hand you have potential/future content providers, the people who will (if things turn out that way) produce the modules, maps, art assets, stated tokens, specialized decks and so forth the Roll20 users will, I expect, come to depend on, and that Roll20 will, I expect, therefore come to depend on. The sooner they know what they can make to share, how they will share it, and on what terms, the sooner they can get started, which is better for their future customers and thus better for Roll20. On the other hand, the Roll20 developers probably aren't in a position to make a reliable announcement about what will be shareable, on what terms, and how until they finish beta testing and become quite sure what kinds of stuff there is going to be and in broad terms how it is going to be implemented, stored, etc. We have to remember that although most of us are using Roll20 for our own fun already and not in a critical, envelope-pushing way, for the moment the product has not been released and our freedom to use it is for testing purposes and as a quid pro quo for work as testers. I expect that one of the important revenue streams that will cover the continuing costs of Roll20's servers, Internet connection, and legal bills is going to be a commission on sales in the market for Roll20 modules and other assets. The developers probably haven't decided on that yet, perhaps aren't yet in a position to make the decision with well-founded confidence. But they have to keep that option open. And unfortunately a free sharing facility would undermine it. With free sharing an unscrupulous content provider could sell his or her content directly to users, thus bypassing the market-place and cutting Roll20 out of its commission, and thus threatening the revenues that we count on to make the basic facility "free". There is also a significant issue to do with secondary copying. The technically obvious way to support copying, and the one that is in the most straightforward way consistent with raising revenue by charging for storage allowances, would be to make a duplicate of the shared files and records. The obvious problem with that is that once I have a copy of your module there will be nothing to stop me from freely sharing it with someone else, including your potential other customers or people you don't want to show it to. Also, there would be nothing to stop me from making additions and alterations that offended your artisti sensibilities and damaged your reputation as a content provider, and then freely sharing that. So I endorse your call for a road-map to future sharing and the future market-place for modules and other assets to be issued as soon as may become convenient. But I am afraid that a free sharing feature would threaten the rights of content providers (the right to control or prevent copying of their work, the right to integrity of their work, and the right to be known as the author of their work) and also threaten the revenues that will make Roll20 financially sustainable. Given the competing claims on developers' time I am afraid that I don't see a free copying capability as likely during the beta test.
There is no danger of accidentally or mischievously sharing copyrighted campaigns/modules since the only way for Mary to touch Joe's campaign is if Joe manually exports it. Well, if Joe manually exports it to me, and I accidentally or mischievously export it to Mary, Mary can touch it without Joe meaning her specifically to have it.
I didn't explain my point adequately. If my suggestion is followed, then a campaign author/owner has the power to eliminate all danger of having others accidentally or mischievously sharing his campaign/module, by just not giving it to anybody else. People who want to share their stuff freely, or who want to rely on compliance of their end-user license (like Paizo does with their PDF products) may do so. Joe may choose to keep his campaign safely to just himself; or he may give it away freely; or he may depend on a license agreement. I was not proposing the ultimate sharing facility, just one that preserves the current level of security but allows people who want to share freely to do so, and which could be compatible with use-locked sharing implemented in the future. Back to the example, if Joe chose to hold his campaign close and never downloaded it, then Mary could never get it. If Joe downloaded and shared it with somebody, then he assumed the risk that some 1st-level recipient's copy could somehow make it to Mary.