r/TheRPGAdventureForge • • Feb 16 '22

System Specific: Best practices for [x] RPG Adventure Design Principles in the OSR

103 Upvotes

The OSR is an RPG subculture that prioritizes exploration, player freedom, immersion, and challenge (by challenge I don't mean rules mastery, or even combat, but rather overcoming difficult in-world obstacles in creative ways). What's interesting about it in the context of this sub is that the OSR blogosphere has spent a solid decade collaborating intensely on developing the principles and procedures necessary to build adventures with these priorities.

Rather than try to summarize it all, I'll be linking a bunch of "essential posts" that explain things better than I could. One thing you may notice though is that in the OSR, designing an adventure is really about designing a place, rather than events or scenes. It's all about building the kind of environments that A.) Are rewarding to explore B.) Present or generate interesting and unexpected challenges and C.) Prompt the players to treat the fictional world like it's real.

Jaquaying The Dungeon

it’s not just random chance that’s resulting in different groups having different experiences: Each group is actively making the dungeon their own. They can retreat, circle around, rush ahead, go back over old ground, poke around, sneak through, interrogate the locals for secret routes… The possibilities are endless because the environment isn’t forcing them along a pre-designed path. And throughout it all, the players are experiencing the thrill of truly exploring the dungeon complex.

Building Houses for Murderhoboes

Make it personal. The plot cannot be about saving the world, because murderhoboes don't want to save the world. It needs to be about the PCs. The heavy handed way to do this is to make it about saving themselves, because murderhoboes always want to save themselves. This is an option, just remember that you don't have to make it deadly, you just have to make it personal.

Analog, Digital, Procedural

You see, in Old School play ... fluff is crunch. The sandy floor, moist walls made of soft stone, composition of the gate, and disposition of the kobolds all can feed into the players' improvised plans and the DM's improvised rulings.

Dungeon Checklist

Read it once before you write you dungeon. Then read it again when you're done, to make sure you got everything.

OSR Style Challenges: "Rulings Not Rules" is Insufficient

Writing a good OSR-style problem is tougher than it sounds. It needs to be something that has no easy solution, has many difficult solutions, requires no special tools (e.g. unique spells, plot devices), can be solved with common sense (as opposed to system knowledge or setting lore), isn't solvable through some ability someone has on their character sheet.

Interesting and Useful Dungeon Descriptions

For players to want to risk their lives collecting information, they have to believe it's going to pay off. This means they need to believe that they are surrounded by useful information.

What is Tested?

When designing a dungeon, one question you should ask yourself is: What am I testing for? Math tests challenge your math skills. Drinking contests challenge your liver and your brain. But what does your dungeon test? How is the wheat separated from the chaff?

Elementary Principles of Dungeon Drawing

From the perspective of PC movement, just about anything you can place in a dungeon that isn't treasure will be one of three things: a speed-bump, a barrier, or a deflector.

Dungeon layout, map flow and old school game design

Fundamentally, a good map should enhance the factors which make dungeon crawling enthralling: for instance, exploration, player decision making, uncovering hidden areas and secrets, as well as maintaining the pace of action.

Bryce Lynch's Primer on Adventure Design

Choices: There should be more than one course of action available to players in order for the adventure to continue. Avoid choke points—both literal choke points in the physical layouts of dungeons and other locations, and figurative choke points which require a unique decision or solution in order for the adventure to proceed.

Old School Space vs New School Time

What keeps striking me about the better-written Pathfinder adventures is how easy it would be to blow them open. Arrange them across space instead of time: turn scenes 1-10 into locations 1-10, and let the PCs wander between them at will.

Encouraging Scheming

If your wizard spell list is "Fireball, Magic Missile, Lightning Bolt, Sleep" then you could have an okay heist, but it's probably going to be more of a head-on assault. If it's "Charm Person, Floating Disc, Summon Toads, Change Weather" then you're going to have to get clever, but the result will be more fun.


r/TheRPGAdventureForge • • Feb 19 '22

System Specific: Best practices for [x] RPG Jaquaying the Plot [Trad/OC]

38 Upvotes

TL;DR The following essay aims to analyze event-based flowcharts of trad/OC adventures in lieu of some of the best OSR dungeon design techniques.

Introduction

Trad and OC, as discussed by Retired Adventurer [0], are two of the most commonly widespread RPG cultures of play nowadays. While they disagree on who should be the primary creative agent while playing (the first culture has a strong GM-led play, while the latter tries to decentralize the creative stranglehold of the GM), both agree that the primary goal of a game is to tell an emotionally satisfying narrative.

Both cultures strongly value "the plot". Neither of those inherently value location-based adventure and dungeons are usually out of favor (even in games that have them).

On the other hand, the OSR culture values location-based adventures over all else, and part of the value of this movement was taking what was good about classic games and streamlining it, by discussing and sharpening their design techniques to better make adventures/dungeons that did suit their intents.

What I'm discussing here is trying to bring OSR techniques and good habits to trad and OC adventures.

New-school Flowcharts

In recent D&D editions, as well as in many Pathfinder adventures, the adventures are presented either as an explicit or implicit progression of events. As discussed by Joseph Manola [1], while old-school gaming is about exploring space, new-school adventures are about events evolving over a span of time.

Many adventures are either plotted out or presented as time/plot flowcharts:

  1. This is from D&D 5e's Rime of Frostmaiden.

  2. This is from D&D 5E's Storm's Kings Thunder.

  3. This is from Night Black Agent's The Red Connection

  4. Mouseguard's one-shot [2]

Why did they do so? Because event-based adventures are inherently something that looks more plot-based, therefore is immediately more appealing to trad and OC players. (Notice that it's implied and understood that scenes or events aren't pre-written by the GM, but they're just setting the situation and how things will unfold in actuality will be determined by what happens during your game sessions!)

Instead of going towards the direction of re-fitting an event-based adventure into a location-based adventure (thus losing the appeal for a vast majority of players and GMs, me included), I think it may be better to take a better look at OSR techniques that were used to hone the quality of location-based adventures and bring them into the event-based adventures.

Melan Diagrams for Flowcharts

First, as discussed by Melan [3], the linearity of dungeons can be shown more clearly by converting maps into diagrams. I don't want to dwell too much into the technicalities [4], but dungeons could've been reduced to any combination of the following four basic shapes. As far as dungeon quality goes, the more linear it is (like Sunless Citadel), the worse it is, while the more loopy/branched it is (like In Search for the Unknown), the better it is.

Second, Scott "Angry" Rehm [5] has discussed, as usual very at length, that every adventure structure could be thought of as if it was a dungeon adventure. He explicitly called converting this dungeon into this mystery adventure "tentacle magic".

GREAT!

Putting two and two together, flowcharts alone could be used to judge the linearity of an adventure, in the same way, it's possible to do the same with Melan Diagrams for dungeon maps.

Now, let's look back at the four basic shapes. Why do you think historically event-based adventures have always suffered from being more often than not pretty much always very railroad-y? Event-based adventures, by the nature of a time-evolving underlying structure, usually can't go back in time to previous events. Therefore, they can't have loops, as dungeons could have instead, and are stuck to Linear Adventures (or "Pure Railroads"), Linear Adventures with sidetracks (or "Pure Railroads with Sidequests"), or Branched Adventures.

What does Xandering even mean?

I believe that also flowcharts should always be heavily xandered.

…

I’m not making words up now, but Justin Alexander [6] did.

In the context of dungeon design, "xandering" means making the dungeon map layout more complex (if analyzed with a Melan Diagram), in order for the dungeon to be explored in very different ways by different players. In other words, this means "making a dungeon less railroad-like". The point is not necessarily to create a complex plot with multiple interacting pieces, but rather to make an environment that's complex enough to obfuscate the "path" and make it be an evolving story that follows the player and GM choices.

If we look like at xandering techniques for new-school flowchart adventures, there are multiple tips and tricks that could be used:

  1. MULTIPLE PATHS: Events should be tied to each other by appropriate hooks and each event should provide three (3) pieces of information about other events (others secret from the get-go) for the PCs to find out. The path they'll end up following won't be unique or direct.

  2. OPEN-ENDEDNESS: In Night Black Agent's The Red Connection, the players need to rescue an ally held captive by a vampire, being flown from one location to the next. The events provided are multiple: either a strike in the airport before the take-off, a strike on the plane while flying, or an attack on the second location after the landing. The same open-ended event, if played by different groups, will provide a very different experience.

  3. MULTIPLE PHASES: Exactly as dungeons have many layers, time progresses in an adventure from one phase to the next. Players may have the chance of joining a handful of events before time naturally progresses to the next phase.

  4. MULTIPLE EVENTS: Within a time phase, multiple simultaneous events take place. The players won't have the time to handle all the events presented, but the phase will eventually go forward once the players had the chance to tackle some of those events, while the rest will resolve and have consequences going forward.

  5. FRONT-BASED PROGRESSION: The importance of planning out the events meant to happen if the PCs weren't there has been discussed in the trad/OC sphere ("The DM Lair" Luke [7] and Michael "Sly Flourish" Shea [8]), and Fronts have been used in multiple adventures already, such as Motherships' A Pound of Flesh. Fronts have the advantage to be easily tied down with phase-based scenarios with phase alterations.

  6. PHASE ALTERATIONS: In order to make scenes where previous choices do matter (and the importance of choices have been discussed by Teos "Alphastream" Abadia [9]), it's possible to use phase alterations, like it was done in Mothership's A Pound of Flesh. Phase alterations let us make branching paths within the same scene, with different meaningful alterations.

  7. NESTED ADVENTURES: In D&D 5E's Curse of Strahd, once the characters reach Vallaki, a new scenario opens up, with a bigger cast of interacting characters with factions, objectives, and schemes. To all intents and purposes, it could've been written as a nested adventure once the character hit Vallaki.

Other techniques certainly exist, but xandered plots should become the norm to avoid the feeling of railroad-ness that usually trad/OC adventures based around event-based flowchart offer.

Bibliography

In this post I am going to present the taxonomy of the six main play cultures as well as a few notes about their historical origins. I am doing this to help people from different play cultures both understand their own values better as well as to encourage stronger and more productive cross-cultural discussion.

What keeps striking me about the better-written Pathfinder adventures is how easy it would be to blow them open. Arrange them across space instead of time: turn scenes 1-10 into locations 1-10, and let the PCs wander between them at will.

To compare the WotC introductory modules with various other introductory products from the 70s and 80s, I used a graphical method which „distils” a dungeon into a kind of decision tree or flowchart by stripping away „noise”.

The truth of the matter is that every adventure is a dungeon adventure. An adventure’s structure just shows how the scenes and encounters are interconnected. But you can map ANY adventure as a dungeon. Especially once you recognize that the hallways between rooms in the dungeon are not really hallways at all. They are just transitions.

They can retreat, circle around, rush ahead, go back over old ground, poke around, sneak through, interrogate the locals for secret routes… The possibilities are endless because the environment isn’t forcing them along a pre-designed path.

Dungeon World fronts are a great way to move your mind away from designing plots and instead driving the story forward through the actions of the most influential aspects of the world. Fronts are the oncoming storms soon to smash into our PCs.

To be meaningful, a choice has to engage players. The players and their characters must have useful information, and they must understand that their decision matters. The adventure then has to back that up with consequences for the choice they make.

You prepare a bunch of scenes that are likely and a timeline that'll keep the situation dynamic if the players can't do it themselves, and then you expect some of those scenes to go unused or unseen and some of that timeline to get derailed. All of that is work worth putting in to make a robust adventure, and even the stuff that goes "unused" was still helpful to you in gaining a more thorough understanding of the scenario.


r/TheRPGAdventureForge • • Feb 16 '22

Theory Six Cultures of Play

37 Upvotes

This article by The Retired Adventurer was really helpful to me in terms of clarifying the main RPG cultures out there and how they approach playing the game. It's useful to think about when designing adventures for one or another.

To briefly summarize, the 6 cultures he identifies are:

1.) Classic:

Classic play is oriented around the linked progressive development of challenges and PC power, with the rules existing to help keep those in rough proportion to one another and adjudicate the interactions of the two "fairly". The focus on challenge-based play means lots of overland adventure and sprawling labyrinths and it recycles the same notation to describe towns, which are also treated as sites of challenge. At some point, PCs become powerful enough to command domains, and this opens up the scope of challenges further, by allowing mass hordes to engage in wargame-style clashes.

2.) Trad (short for "traditional"):

Trad holds that the primary goal of a game is to tell an emotionally satisfying narrative, and the DM is the primary creative agent in making that happen - building the world, establishing all the details of the story, playing all the antagonists, and doing so mostly in line with their personal tastes and vision. The PCs can contribute, but their contributions are secondary in value and authority to the DM's. If you ever hear people complain about (or exalt!) games that feel like going through a fantasy novel, that's trad. Trad prizes gaming that produces experiences comparable to other media, like movies, novels, television, myths, etc., and its values often encourage adapting techniques from those media.

3.) Nordic Larp

