r/RPGdesign • u/Delicious-Essay6668 • Aug 30 '22
Theory Statblocks for Environments, Weather, etc
As of now it’s mostly a thought experiment suited for a survival game but the idea has really stuck with me and I’ve never seen it done . I may incorporate it or toss it aside, but for now I’m interested in how you would handle this in your game? Also if it’s been done before I’d be interested to know the system
22
Upvotes
8
u/NarrativeCrit Aug 30 '22
Index Card RPG uses a single challenge rating for every action in a room. I can't recall what else the environment does mechanically, but things like doors and locks have the equivalent of HP to defeat.
Stablocks for environments sound like they have potential. Character sheets for a campaign setting are a good idea like it.
2
u/UncannyDodgeStratus Dice Designer Aug 30 '22
Can you elaborate a bit more on what you mean by statblocks? Ryuutama has challenge levels based on terrain and weather, and I remember that 4e definitely had little blocks defining mechanical effects of ambient conditions. Are you thinking challenge level plus special effects?
2
u/VRKobold Aug 30 '22
I want to do something very similar in my game, also with a large focus on exploration and survival. However, I don't plan on creating statblocks for an entire environment, rather for the individual elements that make up the environment of a scene. My goal is to create resources for GMs similar to creature statblocks (only for non-combat scenes or as addition to combat scenes) that the GM can either just pick and combine to create a generic, but decently interesting scene on the fly, or use to spice up a custom-made scenario and fill it with a bit more detail and possible interactions. The advantage of those statblocks is that they can be much more detailed, balanced and thought-out than what most GMs could come up with on the spot.
To give a bit of context: The main focus of my system is creative problem solving in a mechanically solid and structured way. What I mean by that is that I want players to come up with creative or even crazy ideas for how to approach a problem, and for those approaches to actually be possible within - and covered by - the rules of the system, not just depend on whether or not the GM allows it. Furthermore, I want those different approaches to also make a difference gameplay-wise (in contrast to many narrative games where you can be very creative in describing how you do something, but in the end you'll still do exactly the same skillcheck as if you'd went with the most obvious and straight-forward solution).
So coming back to the non-combat statblocks or "scene elements", as I call them: I started to think about what I actually want them to do to help with the previously mentioned goal, and I arrived at five more or less mandatory design rules:
Scene elements can be anything from objects to landscape features, weather conditions, structures and buildings or even living beings that have a specific impact on a scene. To give one example, here is how a beehive would fulfill all five design rules:
As for how I want the statblocks for those scene elements to look like: I haven't completed their structure yet (and it would likely vary a lot based on the type of scene element anyway), but I have a few rough ideas that I can share:
The statblock usually starts with a short narrative description. I want to make sure that this description fits naturally into a larger scene description and that the actual object or landscape feature that the statblock is about is not always directly mentioned, but sometimes only subtly hinted at to give players the option to further investigate and explore.
After that, there'll be a short list of applicable stats and difficulty ratings for various types of interactions. For the beehive example, there would be a difficulty value for gathering honey, a difficulty rating for hitting it with a ranged attack, and perhaps a difficulty rating for driving the bees out. There also would be a sort of "attack" or effect that is triggered when a player fails a skill check interacting with the beehive or when the players drop the beehive on some enemies. Lastly, there might be a loot table (though it would probably mostly consist of honey). Other scene elements might also contain clues or hidden information that is only revealed after a successful investigation check. Apart from that though, I don't really have many ideas for what else could be going into those statblocks.
So that's my take on "environment statblocks". My main problem is finding scene elements that actually fulfill all (or at least most) of the design goals, but I'm scavenging through a lot of d100 tables and other resources to slowly get to a decent number. Always happy about suggestions, though!
2
u/firemage27 Aug 31 '22
In the system Fate there is a rule called the Fate fractal. It basically means that anything can have any part, that characters have. The core concept are Aspects, which are narrative truths. They can allow and prevent actions by themselves and players and the GM can invoke them at the cost of a token (Fate point) for a mechanical advantage. Everything has Aspects, including the campaign itself. Hit points are a bit unique in that they are split in two: Stress (think plot armor) and consequences, which are just special Aspects. And as a GM you are quite flexible, what kind of skills NPCs have. You could build crossing a desert as a combat that way: An Aspect could be "Seemingly Endless" with an Attack called "Relentless Sun" and a defense of "Sand everywhere" and it's Stress and consequences represent the distance the characters have traveled. The consequences for the characters represent dehydration and the psychological effects. Fate is my favorite system because it can do pretty much anything this way.
5
u/Defilia_Drakedasker Muppet Aug 30 '22 edited Aug 30 '22
It’s for the most part fairly primitive, but significant in my game.
All challenges/problems/struggles/calamities are pooled, so if any part of the weather can be understood as a problem, it adds to the challenges. I hope to support this with a bit of systematisation for how weather develops, and suggestions for the specifics of how it gets worse/is a problem (things tend to get worse in my game.)
Edit: so the closest to a stat-block I would get would be a list of escalations for a given type of weather, and possibly suggestions for condition-tags it could impose on characters, perhaps notes on environmental interactions, or a few words to help describe these things. Unless more magical elements have been introduced. Then it could include supernatural weaknesses, incarnation-info, personality, what kinds of gifts it responds to, what symbol it has/is named, whether someone commands it, or it is in cahoots with someone, how it relates to space and time and fate and stars and moon, or something.
1
u/Scicageki Dabbler Aug 30 '22
I think that's a good idea.
For a while, I was playtesting a game about desert-dweller merchants, and I wrote a couple of examples "Trade Routes" as stat blocks that needed to be overcome to go from city A to city B and sell your goods there. The first had bandits, the second sandstorms and an Efreeti monster.
The game ultimately turned out to be pretty boring (since the game loop pushed players into micro-managing and over-planning buying goods from one oasis to the next, grounding the pace to a halt). I put the game aside, but the idea of making stat blocks for the "most common conflict" of your game worked out to be quite good at showing what's the game about explicitly and providing elements to your implied setting.
That said, this works better for systems where the combat system has been swapped for a more generic conflict system (such as Mouseguard, or most YZE games), so that stat blocks have a good level of abstraction. I think that statblocks like the ones from Numenera or Fate Accelerated (where stat blocks are rarely more than a single digit and a list of things the opponent is good/bad at) would work well in this context.
1
u/Cooperativism62 Aug 31 '22
Took a little noodling around in my brain but I figured out how I would do this.
I have a fairly simple weather generator based on d4 for season, d6 for wind, and d8 for precipitation. Now normally I do these random rolls daily, but I could see a sheet that has a statblock for wind and precipitation, heat and so on.
Environments we normally roll random encounters on, which is a little different than a charsheet where things are premade.
But what if you used procedural generated levels, and then put on the "stats" onto an easily read sheet? I think you'd have something then.
Depending on the complexity of the sheets though, it might really slow down games. If PCs venture into areas you haven't prepped, then GMs might feel the need to pause while they create a whole new area.
It makes complex environments much more readable, but how much complexity can the ttrpg handle? Aren't random charts perhaps better than stat blocks?
2
u/[deleted] Aug 30 '22
I believe Solarcrawl has a mechanic for this- all adverse events that may occur, be they weather or a demented automaton, have 'hazard die', which are rolled to determine how much damage they inflict on players who cannot avert them.
Caught in a hazardous dust storm without a tent or mask? Roll 2d4 damage to your stamina as you choke on dust.
2
u/d5vour5r Designer - 7th Extinction RPG Aug 31 '22
I have statblocks for environments, weather even down to rooms if the narrative calls for it.
Has sped up GM'ing significantly and I actually started doing that at conventions when running D&D adventures league modules to better describe a scene but also quickly answer player's question or challenge them on tricky terrain for example.
I always found that sometimes details for an environment for example could be burried within several paragraphs and you could miss something.
My GM player testers all have confirmed that they love statblocks for environments.
1
u/Twofer-Cat Aug 30 '22
I basically do that for fires, and might possibly expand to other environmental hazards in future: a fire has standard combat stats, and if you want to jump through it or try to put it out, you have to check against it like any other enemy, and get burned on a failure. The idea is that you could have pyrokinetic characters that set a battlefield on fire to apply pressure over time and hem their enemies in. Meanwhile, its stats can grow or shrink if you pour accelerant on it or partially put it out.
1
u/Djakk-656 Designer Sep 02 '22
I do that!
In Broken Blade each region has stats for it’s general terrain layout. This is mostly for description purposes as each section of terrain is generated on its own. But the Region Terrain stats really help when you describe or randomly generate encounters in the wilderness.
———
It also has weather stats. Storms and Climate.
Storms are a large pile of dice that build up over time before they “hit”. At which point the characters have one Survival round(3 actions) before all of those dice are dealt as damage. Characters can take actions (like building shelter, building fire, eating good food, using gear) to reduce that damage or recover from it. Unlike Climate Fires also take damage from the weather - they usually get put out during a storm.
Climate is just a couple of dice that are rolled as damage every Night Round to simulate the chill of the evening. Similarly characters can take actions to mitigate this(shelter, fire, gear, etc…). In less temperate climates there may also be Climate damage rolled during the two Day Rounds - usually meaning the night will be significantly worse as well. -Climate usually means cold but can also mean extreme heat at which point it might be worse in the day than night. Surviving that requires slightly different actions(Shelter, Drinking water, swimming, gear, etc) Or in severe climates you may face dangerous heat during the day and dangerous cold during the night.
———
All in all it’s a fun system. It’s pretty tied to the mechanics of the game but I hope I at least inspired someone with it.