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 here.
×
×
Cookie Preferences
We use Cookies to help personalize and improve Roll20. For more information on our use of non-essential Cookies, visit our Privacy Policy here.
Should I create a separate game for each adventure or just strat piling everything into one instance or what? What do you guys do? Segment your games into each section of adventure or put everythinbg in one?
New game for each adventure for me... it's worth spending some time on a 'default' instance with your most common macros, handouts, journal entries etc loaded into it. Then you can make a copy of that game for each adventure you want to run. However, if you plan on having a perpetual world with multiple adventures it is likely less tiresome (but potentially more troublesome) to house it all in a single game to keep things consistent.
I keep one game for the campaign, but have a second campaign - a Library Campaign - used to store maps, handouts, creatures, etc., that aren't currently in use. As a pro user, you can use the transmogrifier to easily move things in and out of your campaigns. So its a good idea to move out things you arent actively using, and keep your main campaign lean and fast.
I follow the same guidelines that Gigs does. One campaign world game and a backup for archives. I also have a game for API testing so that I do not run the risk of trashing my main game and one for map making.
Yeah, I have multiple games for testing things in. I should have mentioned those two - but they often get deleted, when I'm finished testing. I often copy the main game then do some testing, then delete it.
Some good points, I also have an 'atlas' game for maps, a 'bestiary' for sheets (not needed so much for compendium enabled systems but my long running 3.5e game used this extensively to alleviate load on the main game) and numerous testing games for API scripts, different sheets/systems and the like. I also tend to have at least one game for macro testing so that I don't have to clutter/clear the chat in active games as often to prevent spoilers ;)
There is a great temptation to build your magnum opus as almost life sized. I fell for it myself. The problem is hundreds of maps, NPCs, Monsters...Add a player with sh** internet, or one who is a bit slow themselves and it grinds to a halt. I am currently building a new campaign, I will set up a builder game, a libraryvand a seperate game for each plot line as they progress.