Nordic Larp is built around the idea that the primary goal of a roleplaying game is immersion in an experience. Usually in a specific character's experiences, but sometimes in another kind of experience where player and character are not sharply distinguished - the experimental Jeep group often uses abstract games to affect the player directly. The more "bleed" you can create between a player and the role they occupy within the game, the better. Nordic Larps often feature quite long "sessions" (like weekend excursions) followed by long debriefs in which one processes the experiences one had as the character.

4.) Story Games

. . . the ideal play experience minimises ludonarrative dissonance. A good game has a strong consonance between the desires of the people playing it, the rules themselves, and the dynamics of the those things interacting. Together, these things allow the people to achieve their desires, whatever they may be. "Incoherence" is to be avoided as creating "zilch play" or "brain damage" as Ron Edwards once called it.

5.) The OSR ("Old School Renaissance / Revival")

The OSR draws on the challenge-based gameplay from the proto-culture of D&D and combines it with an interest in PC agency, particularly in the form of decision-making. The goal is a game where PC decision-making, especially diegetic decision-making, is the driver of play . . . The OSR mostly doesn't care about "fairness" in the context of "game balance" (Gygax did). The variation in player agency across a series of decisions is far more interesting to most OSR players than it is to classic players. The OSR specifically refuses the authoritative mediation of a pre-existing rules structure . . . by not being bound by the rules, you can play with a wider space of resources that contribute to framing differences in PC agency in potentially very precise and finely graded ways, and this allows you to throw a wider variety of challenges at players for them to overcome.

6.) OC / Neo-trad

OC basically agrees with trad that the goal of the game is to tell a story, but it deprioritises the authority of the DM as the creator of that story and elevates the players' roles as contributors and creators. The DM becomes a curator and facilitator who primarily works with material derived from other sources - publishers and players, in practice. OC culture has a different sense of what a "story" is, one that focuses on player aspirations and interests and their realisation as the best way to produce "fun" for the players.

It's worth reading the whole article, as he goes into a lot more detail about the different cultures.


r/TheRPGAdventureForge • • Jul 27 '22

Christopher Totten's "An Architectural Approach to Level Design"

35 Upvotes

My big revelation as a storyteller in the past year is that stories are landscapes: emotional, psychological, ethical. Your job is to take the reader on the most satisfying tour possible of that landscape by carefully designing a topology of character, plot, theme, etc. So with that new spatial mindset, I went looking for a book that could teach me something about how people who design spaces for a living think about their task. I found this book, which seems particularly useful for the readers of this reddit, since RPG adventures take place in actual levels, where the need for architectural thinking is much more literal. Here are some notes:

Philosophy

Miniature Gardens. Totten dives into a Shigeru Miyamoto quote I always loved, about how he thought of Zelda as a "miniature garden that they can put inside their drawer". When I first heard it, I assumed he was talking about the portability of the game cartridge itself. But Totten points out that the miniature garden is a familiar artform in Japan -- zen gardens, bonsai trees -- and he talks about how their design can help us get at possibility spaces, which I think is a major goal on this forum:

Possibility spaces “provide compelling problems within an overarching narrative, afford creative opportunities for dealing with these problems, and then respond to player choices with meaningful consequences.” The idea that games are spaces where players can address problems through creative solutions is useful for defining how we must think of game worlds as emergent spaces.

In the following, Totten is drawing on the thesis of Chaim Gingold, which is available here. (If there's interest, I'll share notes of that in the future, since I plan on reading it shortly.)

Two keys to a miniature garden:

  • Overviews

  • Clear boundaries

The first method of introducing possibility space in miniature gardens is through overviews. As stated by Gingold, “Miniature Gardens are scale models of bigger phenomena. Fish tanks and gardens are scale representations of systems bigger than people.”

One thing I've wondered about in TTRPGs is the insistence on having a fully stocked pantheon. And maybe this is one explanation -- a god's eye view of a world is handy for giving players an overview. Through a lore dump, you can take the player on a tour of the world's creation, giving them the "Previously on..." of this world that they'll be exploring.

Totten goes on to discuss "procedural literacy", which is the player's awareness of what can be done in the space. This seems like a major concern for DMs. Players are pretty literate when it comes to their own character -- you can assume they'll know their combat abilities particularly well -- but how to give them that same confidence in their immediate surroundings? With a fully realized battlemap on the table, players can latch onto minor details: "Hey, could I swing off that chandelier?" But in a theater of the mind scenario, I think it falls on the DM to put in enough description with an eye toward interactivity, and then maybe some bonus material that's there for flavor... until a player surprises you with it.

Clear boundaries is the next. If you look at the map of Hyrule in Link to the Past, it's quite clear when you've moved into a different zone of play. The tileset & color palette will always let you know where you're at, and the transitions between these regions are delightfully sudden. I'm sure that's mostly a function of memory constraints on SNES game cartridges, but Breath of the Wild doesn't fully abandon the dollhouse quality of its overworld. Super Mario World has a similar vibe. And of course this also ties into the previous tenet, of having overviews of the space. No better overview than an actual map.

The Challenges of Sandboxes

One might imagine that the design of sandbox worlds is simple: provide the player with a large open set of spaces in which to play, and give him or her things to do. However, large spaces carry with them the problems of user orientation and location awareness. As many real-world spatial designers know, these are problems regularly encountered by urban planners. It is perhaps not surprising that many of the most popular sandbox worlds are themselves cities. [...] Finding one’s way in a large open space can be daunting. For this reason, urban planners have developed a number of organization principles for how to structure urban spaces. In his influential book The Image of the City, urban planner Kevin Lynch reports the results of a five-year study of how people form mental maps of cities. From this study, Lynch advocates aiding visitors by organizing cities with these elements: landmarks, paths, nodes, districts, and boundaries. Organizing cities in this way creates what he calls legibility for observers of a city.

Running through those emphasized five:

Landmarks are pretty well-known, and Totten stresses how useful they are in luring the user around the space. The castle commanding a flat plain, the black eye of a cave staring out of cliff face, the statue rising from a pit -- lots of eye-catching landmarks that'll invite players closer.

Perhaps one of the most important elements of sandbox spaces comes from creative pioneer Walt Disney. While shooting live action films with dogs, his studio would often need them to run across the set. To accomplish this, they would use sausages, which Disney called weenies, to entice the animals to run in the direction they wanted. Disney described tall buildings in his parks as having a similar effect for patrons by assisting with directional orientation. Jesse Schell, author of The Art of Game Design: A Book of Lenses and one of the designers on Pirates of the Caribbean: Battle for Buccaneer Gold, used the term architectural weenie to describe landmarks used to attract players to goal points in their game. Architectural weenies are an integral part of sandbox spaces. They allow these worlds to retain their openness but still direct players to places that designers want them to go.

Paths. "Paths are the channels along which the observer customarily, occasionally, or potentially moves. They may be streets, walkways, transit lines, canal, railroads." (Lynch) This doesn't seem as relevant for tabletop -- the kind of wayfinding we're talking about is typically yadda-yadda'd, since not much happens when moving between areas of interest... it's why bandit ambushes are a staple, I suppose, to try and assert some reality and not have the players feel like they're simply teleporting about.

Nodes. "the strategic spots in a city into which an observer can enter... junctions, places of a break in transportation, a crossing or convergence of paths, moments of shift from one structure to another." AKA quest hubs!

Districts. "the medium-to-large sections of the city [...] which the observer mentally enters 'inside of', and which are recognizable as having some common, identifying character." Districts are the "modules" of urban planning. A friend of mine just visited NYC, and he told me how bizarre it was to pass through all these distinct neighborhoods that span just a few city blocks. One minute he's in Little Italy, the next in Koreatown. Though the density is unique to New York, we see it in every city across the world and in every story with many worlds. Mark Rosewater, who works on Magic: The Gathering, points out how in sci-fi movies like Star Wars, each planet is single-purpose. You've got the ocean planet, the lava planet, the ice planet. Of course in reality this wouldn't make any sense -- a planet that can support life is too large to have a single biome -- but for the viewer, they're experiencing them like districts. Giving them a distinct theme provides clarity & a sense of boundaries within the narrative, which orients them within the story.

Boundaries. "Linear elements not used or considered as paths by the observer... shores, railroad cuts, edges of development, walls". This seems applicable, but a locked door is a boundary that gamers love to interact with, and are a very important tool for restricting freedom of movement, which will help you pace out the action.

Pacing

I run into music analogies whenever I'm reading about story, and I think it's because they are both dynamic media. No story beat and no music beat stands alone -- melodies only emerge from their sequencing, and the dynamic variations between loud & quiet, or mellow & intense, is what the experience is all about. Turns out architects conceive of space dynamically, too: "As we show in later chapters, spatial contrast is very important for building meaningful experiences in both games and architecture. As such, we must learn how to control how we pace our levels in games."

Totten recommends a two-phase design: first, develop a "parti", which is a top-down plan of your space. Roughly portion out those areas you know you'll must have, but don't fill them in right away. Only once you've got the full scope mapped out do you dig in and start to space out your features:

