Reply to thread

Message: <blockquote data-quote="GX.Sigma" data-source="post: 6509049" data-attributes="member: 6690511">What I really want in published adventures (especially site-based ones) is the following format:Page 1: What this product is, and how to use it. This should start with a logline: a one-sentence explanation of what the product is. (Example: "Ravenloft is a horror-themed dungeon crawl in which the adventurers are constantly stalked by an intelligent and proactive vampire mage with mysterious motives.")Page 2: The short version. Yes, literally the entire adventure on one page if you can (multiple <a href="http://4.bp.blogspot.com/-bXAmO8wlfvw/Tbb7BM3roGI/AAAAAAAAAnM/I3H_SeY3o68/s1600/vornheim_0002.jpg" target="_blank">Vornheim spreads</a> or whatever if you literally can't). Trim all unnecessary details. Just give me the map and enough description that I can tell what's where at a glance. If I feel like reading the module (which I don't), I can read the long version and bring just this to the table for reference. More likely, I can just use this and wing the details with zero prep.Pages 3+: The long version. (Don't expect me to read this--if a detail is important, put it in the short version.)In terms of adventure design, a site needs one of two things: a reason to come back multiple times, or a reason to clear it in one shot and never look back. Anything in between doesn't really work, in my experience.</blockquote>