When designing levels, we can utilize the same mindset by treating our level drawings as ones from Nintendo Power, creating the overall scope of a level on a macro-scale and evenly spreading out micro-scaled areas of more intense gameplay across the entire map. In between the “loud” gameplay moments should be circulation spaces⎯spaces for movement-based gameplay, movement-based obstacles, exploration, or even rest and recharging of the player character. [...] Each of these highlighted moments of gameplay— be they enemy encounters, movement puzzles, or helpful stopping points— has potential for its own genius loci (editor's note: see below for definition). Are these places for rest or for battle? Should the player feel relaxed, tense, or meditative in these gamespaces? The answers to these questions depend highly on the game you are building, but can help you determine the kind of feel you want for your levels.

Jargon

Genius loci. "This lesson is known as genius loci, also known as spirit of place. This term comes from a Roman belief that spirits would protect towns or other populated areas, acting as the town’s genius. This term was adopted by late-twentieth-century architects to describe the identifying qualities or emotional experience of a place. Some call designing to the concept of genius loci placemaking, that is, creating memorable or unique experiences in a designed space."

Refuge and Prospects. This was the jargon that's stuck with me the most.

We have defined prospect spaces as open spaces where one is vulnerable to attack, such as those encountered by early humans who had to explore wide plains to find food and other resources. A refuge, on the other hand, is the contrast to prospect spaces that early humans would return to after their hunt: an intimate-sized space that was shielded from view and from which humans could look out onto prospect spaces to evaluate threats. The ability to evaluate threats is important when discussing prospect and refuge spaces, as it is this relationship between refuges and prospects that allows us to create gamespaces with this concept.

While one would typically assume that refuges describe permanent living structures, this is not always the case. Borrowing from D.M. Woodcock,15 Hildebrand divides prospect and refuge further into primary prospects, primary refuges, secondary prospects, and secondary refuges. Primary pros- pects and refuges are those we are immediately engaged in: the refuge we currently occupy and the prospect we are looking out onto from our refuge.

Secondary refuges and prospects are those in the distance⎯the refuge on the other side of the primary prospect, and the prospect beyond that. From a level design standpoint, we are concerned with planning all of these spatial types. However, from a player perspective, we are concerned mainly with the relationships between refuges, prospects, and secondary refuges. These spaces can create exciting gameplay scenarios when used in proper sequence: running from cover point to cover point in a shooting game, moving from one hiding spot to another in a stealth game, and many others.

Arrivals. Scene-setting is common in every narrative medium, where you lay on the description as characters step into a new space. Totten has some practical advice about juicing that moment: "Much of how you experience a space when you arrive in it comes from the spatial conditions of the spaces that preceded it: if you are arriving in a big space, spaces leading up to it should be enclosed so the new space seems even bigger, light spaces should be preceded by dark, etc." I suppose a question for a DM is what are the ludonarrative equivalent of contrasts like light/dark, narrow/wide, short/tall? The most obvious is safe/dangerous -- players know when they're in town, random encounters stop.

A fun example of an arrival, the "Jesus Christ" spot:

In their book Chambers for a Memory Palace, architects Donlyn Lyndon and Charles W. Moore highlight John Portman & Associates’ Hyatt Regency Atlanta hotel as featuring such arrival in its atrium space. Dubbed the “Jesus Christ spot” by critics, it was not uncommon soon after the hotel was built for businessmen to arrive in the twenty-two-story atrium from the much lower-ceilinged spaces preceding it and mutter “Jee-sus Christ!” as they looked upward. Similar spatial experiences are common in exploration-based games such as those in The Legend of Zelda or Metroid series for leading up to important enemy encounters, item acquisitions, or story events."

Allies. I don't know how widespread this particular piece of jargon is, but it fits so nicely with a tabletop experience. I've seen players really gravitate towards their favorite NPCs, and they go a long way towards creating a sense of place. "In Chambers for a Memory Palace, Lyndon and Moore describe the concept of allies: statues, short columns, and other architectural elements that are of similar scale to an occupant. Beyond iconographic significance, they point out that allies in a piece of architecture can make spaces more inviting. In games, non-player characters fulfill many of these functions and often have their own gameplay reason for being in a space, sending the player on quests, guarding doorways, etc."


r/TheRPGAdventureForge • • Feb 27 '22

System Specific: Best practices for [x] RPG No Plots, No Masters [Story]

34 Upvotes

TL;DR The following essay aims to discuss trends and similarities in the few and far between examples of adventures for story games that do exist, mainly PbtA, as well as the role of prep in story games.

Introduction

This second essay is meant to be a follow-up to my previous one [1], as a jumping-off point of discussion about specific good techniques to design adventures for the poorly-explored cultures of play.

There are many points of contention between Story/Indie and OSR cultures (as discussed by Retired Adventurer [2]), but they have as many commonalities once we go under the hood. The key thing that ties them together is "emergent storytelling", as discussed by Ben L. [3] and often advocated as "play to find out" in story game circles. In the context of story gamers, the inherent problem of GM-led plot-based storytelling is that players are seen as if they were present only as props, and this imposed narrative is seen as counterproductive to the ideal game they aspire to.

What they are after is improvisational, collaborative, storytelling experiences, where players and GMs can explore fiction together, creating interesting stories in a certain genre by throwing characters into provocative situations so as to see what happens.

The Myth of Prep-less

Knowing that a shared improvisational experience is considered to be one of the key tenets of play for story gamers, it's not a surprise that games did shift away from plot-based prep that was assumed to be intrinsic with the experience of TTRPGs (and very little took its place because plot-based prep is what most trad GMs were used to), and consequently adventure modules are a little-explored avenue of game design.

Notice that the "no-prep" misnomer has led to a swath of misconceptions about the story genre (like here [4]), wherein reality most of the times GMs or facilitators are asked to prep something by the rules of their games but, more often than not, using pre-planned material is still somewhat frowned upon. Even Jason Cordova [5], the author of Brindlewood Bay, uses a prep technique known as 7-3-1.

Now, if many story games ask for GMs to prep something, what are they asking for? As eloquently explained by Paul Beakley [6], prep for story games is a multifaceted beast:

  • Prepped versus un-prepped improv. The effect of constraints on creativity has been discussed at length [7], but the "Blank Page Effect" is the main reason why it's easier to make up a character for a playbook-based story game than it is for a generic open-ended game like Fate.

    • In this sense, some amount of prep acts as a constraint to reduce the blank page effect and as a prompt to help the GM (and even more inexperienced story GMs!) to lead and facilitate the improvisational experience of the whole group.

  • Not obstacles, but situations. Situations are unresolved points of tension or, in other terms, they are problems; once one resolves, it generates new situations that continuously generate new play. Now, it's fine for Story GMs to set up and pre-plan problems, as soon as they don't plan for outcomes, solutions, or story threads.

    • Clear examples of "situation prep" come from game-specific GM-facing mechanics, such as Apocalypse World's Threats, Dungeon World's Fronts, R-maps from multiple games...

  • Setting elements (like places and NPCs) are fine. Just don’t go any further than that. Leave plenty of blanks and be an earnest active participant in the game and be eager towards playing to find out what happens next.

    • Clear examples of pre-made setting elements come from embedded settings in some recent games, such as the whole Doskvol's setting from Blades in the Dark or Islands from Agon, both from John Harper.

Dungeon Starters and Loaded Questions

The discussion about "what adventures are" in this sub recently landed thanks to u/Barroombard into something that looks more or less like:

An Adventure is a collection of connected fictional elements that prompt action and are resolved by the intervention of the players.

And this will be my yardstick to evaluate adventures and this fits what dungeon starters are to a tee.

There are very few PbtA-like games that do have explicit adventures and I don't think it's a coincidence that Dungeon World, which is inspired by D&D (with a long history of adventure modules) it's one of those. Marshall Miller [8] did coin the term Dungeon Starter and did compare them with a form of prep made out of a loosely connected cloud of blanks and hooks to make sure the players don’t catch the GM with anything interesting to say. Sometimes they come with game-specific elements, such as monsters, fronts, or custom moves to tie the narrative to the mechanics of the game.

An expert on the subject of dungeon/adventure starters is Jeremy Strandberg [9] (or u/J_Strandberg), author of Homebrew World and co-author of Stonetop.

In Homebrew World, the setup for the one-shot is more structured than it is in regular Dungeon World. This means that, before character creation, the players work together to discuss and establish their Premise, in order for them to make informed choices about character creation.

Then, once players have created their characters it's with Hook questions that characters are tied to the one-shot. The art of asking leading questions during character creation [10][11], especially if they are loaded to assert things meant to be true in the adventure, is what bridges pre-made content and shared storytelling experiences. Key principles about hook questions are:

  1. Address the characters, not the players

  2. Assert at least as much as you ask

  3. Assert things that need to be true

  4. Ask for meaningful contribution

  5. Be specific, but not too specific

  6. Get personal

Magpie Games' Adventures and Playsets

More recently, Magpie Games dabbled with adventures in a couple of intriguing ways worth mentioning to discuss the state-of-the-art applications out there.

First, the Avatar Legends RPG was funded on kickstarter and among the rewards they planned for a cycle of entry-level adventure booklets, possibly because the game was aimed at a big player base not necessarily familiar to PbtA story games. In the quickstart of the game, it's included a fully functional adventure with an in media res hook (the PCs are stuck in jail at the Fire Capital for a botched heist, when a turncoat Fire Sage shows up offering them the scroll they were trying to steal), and then an adventure location with a loose map, a handful of factions & NPCs, and a timeline of likely escalations as the characters try to escape the city. Then it’s up to the players and the GM to find out what happens.

Second, in Unbound: A Mask Supplement there are official "playsets" for the game that majorly change the assumptions of the setting by making it be more focused. So in Iron Red Soldiers, for example, the PCs are the resistance to an alien occupation that has already captured the adult heroes. A juicy set-up, rife for exploration in play. But there’s no built-in “adventure” or “dungeon” or anything like that.

To put it into perspective, "starters" act like traditional adventures, while "playsets" act like traditional settings/campaigns. I don't doubt that the two could be integrated into each other to make a "full campaign" for existing popular story games.

Dos and Don'ts

This is such an untapped avenue of design that I think there is still a lot that could be said about the dos and don'ts of story's adventure design.

We discussed setting up situations, planning for NPCs, factions, and locations with pre-made blanks in it, discussing the premise before character creation, using leading questions before play, and using timeline escalations and game-specific custom-moves during play (which I think could be used to mechanize fictional/reproducible elements). This isn’t so different from "adventure location" style OSR modules, like the often-discussed A Pound of Flesh for Mothership, which also has a location, NPCs, and a series of escalating events that the players can interact with, as they so choose, even if I think the story games ones should pay closer attention to premises and question hooks, as well as leaning into the adventure's blanks.

On the other hand, as discussed at length [12], designing modules for story games can prove quite difficult or impossible, especially if considering difficulties, obstacles, node-based scenario design, event-based flowcharts... but I'd love to hear from you as well!

Bibliography

Both story and OSR gamers find this dreadful. They both reject it using the same form of words. When I first read Vincent and Meguey Baker in Apocalypse World saying, "We play to see what happens," I recognized immediately a formulation that everyone in the OSR would enthusiastically affirm.

What PbtA games really care about is that when you do your Prep, you are Preparing Problems, but never the Solutions, Plots, or Outcomes. That is the crux of the common GM Agenda of “Play to Find Out.” [...] So by all means: prep towns, locations, NPCs, problems, and more. Just don’t go any further than that. Leave plenty of blanks and be an earnest active participant in the game and be eager towards playing to find out what happens next.

7-3-1 is… an exercise. I’m hesitant to call it “session prep,” because the point isn’t necessarily to end up with a bunch of notes I can use during the game. Rather, the point of 7-3-1 is to help interrogate my setting so I understand it at an intuitive level.

But what if I told you that, rather than prepping to avoid having to improvise, you can prep specifically for improvisation?

Establish a premise for the adventure with your group before they make characters.  That means you should bring something with you, or a choice of somethings. You should show up with a premise in mind, or a way to come up with one, plus whatever additional prep you feel will be helpful (more on that later). 

There is a tangle of issues that I am personally grappling lately, re: PbtA. For example, there is a notion that writing modules for Powered by the Apocalypse games can be difficult. Is this true, and if so, why?


r/TheRPGAdventureForge • • Feb 16 '22

Layout How adventures are written.

34 Upvotes

So awhile ago on a forum I am on I responded to someone writing an adventure.

https://www.dakkadakka.com/dakkaforum/posts/list/795515.page (Im Lance845) You should see the adventure he put together for context.

My advice to him was as follows...

So for starters, I have not finished reading through it yet. That being said, my biggest issue with the adventure is that you followed DnDs terrible format for presenting adventures. Don't take any of this as being harsh criticisms of you. This is you doing what you have seen from the information wizards has given you. If I have harsh criticisms it's for wizards. That being said I am going to be blunt about why this format is bad and what you can do to improve it.

This is written in a way like you are selling me, the GM, a novel. Your opening Blurb above the credits which is also the first paragraph is like the back of a book to get me to bring the book to the counter and purchase it. As a DM running an adventure I don't need that in the adventure. At no point should any of the information be presented to me, the DM, the only one using this document, like I am uncovering a mystery as I read on. This isn't a story for me to enjoy this is a guide for me to build a story with my players. I need information I can use.

Before you get to ANY of the sections of the adventure I need an overview.

Overview

  1. What is this adventure about. Or here is a Legend that encapsulates the whole of the adventure.

"There exists a ghost ship that... "

2) What is actually going on.

Get rid of any of the legend in this part and tell me plainly what exactly is happening. I need to know. And I shouldn't need to flip back and forth through paragraph after paragraph of information in specific sections to get confirmation of this information from text written in story telling format.

3) Who are the named NPCs, their motivations, and their relations to other named NPCs.

This should be some kind of major players list with all the needed information about the NPCs right there. Preferably in either alphabetical order or the other in which you will run into them. By order in which you will run into them I mean it's actually impossible to encounter them out of order. If say... the adventure is a town... then alphabetical because who knows where the PCs are going to go and who they will talk to. In fact, do both. Sub section the NPCs into batches based on mandatory encounter order and alphabetical within the subsections. The point is to make it a page I can tab and move to quickly for all NPC related information without having to dig through text to get the information I need.

4) How the players can get there...

Now give me some adventure hooks. Don't just tell me the story of how the adventurers stumbled onto an anchor in the mountains. Give me 3 options of things the players COULD find out. Maybe they meet someone who encountered the anchor and heard noises and now he's telling the story in town prompting the PCs to explore the mountain. Maybe they hear a bard play a song about the ship that drops anchor all over the kingdom occasionally. Maybe the adventurers are in a mountain and they hear a crash while making camp.

You never tell the players what they are doing. You give them, and thus me the DM, hooks to present the players with and send them in a direction. Keep the in game flavor text italicized and brief. Opening little blurbs to each section. Keep them purely descriptive of the environment. Never explain actions by any of the PCs. For example: you describe what they find when they explore the rope and anchor. Don't. They might not investigate it in that way. But you DO need to tell me that the anchor and rope for all intents and purposes are real. These are physical objects and the anchor is implacable. Now IF my players decide to try and move the anchor I have the knowledge to respond to their actions. Not a few sentences I have to take out of a paragraph of a story that need to be re-contextualized to fit the moment when my players act.

Next: The adventure itself.

So we should now dig into this as acts in a play or chapters in a book.

Act 1: The Ghost Ship.

Begin with one of those italicized blurbs that are purely descriptive and set the scene.

Now list each component of the ship. Within each component of the ship list the events that can transpire there.

So you present this information like this.

This apparition is encountered when adventuring in the mountains. After a cold wind blows up, and the fog sets in, the players will start to notice the creaking of the hull, the flap of sails and thrum of the rigging. Shortly thereafter, they encounter a great outcrop of rock, thrusting up into the clouds where it disappears from sight. Beside it, they find a rope strung taught toward the sky, with an anchor embedded in the snow and ice. When investigated, the rope feels real enough, and the anchor heavy enough to defy being moved. This is no apparition - it's real!

[b]Boarding[/b]

When the players climb the rope, they find a great ship speared on the rocky outcrop - its timbers long since fallen to decay, the last vestiges of paint still clinging to the warped and split timber implying that this ship was once extravagant in the extreme. Icicles hang dripping from the keel (underside) of the ship. Players climbing the rope will arrive on the fore deck, at the front of the ship. The whole ship lists down to the port (left) side, the ribs of the ship jarred against the stone upon which it hangs on its starboard (right) side. The figurehead is a rearing horse, the deep grooves of its carved mane showing traces of pale green paint, its heavy wooden features softened by rot and crumbled by time. The name plaques on either side of the ship read "The Celestial Mare", and a History check DC (20), with advantage for adventurers over 300 years old, reveals that this ship was a notorious pirate ship, which vanished without a trace some 300 years ago. The decks are strewn with detritus and debris; long empty oil lamps, scattered ropes, fallen rigging. The foremast lies at an angle over the cargo hatch, and the central & mizzen masts point accusingly up at the skies from which it seems to have been dropped. One side of the rigging has fallen to the deck and can easily be lowered over the side to allow any less able climbers to board. But this is no skyship - how did a seafaring ship come to rest in such a place?

I would present this same information like this... (I give you blanket permission to use and or change any of this for your own use in any way that you see fit from now until the end of time and forfit any claim to ownership of the following text)

[b]ACT 1: THE GHOST SHIP

1] The Ship - The Celestial Mare[/b]

[i]The creaking of a ship at sea can be heard on the chill winds high in the mountain. A fog settles over the area as the sound of sails flapping and rigging thrums in the air. A rocky outcrop juts from the mountainside and disappears into the fog and clouds above. Beside it, a massive anchor embedded in the ice and snow with a rope pulled tight following the outcrop into the sky.[/i]

Here the players first encounter the ship "The Celestial Mare" It has been speared onto the rocky outcrop - it's timbers long since fallen to decay, the last vestiges of paint still clinging to the warped and split timber. It's anchor, embedded in the rock and ice bellow and covered in a dusting of snow is still attached to the deck by a thick strong rope. The anchor is implacable. The ship was clearly extravagant in it's day. Icicles hang dripping from the keel (underside) of the ship. This ship is tilted toward it's left (port) side. On it's right (starboard) the ship is penetrated by the outcrop and the splintered wood creaks and cracks as it grates against the stone. The figurehead is a rearing horse, the deep grooves of its carved mane showing traces of pale green paint, its heavy wooden features softened by rot and crumbled by time. The name plaques on either side of the ship bare it's name "The Celestial Mare". The decks are strewn with detritus and debris; long empty oil lamps, scattered ropes, fallen rigging. The foremast lies at an angle over the cargo hatch, and the central & mizzen masts point accusingly up at the skies from which it seems to have been dropped.

[b]Events[/b]

-=The Anchor=-

The Anchor is the first visible sign of the ship, it's rope disappears into the fog and sky with the rocky outcropping. If the players investigate it they will find it very real. This is a massive anchor at least the size of a man and embedded as it is is impossible to move. The rope attached to it is old but in good condition. It is strong and thick, made of rough cord and would be easy to climb if not for the ice and snow.

-=Boarding the Ship=-

Players can enter the ship in a few ways.

-The Rocky Outcrop-

Some players may choose to use the rocky outcrop to work their way into it's hull (Section [b]3] The Cargo Hold[/b]). Those who choose to take the outcrop will need to clear away some of the timbers to make a space big enough for them to fit. Describe the looming ship as it takes shape out of the fog. Describe the outcrops frozen condition. No roll should be needed to approach the ship but that doesn't mean you shouldn't set the stage as cold and dangerous with low visibility. A [b]Strength test (DC 15)[/b] can pull away some of the timber to clear the way. Give advantage if they use an axe or other good tool to help.

-Scaling the Rope-

Others may attempt to climb the rope to reach the Deck (Section [b]2] The Deck[/b]). Doing so requires a [b]Climb Check (DC 15)[/b]. If they fail make a show of the ice that has accumulated on the rope and tell them how close they were to falling off the cliff into the fog, but do not actually drop them. Let them try again at "risk" or retreat down the rope to take the easier rock outcropping. If a player successfully makes it to the Deck there is loose rigging near the side where they appear that can be lowered down for others to climb. Anyone scaling the rigging does not need to make a check.

-=The Ships Identity=-

Any player who either scales the rope/rigging or approaches the hull and say they look around the outside of the ship will see the name plate on the side of the ship (No roll needed). Prompt if they wish to make a [b]History Check (DC (20)[/b]). Give advantage for adventurers over 300 years old. Success reveals that this ship was a notorious pirate ship, which vanished without a trace some 300 years ago.

So on and so forth.

See the difference? What wizards does is write you a novela that you read. What they (and thus you) SHOULD be doing is giving a DM the tools they need to run the adventure.

A note on formatting. By keeping the ____Check (DC__) format for all skill checks in text and by bolding them you can make the information very easily readable for the DM. You might even want to color it differently. That way at a glance I can look at my page/notes when a player wants to climb and see a bold/blue Climb Check (DC15) stand out amongst the text and know exactly what to ask for. This could even go a step further and format it as [b][color=red]History Check (DC20) Adv: 300+ years old[/color][/b].


r/TheRPGAdventureForge • • Mar 06 '22

Structure R-Maps and the Social Sandbox

27 Upvotes

TL;DR The following essay aims to discuss relationship maps as a scenario design technique to outline non-exploratory sandboxes.

Introduction

This third essay is meant to explore a scenario design technique known as "Relationship Map or R-map" meant to outline and explore complicated inter-relations between fictional elements, usually characters, without outlining events.

The extreme basic idea is that relationship maps are organigrams that show graphically the relationship among fictional elements on a diagram. In this sense, Relationship Maps [1] are useful to visualize and explain complicated relationships and draw conclusions about implied situations.

While historically the first mention about Relationship Maps was in GURPS Goblins, the term was popularized by Ron Ewards in 2002 Sorcerer's Soul, as discussed at length [2] by him. Worth pointing out that Relationship Maps are not just another name for node-based scenarios, à la Justin Alexander, as discussed here [3]. The term has outgrown its initial definition, for better and for worse, and has been used in a bunch of different games (such as Smallville RPG, Vampire: The Masquerade 5E, Undying, Saga of the Icelanders, Technoir, Burning Wheel...) in a vast array of different ways.

What are R-Maps good at?

One Page Dungeon Contest is a yearly contest about one-page dungeons/adventures. Let's look at Kelvin Green's winner entry from 2012 where they did show a simplistic relationship map with charming little portraits of the characters on "A Rough Night at the Dog & Bastard" [4].

  • Visual Cues are -to me- one of the best ways to convey pieces of information easily, as soon as R-maps aren't cluttered with too much information. Keep it simple and easy, for it to be accessible by another human being. For example, just by glancing over A Rough Night at the Dog & Bastard's map, it's easy to see who are the three more connected characters (e.g. the ones more connected to the others, so Parlethotaxus, Septimus Drake and Lady Genevieve) or if two characters are supposed to already know each other.

  • Intrigue Sandboxes are mapped by R-maps and they could be updated as a living document if things happen during play. Relationship Maps are the foundation of a story, but don't dictate how things will evolve once actions begin. For example, if Lady Genevieve gets killed, it's very easy to cross her out and redefine connectors right after the death.

  • Triangle relationships [5] are implied relationships between two characters mediated by a third (such as PC-NPC-PC triangles from Apocalypse World). While they are usually pretty difficult to assess, R-maps make them very easy to adjudicate on the fly. For example, we know that Balotelli will try to kill Lady Genevieve and that Lady Genevieve had an affair with Baron Roosterlick, therefore it's likely that Baron Roosterlick will try to stop Balotelli if there aren't ill feelings among him and his former lover.

  • Proactive NPCs are easier to handle just because goals are often implied in relationship maps. For example, if PCs didn't thwart Balotelli's plans trying to assassinate Lady Genevieve, resulting in her death, it's likely that Parletothraxus would snap and get vengeance on whoever did ruin his saucy evening.

Three Key Questions

(1) Are PCs on the map or not?

This is the very first thing that needs to be assessed.

Historically, PCs were meant to not be on the R-Map, and their role was to enter this maze of relationships (usually to investigate a mystery and discover a hidden secret among them) and act as a catalyst to goad one or many of the other characters into further action.

Nowadays, more often than not, relationship maps are built outwards from a central core made by the player characters' relationships towards non-player characters, so that the maze of relationships is centered on PCs. The point is not entering and solving the maze of relationships but wandering in it, to create dramatic character-driven/goal-oriented stories, where NPCs proactively react to players' actions.

(2) Is the R-Map in the open or secret? Who made it?

This is another key difference for, as far as I'm concerned, story games with R-maps and trad games with R-maps.

Historically, R-Maps were made by GMs as part of their prep and were GM-facing tools, definitely not in the open. On trad play, it was sometimes possible for players to have access to a "public R-map", which somehow mimicked what they did learn on-play, built on the full GM's one.

In story game circles [5], R-maps are front and center and used at the table, shared by all players. More often than not, they're written collaboratively as part of character creation if the game revolves heavily around those.

(3) What are the Elements? What are the Connections?

This is more subtle and essentially reads as "What is this R-Map about*?*".

The more commonly agreed-upon symbols on R-maps (even if multiple variants could be seen from different blog writers, such as [6][7]) are derived from Smallville RPG's pathways chart:

  1. Rectangles are Player Characters

  2. Circles are NPCs, Extras or Groups

  3. Diamonds are Locations

  4. Situations are Triangles.

As far as mapping situations as well as places and people, Paul Berkley did explain poignantly [8] that adding situations to a Relationship map makes them be a "situation map", as in a snapshot of the current status quo and the most important elements at play.

By choosing appropriately what kind of elements include and what kind of connections include (or, even better, what kind of elements/connectors it's appropriate to leave out), it's possible to frame different situations with strongly curated R-maps. For example, by including only Noble Houses and Alliances it's possible to map a political landscape (like the faction relationship map from the adventure in the back of Cryptomancer) or by including only PCs it's possible to map an intra-group relationship map, and, from Sorcerer's Soul, the only kind of connectors allowed were family ties and sexual relationships, which were used to frame a very specific familial relationship map.

An Adventure Designer's Perspective

Looking back at the previous three questions, as far as using R-maps as adventure designers, PCs need to not be on the map (since modules should be PC-agnostic) and I'd say that adventure modules are better served when they are not meant to be public. From my perspective, R-Maps offer a very strong tool, to outline social situations (or "social sandboxes") for the PCs to explore, while providing a tool for GMs to understand what's going on and keep up more easily.

While it's true that R-Maps could be used to outline the scenario for social sandboxes, it's not enough to just lay out fictional elements and expect them to play themselves. In well-written sandboxes [9], two key elements that must be included are both "scenario hooks" (usually included as rumor tables) and a "default action" if players miss the hooks or don't find them interesting. In my experience, hex-crawlers and dungeon-crawlers always have a very simple default action (which is keeping exploring forward), but in social-crawlers [10] the default action must be thought in advance as part of the scenario and included to avoid the scenario falling into itself.

Bibliography

The CRM depicts, on a single page, all the relationships between all your story’s characters, or at least the major ones. Having this map before you as you write the story will help you keep these relationships in mind.

They are a diagram of two specific sorts of "connections" among NPCs, primarily - kinship and sexual contact. They can include other connections too ("friends," "boss," etc), but usually these are secondary and used only when the primary type of connection doesn't apply at all. [...] Relationship maps as I define them are not corridors and pathways of player-character "movement" during play. They are a way to remind the GM just what passions and issues are currently hanging fire among the NPCs.

The page is not a dungeon at all. It does not even have a map of a dungeon. It consists solely of an inn filled with people and their relationships to one another.

I’ve long been a proponent of at-the-table relationship maps, and of setting them up with everyone’s participation at that table. [...] It is a central and theatrical process, which draws everyone’s attention to the table during creation and play. This last one I cannot emphasize enough.

I wanted to be able to put that kind of nifty stuff into other games, so I ended up writing up this thing called “Entanglements.” It’s essentially a genericized version of Pathways, with a few new elements I thought would be neat, plus some suggestions for using it with specific games.

R-map + situations = situation map.

One technique for understanding your game’s situation I’ve talked about before is the situation map*. [...] Labeling situations that are currently in play among those relationships.*

A good sandbox has scenario hooks hanging all over the place. The successful sandbox will not only be festooned with scenario hooks, it will also feature some form of default action that can be used to deliver more hooks if the players find themselves bereft of interesting options.


r/TheRPGAdventureForge • • May 22 '23

I wrote a tutorial for the basics of adventure writing and publishing

26 Upvotes

The post is available over on my blog, with images and a couple of supporting files, but I'll copy over the text here as well, please forgive any weird wording because of the transfer. Thanks for looking!


WHAT IS THIS?

In this post I intend to go over my entire process for adventure writing. I’ll use my latest adventure, A Opossum’s Hat, as an example. To the best of my ability I will put links to other articles I found helpful and give insight into what I personally do and use.

Disclaimer: This is just my process, your mileage may vary.

IDEATION

I usually write based on a core idea. A interesting antagonist or a cool setting usually sparks an adventure idea for me. The idea needs to be something you can build on for the rest of the adventure.

From the core idea, I brainstorm to flesh out the adventure. I add details and make lists for things like adventure hooks, minions, encounter concepts, and ideas for the setting/dungeons. These lists and ideas are meant as fodder for writing later on, not all will make it in and not everything in the final product will be in the brainstorming.

What specifically needs to be fleshed out depends on your adventure. You want enough information to make an outline of the adventure with more specifics. If you begin brainstorming and have issues, come back to brainstorming and then try again.

In an adventure you want to give the characters something to do, something to act as an obstacle or threat, and some locations for all those actions to happen in.

For A Opossum’s Hat I started with an image I made in Blender of a opossum magus. Initially the image was just for fun, but after finishing it, I really wanted to put my players into a game with this silly little opossum. So I started brainstorming the adventure in the program Obsidian. Using the Excalidraw plugin, I can doodle and write on a large canvas to collect everything into one space.

In my brainstorming I made lists for things like, information about the antagonist (Miss Ophelia), possible encounters, hooks, maps, and even a sparse outline.

OUTLINING

I like lists. My brainstorming is mostly lists, and the entirety of the outlining phase is one big list. At the end of the day, the outline is just a list of contents in order of appearance, but in practice I use it as a step to map out exactly what I want to write.

The outline makes sure you cover the material you need to, and that its presented in a sensible manner. Adventures usually have a couple basic sections: Introduction and Locations/Encounters. Adventures may have more sections or be broken up into different sections, but at its core you just need to let the reader know what is in the adventure, and what encounters are involved.

INTRODUCTION

The introduction includes information the reader needs up front: statement about the number of players, power level of characters, length of adventure, and contents. Its meant to convince the GM to run the adventure. A good elevator pitch will get more people to give it a try. Showing what’s included at the start may convince GMs looking for new creatures or maps to take a look at your adventure even if they aren’t interested in the adventure as a whole. The introduction includes a few sections itself. Not all are always required.

  • Overview: A 1 paragraph broad description of the adventure, helps the reader make a decision about whether they are interested or not

  • Adventure Hooks: A list of ways the GM could introduce the adventure contents to the players, I usually include one blunt and some subtle methods

  • Background: Relevant history the GM needs to know before they continue reading, includes context for the setting, antagonists, and items

  • Synopsis: A longer more detailed overview of the adventure, what is expected to happen as the adventure unfolds

LOCATIONS/ENCOUNTERS

The adventure will need some locations and encounters for the GM to use and players to experience. Usually each encounter will at least get a description. More complex encounters will need more information like stat blocks and mechanical descriptions. What exactly is included will depend on the adventure and the encounter. For a traditional dungeon scenario a good place to start for the overall layout of encounters is to go from the location overview, to the exterior encounters, to the interior encounters. If an adventure is more linear, presenting the encounters in chronological order is likely the best.

A good resource for encounter writing and adventure writing in general is How to Write Adventure Modules That Don’t Suck

  • Each individual encounter will need a description, traditionally they have a few sections.

  • Box/Read Aloud Text: Used as a flavorful way to put characters in the scene

  • Paragraph Description: Mix of mechanical and flavor description directed towards the GM to help fun the encounter, includes trap triggers, dimensions, room effects, and creatures

  • Stat/Mechanical Blocks: A set of statistics for the creatures and effects in the room

  • Summary: A set of bullet points to help the GM run the encounter at a glance

For A Opossum’s Hat, I changed the general formula to match what I wanted. This is a small location and antagonist meant to be placed in a larger sandbox or as a one-shot. I trimmed the introduction down and expounded on the hooks section to give the GM lots of ways to get the players interested in the adventure content. I left out box text, as I don’t particularly find it useful myself. I added on a Collection section to collect all the antagonists and magic items and maps into one place.

FIRST DRAFT

Using the outline, I write a first draft. I draft in Google Docs because Affinity Publisher doesn’t accept the markdown language that Obsidian uses. I focus on getting information down, not making it read well in the first draft. I also don’t usually add in stat blocks, art, or maps at this point. Anything I desperately need will be added just before playtesting.

Breaking down the draft into sections can help get through the initial writing. Some people find keeping a word count long to be motivating. My goal at the end of the first draft is to have at least some semblance of the information I need in the order I want it in.

For A Opossum’s Hat I wrote each section in order of the outline. If I realized I needed another new section, I added it to the outline and to the draft.

PLAY TESTING

I playtest with the same group of 3-4 people that I can harangue into playing with me. I am eternally grateful. The goal is to utilize what I’ve written to run the game and see what needs to be added, changed, or removed.

I usually just monitor what I needed, what I used, and what I wished I had but didn’t when I’m running the game. Ideally you would also have another GM run what isn’t you, but as a solo writer I don’t have that luxury.

For A Opossum’s Hat I realized I needed more information on the hat and what benefits it might impart the players. I also needed to name the dead mage and the hat. My players mostly avoided the traps by luck of not going near them, but did trigger a bunch of minions at once due to not investigating the farmhouse much. The final fight was difficult but winnable (though they did lose due to being unfamiliar with the game system).

After playtesting I went back and added the names and information on the mage and hat that I wanted to add. These changes can be spotted in the final product vs. the first draft.

EDITING

I use a three phase editing process.

First I have the text read to me using a text to speech program. I listen to this to effectively reword things that don’t make sense, are too wordy, or are just redundant. This is the phase where I fix the words that I wrote in the first draft.

The I take this new text and use SlickWrite to check for grammar and other writing elements. In this phase I try to:

  • Remove and limit adverbs

  • Remove repeated opening words in a paragraph

  • Limit -ing verbs

  • Limit passive voice

  • Fix grammar errors

  • Fix repetitive sentence structures

  • Fix spelling errors

  • Check commonly confused words

After the round of grammar edits I then run the text through the text to speech program again, to double check that things still make sense and sound good. By this stage I’m just checking my fixes.

I then usually get a friend to read through. He has found mistakes like doubling up on paragraphs and incorrect sentence structures.

How different did A Opossum’s Hat look between draft 1 and draft 2? Draft 1 is linked above and the final draft is available in the product. The word count wasn’t terribly different down from 2890 to 2859. The word count difference is usually larger on longer projects.

LAYOUT

I use Affinity Publisher, but anything that can export a series of pdf pages will work. If you’re doing POD, be sure to dig into what your printer requires, because they will likely have requirements. DriveThruRPG has some good documentation for InDesign or Publisher.

My go to articles for general design advice are by Explorers Design [1] [2].

You can use the templates (you have to be logged in) provided by DriveThruRPG for help with margins, bleeds, and such for each size paper. Their set up might be more forgiving to the printer on the margins than it needs to be for digital files, but they will get you started.

General things to avoid included orphaned or widowed lines. These occur when the first or last line of a paragraph or section falls alone on a previous or next page. You can avoid these by using page breaks to group everything back together, or rewording things as needed.

Another general thing to avoid is walls of text. Use shorter, easier to read paragraphs instead.

I usually do the text layout first before making/adding art. The text layout includes setting up text styles and applying formatting to the text. I also add in all my page/column breaks to separate sections and avoid orphan/widowed lines. After I’ve done the text layout, I go back and add in picture frames for all the art into empty spaces. Don’t feel afraid to leave some empty space, it will let the reader’s eyes rest.

My Affinity Publisher is the old version. The tutorials I used to learn it are out of date or missing. Instead here is a list of things you should know how to do in your publishing software and can look up tutorials for. Most should be covered in a overview tutorial.

  • Insert text frames and put text in those frames

  • Link text frames to have the text auto flow from one frame to the next

  • Set up text and paragraph styles

  • Adjust margins, bleeds

  • Set up guides for columns, rows, and baseline grids

  • Edit text wrap settings

  • Make and edit a table

  • Insert text fields like page number and section number

  • Insert pdf bookmarks and organize them

  • Insert picture frames and art into those frames

For A Opossum’s Hat I used DriveThruRPG’s 5x8” POD template. For 5x8” layouts, I usually do a 1 column layout. For A4 sheets I usually do a 2 column layout. For A Opossum’s Hat I didn’t use the baseline grid, but I should have. The baseline grid really makes things look neater.

I used a 10pt sans-serif body font (Karla Google Font) and a 12-20pt serif header font (Lora Google Font). The body text style is justified left while the headers are either centered or left aligned. Some headers are bolded, some are not. Some headers are all caps while others are mixed. Headers are truly up to taste so long as they give the reader some differentiation between the text’s sections.

I inserted page breaks to break apart text at logical places rather than randomly across pages. I separate each section from the previous page (ie putting in blank space between the end of the Introduction section and the Signposts section header).

I added in my encounter tables. Tables are horrible to edit, but they can look very clean when done right. I tend to avoid having too many lines and instead use light fills to help differentiate lines.

I added in picture frames for the art and maps. Maps I added into where they should fall logically and then set the text wrap settings to jump or surround to move the text out of the way. For the art frames, I found empty spaces and place them into those. These empty spaces are made when you add in page breaks to separate sections and avoid things like orphaned/widowed lines.

I keyed the farmhouse map using text in the publishing software rather than the photo editing/painting software. I also used the text in the publishing software to put text onto the cover. Keeping the text in a vector format keeps it from pixelating in the pdf.

When exporting for digital I use the “all pages” setting rather than the “all spreads” setting. If you’re doing POD follow your printer’s requirements for that. I also export the pages as .png’s for use as screenshots on Ithc.io. When I export these .png’s I have to set the matte under the advanced export settings to white (or else it exports with a transparent background and looks wrong.

ART

Good, interesting art will elevate and adventure. Bad, missing art will have people discount an adventure before reading it. My art is not the best, but I make it for as little money and time as possible without commissioning artists (and I have little drawing/painting ability). I have nothing against commissioning artists, I just don’t have the money. I use a couple of techniques.

Photobashing takes photos and shoves them together to create something new. I have a tutorial on this on the blog already. For photobashing I use Affinity Photo (again the older version), but there is the free software GIMP that can do the same things. I use sites like Pexels to find free photos to use to create the art I need. Once I have created the piece, I usually apply this “painting effect” in Affinity Photo. I just hides a lot of errors and helps make it look like you maybe hired an artist. There is also a free program called FotoSketcher you can add on top for even more painterly feeling. You can also find other painting effects that might appeal more to you. Photo bashing is limited by the photos you can find and how well you can extract shapes and paint them together. It has limits.

I also make 3d art in the free program Blender. While Blender is very budget friendly, it has a large learning curve and steep time cost. Modeling and texturing a scene can take several hours, even once you know what you’re doing. You can reuse models and scenes you’ve made, and the end results are very versatile. You can easily change the look of a scene using different materials or just changing the camera angle. There are less limitations for Blender. You can make pretty much anything, it just takes time. “The Donut Tutorial” is the classic Blender starter tutorial if you’re interested. Using Blender, you can even get black and white, hand drawn looking images.

You can also mix the two. Make some elements in Blender and mix them into a photobashed scene. With both of these, the computer does a lot of the work and they require less skill than something like painting or drawing.

For A Opossum’s Hat, I used mostly Blender to generate the images. I edited some in Affinity to finish, but the bases were made with Blender.

The black and white pieces for interior art were rendered using Blender’s Eevee renderer, which allows for a hand drawn look. The cover was a scene rendered with Blender’s Cycles renderer. I used some materials from PolyHaven.

I made the original inspiration image as a landscape, and therefore had to adjust it to be a portrait setup. This was relatively easy thanks to blender. I just edited the render dimensions and changed the camera position to get something appealing.

PUBLISH

The most common publishing locations are Itch.io and DriveThruRPG. DriveThruRPG has POD services, but takes a larger cut of profits if you don’t use them exclusively. I’ve found that people on Itch.io are more likely to pay a price for a PWYW product while DriveThruRPG drives more traffic to the product.

Both sites will require you to have an account (DriveThruRPG requires you to sign up for a publisher account on top of your customer account). Both require tax information, DriveThruRPG requires it up front while Itch.io will wait for you to ask for a payout (or at least until you put something paid up for sale).

DriveThruRPG has a good set of documentation for their systems.

Itch.io has some good official documentation, but also this page with image dimensions is super helpful.

Keep in mind if you’re doing POD, that you will have to wait for the printer to approve your files and wait for a proof to arrive before you can approve the product for sale. Its a bit of extra time, and something to keep in mind.

For A Opossum’s Hat, I just published it on Itch.io for now. I’m usually more picky about what goes onto DriveThruRPG as setting up the pages takes a bit more time that Itch.io.

I usually use the Introduction Section (at least in part) as the product description. Other, better marketing, people will tell you to do something with more effort, and you should. I’m lazy.

I did make clear that the adventure is compatible with Worlds Without Number, because people might default to DnD and I don’t want to mislead them.

THATS IT, YOU’RE DONE

You’ve made a draft, edited it, put it into a layout, made and put in the art, and made a product page and put it up for purchase or download by others. You did it! Thats the whole process.

You should probably also market your project, but I don’t. I find that marketing kills my motivation in a project. As a hobbyist, I’m okay with avoiding that area, and I have no advice on the topic. I’m sure others have plenty.


r/TheRPGAdventureForge • • Feb 13 '22

Introductions New Posters Read This

22 Upvotes

Welcome to r/TheRPGAdventureForge! You'll be getting a greetings DM in an hour if you just joined. The first thing to do is reading the sidebar to get an idea of what we're trying to do here. Then, assign yourself a User Flair! Instructions below:


Your User Flair is based on which of the 8 Kinds of Fun appeal most to you. They are explained below... choose the one that best describes why you play RPGs. You can edit the flair to list additional types of fun if you want. For example, I appreciate Narrative in my RPGs the most, but Discovery is also pretty important to me so I listed it as well.

  • Sensory: Choose this type of fun if you are most attracted to beautiful art, intricate miniatures, dice, maps, music, etc. You probably have more RPG products in your collection then you'll ever rightfully use, and its important to you that there are numerous props and visualization tools while you are playing.

  • Narrative: You take pleasure from a well-told story, with climaxes, plot lines, closure, themes, and all the other literary devices. It is important to understand that the Narrative player wants to experience a story, not TELL a story. That means that RPGs that ask players to make "out of character / author-stance" game decisions (ironically these are often called "narrative" games) will not be as satisfying for you.

  • Fantasy: This is the fun you get by immersing yourself in the game world and feeling like you are a real character in what could be a real place. Immersion and suspension of disbelief is the name of the game - you don't like RPGs that are too abstracted or require to many out of character decisions. You're concerned about "realism" in games that are ostensibly about made-up worlds.

  • Challenge: You want to overcome obstacles, solve problems, and defeat enemies. Strangely enough, this also means Challenge seekers want to be able to lose. Failure and success must be because you made the right choices, either through manipulating mechanics, character creation, or the imaginary world itself. You just want fair obstacles to overcome and tools to play with.

  • Fellowship: You see playing an RPG really as a framework for enjoying time with friends. You seek social interaction and cooperation. In fact, you almost dont really care about the game compared to the people you're playing with. You probably leave the rules and system mastery to others, preferring the memes and inside jokes your group makes while playing.

  • Discovery: Discovery players like exploring and uncovering new things. Things that other more careless players might have missed. But not you, you'll go out of your way to search every corner the world eager to find every secret waiting to be found. You enjoy the feeling of mastery it brings to know everything about everything. This includes self-exploration through things like moral and ethical dilemmas.

  • Expression: You revel in creativity and uniqueness. You want to say something about who you are, what you believe, or otherwise leave your mark on the game. You usually do this by making exotic, in-depth characters, bringing lots of backstory to the game, and using evocative first-person language. You will enjoy games that ask many out of character, author-stance style questions as you get to flex your creative muscles more.

  • Submission: You like to turn your brain off. Chill. Relax. Murderhobo your way to a good time without thinking too much. We'll call it the "beer and pretzels" styles of play, where you just want to goof around with clear, straightforward goals and obstacles that exist just to demonstrate how kick-ass you are. Or are not. It doesn't really matter.


So there you have it. Pick the one that most describes you, most of the time. Then go to the sidebar at the right, click on the pencil next to your username and the phrase "User Flair" and select the appropriate option, adding additional types of fun if you feel like you need to.

[[Edit: Recommend you read the comments below as other folks provide feedback on the eight types of fun listed here as well as the source study these eight were derived from. There is no problem with you reading the concepts and coming to your own, slightly different, conclusions. I encourage you to edit your flairs if you think there's a more precise way to describe the types of fun you're interested in.]]

Adventures will satisfy some of these types of fun more than others. Designs can combine them in lots of ways, and there are many ways to use them in complementary fashions. There are also many ways where they can be a detriment to each other, such as if you were to ask a Discovery player to describe a new room they had just found. You'd be offering them a chance for Expression, but what they really wanted was to Discover what was "already" there. Keep this in mind as you design and provide feedback.

That's it! Introduce yourself in the chat room and happy designing!


r/TheRPGAdventureForge • • Feb 13 '22

Introductions Adventure Forge Introductions

21 Upvotes

Welcome, let us know who you are and what you're all about here! Any sort of chat about what kind of RPGs you play, how you play, and why you play are all great things to include. Come here to get a feel for whether or not you like the vibe we've got going.


r/TheRPGAdventureForge • • Apr 17 '22

World Building Essential components of a good setting guide?

20 Upvotes

For my (Stone Age) setting that has a strong focus on travel and survival, I'm thinking of including the following:

  • Encounter and forage tables separated by terrain type,

  • factions or cultures,

  • a bestiary,

  • adventure hook and settlement tables.

An obvious idea would of course be a world map with a few specific keyed locations, but Veins of the Earth doesn't have that and is considered one of the best.

With my random musings out of the way, what do you folks think could make for a good setting? What would you hope to find in a setting guide that you'd struggle to run setting-specific games without?

Are there any standout examples of setting guides or (especially) "how-to"s that you can point me to?


r/TheRPGAdventureForge • • Feb 13 '22

Theory Design Adventures, Not Just Systems

19 Upvotes

This post was originally made on the r/rpgdesign forum and spawned a great conversation. I dont consider myself to be very "polished," and this post certainly isn't, but maybe it can show off the sort of things we're trying to innovate on here. Here's the original conversation: https://www.reddit.com/r/RPGdesign/comments/sd4tp1/design_adventures_not_entire_rpg_systems/


I was recently exposed to the idea that RPGs are not games.

RPG adventures, however, are.

The claim mostly centered around the idea that you can't "play" the PHB, but you can "play" Mines of Phandelver. Which seems true. Something about how there's win conditions and goals and a measure of success or failure in adventures and those things don't really exist without an adventure. The analogy was that an RPG system is your old Gameboy color (just a hunk of plastic with some buttons) and the adventure is the pokemon red cartridge you chunked into that slot at the top - making it actually operate as a game you could now play. Neither were useful without the other.

Some of the most common advice on this forum is to "know what you game is about." And a lot of people show up here saying "my game can be about anything." I think both sides of the crowd can gain something by understanding this analogy.

If you think your game can "do anything" you're wrong - you cant play fast paced FPS games on your gameboy color and your Playstation 4 doesnt work super great for crunchy RTS games. The console/RPG system you're designing is no different - its going to support some style of game and not others. Also, if you want to take this route, you need to provide adventures. Otherwise you're not offering a complete package, you're just selling an empty gameboy color nobody can play unless they do the work of designing a game to put in it. Which is not easy, even though we just treat it as something pretty much all GMs can do.

As for the other side, Lady Blackbird is one of my favorite games. It intertwines its system and an adventure, characters and all, and fits it in under 16 pages. I love it. I want more like it. As a GM, I don't need to design anything, I can just run the story.

So, to the people who are proud of "knowing what your game is about," is that actually much better than the "my game can do anything" beginners? Or is it just a case of "my game is about exploding kittens who rob banks" without giving us an actual game we can play. An adventure. Or at least A LOT of instruction to the many non-game designers who GM on how to build a game from scratch that can chunk into the console you've just sold them. I wonder if many of these more focused/niche concepts would not be better executed as well-designed adventure sets for existing RPG systems. Do you really need to design a new xbox from the ground up to get the experience you're after, or can you just deisgn a game for a pre-existing console? Its just about as hard to do well, and I'd appreciate a designer who made a great game for a system I already know than a bespoke system that I'll just use once to tell the one story.

Id be very interested in a forum dedicated to designing adventures, not necessarily divided up by game system. Im getting the sense they're a huge part of what we're trying to do here that gets very little time of day. Anyways, Id appreciate your thoughts if you thought any of this was worth the time I took to type it out and you to read it.


r/TheRPGAdventureForge • • Apr 09 '22

Theory What makes for an Interesting Situation?

18 Upvotes

Hello everybody! In a certain sense this post is a follow-up to the one where I try to define what an Adventure is. A definition I have arrived that uses a term 'situation' as the main building block of an Adventure. So I asked myself, what makes a situation interesting?

The Intent

The intent of this post is to try to define and examine the qualities of an 'Interesting Situation'.

In the larger scope of Adventure-developing this should help us understand what our goal looks like when we develop more practical tools for Adventure building.

It also could be used as a tool for examining Adventures to see if the situations it's made of are actually interesting.

I will first provide my definitions and qualities, and then I'll explain how have I arrived at them. Then, I'll provide some examples.

I'd like to see the community's feedback to the definitions and criteria provided, as well as to see the practical advice.

The Limitations

Some notes should be made about the limitations of these definitions:

  1. Not everything that is "Good" is "Interesting". This post's intent is not to imply that everything that does not follow the definitions is somehow 'bad'.

  2. Not everything that is "Interesting" is "Good". This post intent is not to imply that following these definitions is a guarantee when it comes to making a successful situation.

  3. This looks only at singular situations by themselves, without further context (no "situations that are contained within other situations"). This means that some situations might exists that can only fit all the criteria in the context of a larger situation.

  4. Current definition excludes lying to the players. Theoretically it is possible to merely present an Interesting Situation without fictional elements comprising it being actually true. This was excluded, as it made all my attempts of defining it too messy (plus, generally speaking, I believe that it is normally undesirable, as it often leads players to be disappointed, and as such is a more acceptable omission).

The Definitions

A TTRPG situation is a set of fictional elements that can be reasonably isolated from the rest of the fictional reality.

An interesting TTRPG situation is a TTRPG situation that allows players to make Interesting Choices*.*

To allow players to make Interesting Choices*, a* TTRPG situation must fulfil the following criteria:

  1. Fictional elements represent different values*, some of which are* at odds with each other

  2. Players are informed about the connections between contradictory values and their connection with the fictional elements

  3. Players share those contradictory values

  4. Players are in the position of power from which they can meaningfully affect the fictional elements of the situation

The Explanations

First, the definition of the TTRPG situation - it comes straight from the previous post of mine, so I won't linger on it and move on to the interesting bits.

The first bit is defining an interesting Situation through Interesting Choices. Now, while I can't see how could I meaningfully prove it, I believe that an act of playing a TTRPG is ultimately an act of making choices. It's not a particularly deep insight, and hopefully this will be found agreeable by the members of this sub. And if we accept that, I think that the idea of interesting situation being such a thing that allows for interesting choices to happen seems like a fairly reasonable take, too.

Now, this, of course, leaves me to define what an "Interesting Choice" is! Which is not easy.

I made a decision early that my definitions and criteria should be inclusive. Therefore, to make the task a bit more surmountable, I have decided to flip the question and instead ask myself "which choices are definitely NOT interesting", and define an Interesting Choice as an opposite of that.

What I have arrived at was the following:

  • Choices that can be trivialised/solved. When one of the options can be determined objectively better than the other (choice between a sword that deals 2 damage and a sword that deals 6 is trivial and not interesting).

  • Choices between the unknowns. When you don't actually know what the options are you can't actually make an meaningful choice, as it is effectively random (choice between a blue sword and a red sword - one deals 2 damage, the other deals 4, but you don't know which is which).

  • Choices between the equivalents. When you choose between equal options you can't actually make a meaningful choice, as it is effectively random (choice between a red sword that deals 3 damage and a blue sword that deals 3 damage is not an interesting one).

This is the biggest list I could come up with that included choices that were definitely uninteresting by themselves.

Now, we are to find what's the opposite of all that. With point 2 this is easy! Inform the Players then.

The other two are tricky. We have to find something that can't be 'solved' yet is also not an equivalent.

If a choice is solvable that means that if we were to use all the relevant criteria to judge an option's desirability we are to find an option that is a clear best choice. Now, to make a choice that is not that, it's pretty clear that we must have more than one criteria for judging it merits. As long as there is only one criteria there will always be the best answer, and if there won't be it's only because there are equal choices.

Now, having more than one criteria does not guarantee that there isn't a solution. So some of them must be at odds with each other! As in, maximising both criteria A and criteria B at the same time should be impossible.

Swapping the word 'criteria' for a word 'value', as I think it's both more generic and also rolls of the tongue better, and here we are. Interesting situation must represent values that are at odds with each other.

Of course, none of this works is the player just don't give a damn about one of the criteria, so this is also an important part of the definition. If Value A exists, but does is not accounted in the players decision making process, well, it is irrelevant for the choice.

And thus we are done with an "interesting Choice" part. The last one left if the 'allow' part. Players have to be able to actually make the choice they want to, otherwise all of this is nothing but set dressing and empty words. This gives us the criteria number [4].

Now, it is not impossible that I have missed something, say, another kind of an inherently not-interesting choice that my criteria still permits, but I couldn't find it. Generally speaking, I am very satisfied with those 4 points! I think they are pretty intuitive and fairly broad, yet I've also often seen those violated in cases that were clearly supposed to be tough choices.

An Example

I will now provide a simple example-Adventure that follows these criteria. After that, I'll break each individual criteria and show how this affects the Adventure and the ability of the situation to be interesting.

The Adventure, as usual, would consist of a hook and a situation.

The Hook is that players need to get to a certain place before an Important Event happens.

The Situation is that to get they need to pass the abandoned and dangerous underground city. As the players arrive, they are informed that there are 2 known paths though the city, a long one that passes near a giant ancient statue, and a short one that goes though a waterfall where a terrible kraken lives.

Let's look at our criteria:

  1. There are 2 values in play that are contradictory. Values are 'character survival' and 'getting there before the Important Event happens'. No path satisfies both.

  2. Players are informed that this is the case

  3. Players share those values. Time pressure is the Adventure Hook, and caring for safety of their characters can be assumed.

  4. Players can in fact make that choice.

Therefore, the situation is an Interesting one.

Now, let's break it!

Let's break [1].

  • There is no kraken - players obviously choose the waterfall route

  • The paths are of the same length - players obviously choose the statue route

  • The waterfall path is the longer one - players obviously choose the statue route

All these put the values out of conflict and make a choice is a solvable one.

Let's break [2].

  • Players don't know about one of the route's existence - they obviously choose their only option

  • Players don't know about the kraken - they obviously choose the waterfall route

  • Players don't know that paths are of different lengths - they obviously choose the statue route

  • Players don't know just how much is the statue route longer - their choice is either a guess or conservative one (waterfall route)

  • Players don't know just how threatening the kraken is - their choice is either a guess or a conservative one (statue route)

Lack of critical information prevents players from even realising they are faced with an interesting choice. Lack of full information

Let's break [3].

  • Players don't actually care that much about getting there in time - obviously they'll take the statue route

  • Players don't see kraken as a threat to their characters - obviously they'll take the waterfall route

  • Players believe that GM won't dare to actually kill a PC - obviously they'll take the waterfall route

This one is pretty obvious, too. If players don't actually care in the first place, the conflict of values does not exist, and therefore there is no interesting situation.

Let's break [4].

  • One of the routes is completely blocked - obviously players choose the other one

  • Average enemies found in the underground city is way, way above what PCs are capable of fighting - therefore they can't take either of the choice

If players straight up can't actually make a choice in any meaningful way, well, they obviously can't make a choice. Not much to be said here.

This example is meant to show how a fairly basic yet interesting situation follows the criteria, and how stopping to follow this criteria in virtually any way immediately stops the situation from being an interesting one.

An Important Addendum

As mentioned before, these is one thing missing from this scheme - lying to the players. Strictly speaking, point [1] can be skipped as long as point [2] lies and tells the players that point [1] exists. This works only in the moment, but it puts the players in the exact same position as the real deal.

This might not sound too great for obvious reasons, and I kind of agree, but I also believe that it's something worthwhile to consider. It is true that as the game progresses the deceit is likely to be revealed, but it's normal for the situations to change after being affected by the players actions, so it's still kind of part for the course.

The Next Step?

The next step would be, of course, seeing how people react to these ideas of mine. After I am satisfied with this thing, I'll finally study the practical implications! I'll examine each criteria and try to find some methodologies that would allow an adventure designer to consistently create Interesting Situations.

Conclusive words

Personally, despite the fact that I feel like I've made more assumption in this post than in my previous one, I am surprisingly satisfied with what I came up with! This seems both inclusive, yet pretty robust, and also something often see unfulfilled, both in Adventures and in actual play, to their detriment.

What do you people say? Perhaps you can break one of my criteria without breaking the example situation? Or maybe I have missed a case of an inherently uninteresting choice? Or maybe you would like to share you tips on what makes situations interesting? Or maybe you want to say that I have finally lost my mind and am wrong about pretty much everything?


r/TheRPGAdventureForge • • Mar 14 '22

Theory Iconic Encounters - Adventure Design Blog Series that examines great adventure encounters!

Thumbnail self.oldskullpublishing
17 Upvotes

r/TheRPGAdventureForge • • Aug 10 '22

Resource Good adventures examples

16 Upvotes

So I have read a lot of both the Alexandrian and the Angry GM blogs. The nodes based designed for adventures and the use of timeline to determine the bad guys actions really speaks to me but I feel like I'm missing good examples.

What prewritten adventure modules (whatever the system or the genre) does r/TheRPGAdventureForge recommend ?


r/TheRPGAdventureForge • • Mar 12 '22

Theory [UPDATE] So, let's try do define what an "Adventure" is!

16 Upvotes

Hello everybody! You might know me as an author of the original "So, let's try do define what an "Adventure" is!" post. I've always planned to write an update to that post, but, well, stuff happened! But now I am here.

The Intent

The intent of this post is to follow up on the original post, it's discussion and some more of my own thoughts!

Similarly to it, I don't expect to find a concrete answer - though now I feel more solid about certain things. We'll have to discuss this, and to interrogate the related concepts.

First, I'll lay out my new definitions, and then I'll explain why they are the way they are, in the process addressing the stuff from the previous thread and my processes.

The Definitions

A TTRPG Adventure is a set of TTRPG situations that are connected through Hooks*.*

Hooks are fictional reasons for the players to engage with the TTRPG situations*.*

Where are two kinds of Hooks*:* Opportunities and Demands*.*

Opportunities are Hooks that allow for Players to refuse engaging with the associated TTRPG situation*.*

Demands are Hooks that do not allow Players to refuse engaging with the associated TTRPG situation*.*

A TTRPG situation is a set of connected fictional elements that can be reasonably isolated from the rest of the fictional reality.

A TTRPG situation can contain multiple TTRPG situations within itself.

The Explanations

Now, that's a lot more than the last time! The big thing I've noticed is that many people have pointed out to the need for a "hook" or "calls to adventure" of sorts, one way or another. It didn't really set right with me, and some thinking later I finally realised why - because hooks were the 'connective tissue' I have mentioned! So, of course, it did not sit right with me as I have already separated 'situation' and the 'connective tissue' by that time. Hopefully the new version is more appealing, as now it makes this clear and explicit, both for me and for you!

You might remember from my last post that I planned to try and create the smallest possible adventures to see things through. These plans ended up scrapped! The reason for this is that almost immediately after that initial post I have seen u/TheGoodGuy10's post about 'An Orc and a Pie', which is was considered to be the smallest possible adventure. It was notably different from my definition, as it was not a set of at least 2, but a 1 situation! This made me reconsider my definitions further, at fully realise that the connective tissue of 'hooks' can be present even if it does not connect 2 situations together. The issue was rather silly - I forgot of the most important bit, of the Players, who, of course, must be connected to the Adventure, too.

Now, there are some other interesting things going on with these definitions I wrote. First, let's talk about why I felt the need to add 2 distinct kinds of Hooks. Now, the first thing to acknowledge is that it is almost certain that you can classify various Hooks in various ways! This is but one way. I added it because reading the comments in the previous thread a very commonly used term 'call to adventure' - which I though was a bit too narrow a view, even if only by implication. Many sandboxier adventures rely on non-Demanding hooks: "there is giant tree to the North on the map, let's go see it" or "ooooh, poster says there is a huge reward for the bandit captain terrorising this trading route! Let's go get 'em!". One of the reasons I wanted to find these big core definitions is so we can see the possibility space it allows for, and to potentially find something new or previous not though of. So that's why I put these in!

Another big thing is that we finally came to defining a 'TTRPG situation'... kinda. If you have noticed, I have now introduced the 'reasonably isolated', which is a very non-specific turn of words! However, unlike the previous time where I have said "because I dunno" here I'll say that this is actually by design.

See, initially, I noticed a thing - say,there is a very classy adventure, and at some point of it there is a dungeon. Now, dungeon might very well have connections with the rest of the adventure, but it's a very isolated part, a part that, when engaged by the Players, is mostly self-contained. So we have a situation of the Adventure scale (goblins are raiding the village to further the agenda of an Evil Wizard!) and we have a smaller situation (goblin cave dungeon). My initial thought was "well, let's go further and find the smallest grain to find some lower level definitions!". So I took a classy dungeon and decided to deconstruct it.

As a simple, respected and a well known dungeon I took the very first Goblin Lair from The Lost Mines of Phandelver, a starer DnD 5e adventure. Initially I thought I'll dig into it, I'll separate it room by room and describe each room as a situation with it's own Hooks. The problem is this didn't work. Now, on the purely surface level, it's not like it was impossible - in room X there are wolves, they are barking if they see PCs, so there is a Demand to stop them, but they can also be befriended, which is an Opportunity, etc... But something inside of me looked at the notes I started making and said "No, this isn't right. What you are writing right now is a lie. This is not how any of this works".

The thing I had to confront, is that Adventures are not like Doom levels. That is because TTRPGs are fundamentally different kinds of games. In Doom, all the ways a Player can interact with the level is pre-determined, but that is un-so in TTRPGs. One could say that one of the most memorably-defining features of a TTRPG is that you can do (or at least try to do) a thing if it makes sense for the thing to work. And this screws with Adventure design. See, in that dungeon, Players also can try to talk with things out with a goblin, give that goblin now-pacified wolves and help him lead an anti-bugbear revolt. One can write this down as an Opportunity, but it's an Opportunity that is... of what scale exactly? Also, it's not explicitly listed in the Adventure. So, what do we do about that? To try an quantify all meaningful things Players could end up trying in that dungeon is almost certainly impossible and also heavily impractical. Now, from an Adventure designer's perspective it makes sense to list some more obvious ones, but the list is almost certainly not comprehensive. But from a perspective of making definitions, quantifying things like this, that makes it impossible to write them all down. There is also a question of scale - dungeon is interconnected, things from one of these room-scale situations can affect the other - hell, they can literally shift from one room to another. Players can lure an evil bugbear into a trap that was initially laid down for the Players. On top of that, some things that don't have any hook at all might end up working as if they are during Play - a small empty room might end up a tactically sound last stand for the Players, a wardrobe can be used to block the entrance, etc.

So... here we are. I look at my notes and I say "I can't just write down all the hooks between the rooms, not in good faith at least. Also, these are not disparate rooms - this is one whole dungeon, the goblins from room 1 are subservient to Bugbear from room 8, and none are actually locked in to stay in these rooms". And, to me, it follows - there isn't the smallest grain from which 'situations' are made of, there is just a smallest 'reasonably isolated' situation. Which lays in the eye of the beholder, of course, and I am afraid there isn't a way to clarify that further! But I can't say I am particularly dissatisfied with this answer either - it seems practical enough, and sometimes things like these have to do.

Now, as for a situation containing multiple situations - I think this one is largely self evident. But, just to make sure, let's make an example. Goblins are attacking the village! The operate from a cave, and have been driven mad, because an Evil Wizard gave them a Cursed Idol. Wizard plans to use the goblins to weaken the village to attack himself with is undead! The reason he does this is revenge to the mayor of this village. Now, this is a situation, and it's also 3 situations - a goblin dungeon, a planned siege, and village politics related to whatever this revenge business is all about. These are obviously related, but can also be treated as mostly separate from each other (hence the 'reasonably isolated' bit). A more obvious case would be a sandboxy Adventure, where the larger 'situation' is a setting that just happens to contain a wide array of various situations.

The Next Step?

Now, this time I am - for now - quite satisfied with these definitions, so unless something extraordinarily comes up on the comments I don't think I'll be making a third update soon. Now, I want to write some more practical articles about principals of good design rather than general definitions.

Conclusive Words

I am glad I got an opportunity to work with this community! (and hopefully I'd be able to continue, which is regrettably not a safe bet for me anymore) And I am way more satisfied with definitions this times. Of course, no doubt we'll have to examine these terms again! What do you think of them? Know any adventures that won't fit with these definitions? Or, perhaps, you'd like to make an argument that No, Adventures Are like Doom levels?


r/TheRPGAdventureForge • • Feb 14 '22

Theory So, let's try do define what an "Adventure" is!

16 Upvotes

Seems like an obvious place to start, innit?

The Expectations

As this is the very beginning of this sub project, I don't actually expect that this post will find an answer! We'll have to discuss the topic, and also interrogate many related topics to get the actual handle on the actual important bits before we'll have a vocabulary and understanding needed to take on this definition.

Still, we have to start somewhere! If only to see how far we've come later on. And I don't see why should we not start with a long shot.

In this post I shall provide my definition of an adventure. In responses I expect to see other definitions, critique of my definition, interrogation of the concepts and the language of my definition, the logic behind it, etc.

The Definition

Pondering the topic on my own, I have arrived at the following definition:

A TTRPG Adventure is a set of connected TTRPG scenarios.

The Explanation

I wanted a definition that accounts a variety of pre-made ready-to-go TTRPG content. This, I think, should include all from the range between Linear and Sandboxy adventures.

Linear adventures are defined by, well, their linearity: from scenario A follows B, then C. The more they deviate from this, the more "sandboxy" they become.

Sandbox adventure is defined by it's lack of linear structures. It is effectively a setting with scenarios A, B and C located somewhere in it. Writing this down I noticed that while, yes, there is no linear structure, there still is a structure - their shared setting. If sandbox lacked that connective tissue, this hypothetical book would just be a collection of scenarios.

Which is how we arrive at my current definition: Adventure = some scenarios + connective tissue between them.

This definition also gives us this: a single classical dungeon is an Adventure, where individual rooms are scenarios (combat, puzzles, traps) connected to each other through dungeon corridors. It also should be able to accustom all the Adventures I've seen thus far.

There is a pretty glaring issue with this definition - I introduce a concept of "TTRPG scenario", which I have not defined. Originally I planned to include a draft version of this definition too, calling it a "conflict", but my hand hesitated here as I noticed that I found myself unsure. It felt potentially too narrow, in the sense that while I couldn't find an immediate issue with this term, I felt like I might be too eager to jump on it. Another version called is "a scene", but I found myself dissatisfied with it, too, as this felt too vague and is associated with non-game-like media operating with very different structures and confines. Ultimately I have decided to let this one be undefined for now. I do wonder if anyone here has a better idea - or perhaps would say the initial "conflict" is good enough.

The Next Step

The next step from here on (other than the TTRPG Scenario definition) would be to put this into practice - to create a Smallest Possible Adventure.

Is should consist of exactly 2 scenarios, connected with some tissue. I plan to create 2 versions, a linear one and a sandboxy one.

Conclusive words

So where it is. Something to start the brain juices flowing, hopefully. What do you think of that definition? And about those pesky "TTRPG scenarios", too? Wanna take a crack at a Smallest Adventure?


r/TheRPGAdventureForge • • Nov 05 '23

Resource rpg adventure design resource list

15 Upvotes

So, I'm planning to release an osr esque adventure module, and now I'm putting together a list of some adventure design books that can help me, I'm leaving this list open for edits for anyone who wants to contribute and expand, enjoy!

https://docs.google.com/document/d/1atjMEUlrARJcxNWb0c9ihuc54dkGHyBx7SdFC1CXYNk/edit?usp=sharing


r/TheRPGAdventureForge • • Mar 24 '22

Feedback: Full Adventure Looking for feedback on my psychedelic dark fantasy Stone Age dungeon

15 Upvotes

Hey folks! I’ve written up a mostly-finished draft of a dungeon for my ‘psychedelic dark fantasy’ Stone Age setting for the OSR game Knave. I’d love some feedback and/or test audiences! Go easy on any editing goofs; I’m kind of between passes.

I guess some obvious questions would be:

  • Would the structure make it easy to run?

  • Is it interesting and creative?

  • Would it make a fun adventure?

  • Does it all make sense?

https://docs.google.com/document/d/1K8E0z25o2P5ZRogl91SvHy5XRvjVRNFPeYaourS8XFY/edit?usp=sharing


r/TheRPGAdventureForge • • Mar 07 '22

Feedback: Full Adventure Lost and Forgotten - An adventure that messes with memories [Free]

15 Upvotes

Hi everyone, I've just self-published my first adventure and thought it might be an interesting one to talk about. Since it plays with missing memories and forgotten characters, it was a real challenge to design the environmental story-telling in a way that would make sense both to the players and the GM reading the adventure. More discussion under the spoiler tag.

Links below (free or PWYW if you want to check it out)

Itch: https://kellymakesgames.itch.io/lost-and-forgotten

DrivethruRPG: https://www.drivethrurpg.com/browse/pub/21159/Kelly-Whyte

Having to write characters that almost no-one can directly talk about is a real challenge, even more so to then have to convey their absence to the PCs. It's a real pleasure when running this game to gradually see players put the pieces together. Figuring out Mary is indeed a real person, that the siren works in a sound-based way, that way more people have gone missing than anyone realises, it's a real journey!

I hope this helps someone writing similar ideas. Having a 'what really happened' section, timelines and corrections to the rumours that are floating around are really useful tools when dealing with a lot of leads.


r/TheRPGAdventureForge • • Feb 22 '22

Theory What really is an adventure?

15 Upvotes

What really is an adventure? If we want to keep away from railroading and setting scenes directly isn't it just a collection of situations, locations and resources?


r/TheRPGAdventureForge • • Jan 24 '23

Weekly Discussion Distinctions and Definitions - Difference between being a RPG System Designer vs and Adventure Designer

14 Upvotes

This sub is hoping to fill a niche within a niche. Specifically - adventure design in RPGs as opposed to system design.

But is there really a useful difference between the two?

What do you think. What are the skills required to write a RPG system as opposed to writing an RPG adventure? What defines "being a good system designer" and "being a good adventure writer?" Can one be good at one and not the other? What are the benefits of each?

As an individual, I take the stance that systems design is "how to play a potential game." Adventure design is what makes the game "get up and go." As an example, D&D PHB is a system that explain how to play, but you need Mines of Phandelver or an equivalent adventure structure to actually start playing. Alternatively, Blades in the Dark includes system-type rules like position and effect, but also builds in an adventure structure with its starting scenario + gameplay loop of score --> downtime --> new score. PBTA games tend to be good at this. Do you have opinions on this way of looking at things?


r/TheRPGAdventureForge • • Jan 03 '23

Feedback: Full Adventure Idea for a Depthcrawl, looking for feedback - The Interdimensional Onion

14 Upvotes

Hi, I was recommended to repost this here:

For those not familiar with Depthcrawls, here is a great article on them

https://thealexandrian.net/wordpress/48524/roleplaying-games/pointcrawl-addendum-depthcrawls

The TLDR is they are adventures like the Gardens of Ynn, where the points of interest are randomly generated and get weirder as you get deeper into the "dungeon". This is heavily inspired by Emmy Allen's works.

Premise: The Interdimensional Onion is a multi-multiverse, consisting of many layers, each its own multiverse. Each layer of the onion is surrounded by a skin. Within a given layer, interdimensional travel and teleportation works normally. The skin disrupts dimensional travel (see Going Forward and Going Backward)

Depth: A key idea in Depthcrawls is depth. Depth measures how far into the dungeon you have gone, and generally is correlated to the strangeness and danger of the points of interest. In the Interdimensional Onion, your depth equals your layer. The deeper you travel into the onion, the weirder the worlds and events get. Each layer in the onion is its own multiverse, containing a nigh-infinite collection of worlds.

Why Enter the Onion?

  • Research - It's a dimensional anomaly, and many dimensional orgs will pay for collected data.

  • Treasure - If the PCs are not already interdimensional travelers, the onion offers them a chance to explore strange worlds they wouldn't normally have access to. Many of these worlds will have magic or technological items that the PCs have never seen before.

  • The Onion's Core - Supposedly somewhere deep in the Interdimensional Onion lies the Onion's Core. Legend says that players who reach the Onion's Core get <TBD>.

Exploring the Onion

The onion can be traversed with an Onion Key. An onion key is a techno-magical device that can be discovered or crafted by PCs with the appropriate knowledge. When entering a new location in the Onion, roll once on the location, details, and encounters table.

Entering the Onion: Players can enter the onion from any location in any universe, provided they have an Onion Key and there are no interdimensional impediments blocking their access to the Onion. See Going Forward for the effects of traversing the onion's skin.

Going Forward: When players first enter the onion, or are ready to venture deeper into the onion, they can attempt to move to the next layer by crossing its skin. Doing so increases their depth by 1. When crossing a layer of the onion, you are randomly deposited to a new location in the next layer. It is impossible to control where you end up, the onion disrupts interdimensional travel. You (usually) won't be dumped out somewhere that will instantly kill you. Roll on the location table with your new depth. Crossing the skin creates a time dilation effect. For those traversing the skin it will feel instantaneous, but from an external observer it will seem that an hour has passed. Passing through the layer's skin requires a roll on skin-traversal side effects table

Going Backward: When going backward, you can choose to return to a point you have visited in the previous layer, or instead go somewhere random using the Locations table. Going backward is a lot easier than forward, and decreases the depth counter by 1. The time dilation is reduced to 5 minutes, and players don't need to roll on the skin-traversal side effects table. Its as if the onion wants them to turn back ...

Leaving the Onion: You can leave the onion via the same rules as Going Backward, provided you are in the onion's outermost later.

Lateral Movement: Players may travel to other worlds in their current layer. Within a layer, interdimensional travel works as expected. Players can use whatever plane-hopping capabilities they already have, or use the Onion Key to transport them to another random location within the layer (roll on the location table using the player's current depth). The onion grants them no special knowledge of the surrounding dimensions and planets within the layer relative to a given location. Players must scry, explore, or research that on their own.

Explore: If the players decide to stay put and explore their current location, roll on the Events table once per hour. The GM can roll more frequently if they think it will be fun.

Random Tables

These tables are incomplete, just throwing ideas at the wall. Ideally each list would have 35 elements in the completed version. For each of these tables, roll a d20 + the PCs current Depth. The depth of the first layer of the onion is one, and each subsequent layer increases the depth by 1. For example, if the PCs are entering layer four, the would roll 1d20+4

Locations

  1. A village in a nation analogous to 2nd century AD Korea.

  2. A nightclub in an intergalactic space station

  3. A domed city on an asteroid where asteroid mining is taking place

  4. A farm on an otherwise dead, red planet

  5. A stone-age village on an alien planet

  6. A wizard school in a high-fantasy world

  7. A basement under a bar in 19th century London-analogous city where occult rituals are taking place

  8. A virtual reality simulated by a giant computer

  9. A dreamworld filled with the collective dreams of dreamers across the multiverse

  10. A densely populated mega-city in the 31st century.

  11. An alien onion farm

  12. An observatory on a flat-diskworld. An astronomer is mapping out other disks in space.

  13. A steampunk city on the back of a giant whale swimming in an ocean of blood, or tomato paste

  14. A wasteland suffering under nuclear winter

  15. A Fae dimension

  16. The control center of an abandoned dyson sphere

  17. A universe entirely composed of dark matter. Everything is invisible and the only interactions are gravitational.

  18. The den of a cabal of brain-eating psychic creatures.

  19. A house surrounded by a magic forcefield inside the mantle of a planet. A single person sits inside.

  20. A ghost realm filled with spirits of the dead.

  21. An empty void. There is nothing here at all. Players float in nothingness.

  22. The deck of a time-travelling spaceship

  23. A wizard laboratory. The wizard is growing an army of mutated Alliums in vats.

  24. A gymnasium on a giant onion-planet. Everything is onion themed. It's a bit absurd.

  25. A prison dimension filled with multiversal criminals

  26. An alternate version of one of the PC's hometowns. In this version the PCs never existed.

  27. The Onion's Core .... It contains the secret of the onion: The onion was made by ancient engineers, so advanced in their craft, that they could reach to the realm of ideals and manipulate the Platonic Forms as easily as they could manipulate matter. The Interdimensional Onion is an accident, an experiment gone wrong with an early prototype of this technology, designed to bring the metaphorical concept of an onion into the physical universe. The test was conducted in a pocket-universe, which has since bloomed into the Interdimensional Onion. Why an onion? Who knows. Maybe they thought it would be a harmless test, a simple concept with both literal and metaphorical meanings.

Details

  1. The location is significantly hotter than expected for a normal location of its type.

  2. Location is 2 dimensional. Players are compressed into flat beings for the duration of their stay

  3. No gravity

  4. The location is significantly colder than expected for a normal location of its type.

  5. The location has more than 4 spatial dimensions. Expect tesseracts.

  6. Roll twice on this table

  7. This location is in the past of another location the PCs have already encountered. PCs should be careful to avoid changing the timeline. Reroll if this is not applicable.

  8. This location is a parallel version of one the PCs have already visited

  9. There is a climactic battle taking place between an evil wizard and their also-evil apprentice

  10. Inhabitants of the locale are anarchists

  11. Deposit of Onion-ore, a rare metal with mystic properties

  12. The location has recently had someone change its past. NPCs from the previous version of the timeline are phasing out of existence, while NPCs from the new version are phasing in. The PCs could potentially help to adjust the past to allow for both versions of the timeline to exist simultaneously.

  13. Onions are sprouting all over this location, even if that should be impossible. The locals don't seem to mind.

  14. The location is undergoing a zombie apocalypse

  15. This location is a future version of one the PCs have already visited.

  16. The location seems to be mocking the PCs. Art, architecture, and geological formations seem to be mirrors of their insecurities. The location's inhabitants don't seem to notice.

  17. Upon close inspection, the PCs realize the terrain is made of nanomachines

  18. There is a crashed UFO filled with advanced technology.

  19. The gravity is much higher than expected for this locale. It might be difficult for the PCs to stay for very long.

  20. It's pitch black. There is no natural light, and artificial light is less effective than it should be.

  21. Roll three times on this table

Skin-Traversal Side Effects

  1. Your favorite food changes to one of your choice.

  2. Develop an onion-like body odor

  3. Body glows iridescent colors for 2 hours

  4. Dominant hand is switched for 1 week

  5. An onion appears in your travel bag.

  6. Cats tend to avoid you for 1 week.

  7. The PCs appear half-buried under a small pile of onions. They harmlessly spill out of the pile.

  8. Receive chilling visions of the Future

  9. Your favorite food becomes Onions

  10. Temporarily become invisible for 2 hours

  11. Noticed by beings monitoring the barrier

  12. Time dilation is 2 hours instead of 1

  13. The PCs clothes are covered in spider silk.

  14. Body transformed to a different species for 1 week.

  15. Grow gills and insect wings for 1 month.

  16. Time dilation is 4 hours

  17. Physiology becomes onionlike for the remainder of your stay

  18. Time dilation is 1 day

  19. PCs have a philosophical revelation

  20. Become a spirit-being if you are not already one. Become material if you are a spirit-being. Lasts one month

  21. Your arrow of time is reversed or rotated

  22. Your favorite color becomes onions.

  23. Roll again on this chart twice

Events

TBD

Encounters

Note: encounters are in addition to the normal populace you would expect to encounter for a given location and its details.


r/TheRPGAdventureForge • • Apr 10 '22

Theory What inspires your ideas for adventures?

14 Upvotes

Is it media like books, movies, or songs? Is it the source material of the game itself? How about original ideas? Do any of them come from the players? Do you take the game system as is? Do you change rules to make it fit your adventure better? Do you change your adventure to fit the system?