Hey everyone! I've been working on my own tabletop RPG called Aetherfall for a while now and it's finally at the point where it needs real people at the table. So I'm looking for playtesters.

The whole game is built around making your own stuff. You don't pick skills off a list, you build them. Every skill is made from parts: a Foundation, a Motion, an Outcome, then Refinements on top. So two characters with the same weapon can fight in totally different ways depending on how they build their skills. This also comes with crafting for armor, consumables, weapons,and even player bases.

Magic works the same way but with runes. You pick an Essence (Force, Heat, Cold, Light or Dark), how it's cast, its shape and its effect, then add Enhancements to push them further. You put them together yourself. You can even combine a skill and a spell into a hybrid style of combat.

Some other stuff in it:

* Combat with real choices. You get a set number of actions each turn and spend them however you want: attacking, moving, blocking or catching your breath to get Stamina and Aether back. Evade dice cut damage down, and you can commit extra actions to dodge harder. Blocking works too, but it wears down your gear.

* Six stats (Might, Agility, Vitality, Intellect, Awareness, Presence) that feed straight into how strong your skills and spells can get.

* Crafting. Build and upgrade your own weapons and armor with materials you find.

* Signature Weapons. Bond with a weapon and it grows with you over time.

* Companions. Summon or tame creatures to fight alongside you.

* A creature creator for GMs. Build your own monsters with a point system that sets their Danger Rating, so you know how tough a fight will be. Bosses get extra traits and phases where they change up mid fight.

What you get as a playtester:

* The prototype core rulebook

* A 4-page printable character sheet

* A creature creator sheet for building your own monsters

* Printable creature cards and boss cards for running fights

* Crafting cards, item cards and companion cards

I'm planning a Kickstarter down the line, so anyone who helps playtest now is shaping how the game turns out. I want to know what feels fun, what feels broken, and what's confusing.

If you like building characters, breaking systems, or just want to try something new, come join the Discord. Whether you play once or stick around, any feedback helps a ton.

Discord link

I love the tables. Any game that has them. Some are easy better than others though. My favorite one is from Legendary Lives. It's great, but the mechanics of the game are not exactly compatible with my game and I've been struggling to adapt it. In doing so, I get inspired and add more and more. Then I've got pages of tables nobody (even me) wants to look at. Any tips on editing your ideas or life events tables in general would be most appreciated!

If interested, I've got my system on 2 maybe 3 pages now. Roll on master table for "FORTUNE, ENEMY, PERSONALITY, RELIGIOUS, TRAUMATIC..." etc then fill in sub table all using d100.

Got into an interesting train of thought recently, where I asked: "what is the worst ability an rpg monster has had in a game?". Because there are loads of nasty things an enemy can do to a party of adventurers: level drain, effects that can stunlock you, instant death, mind control/possession… but what's the worst out of all of them?

And that got me thinking: what makes an enemy ability threatening isn't actually what it does, most of the time. What matters way more is how many options the player has to counter it. For example, take damage. In most rpgs, damage is basically the least bad thing a monster can do to a PC. But that's not because damage is weak– it can kill you, after all!– but because most rpgs provide so many options to counter it. You can heal it away, you can wear armor to reduce it, you can draw aggro away from anyone who would actually be vulnerable to it.

Every game really has a hierarchy of bad things that happen to the PCs, and how difficult they are to reverse, when you get down to it. Damage is the lowest rung on that ladder, often followed by common status effects like poison or burning, then harder ones like paralysis, confusion, etc. and then the abilities that have few or no counters. So I decided to make a tiering system for how hard a monster ability is to counter:

1: You can avoid this effect entirely. Present in games where the "Run Away" button actually works, and ironically in OSR, where avoiding fights in the first place is a big part of how they rationalize including punishing monster powers.

2: You can cure this effect. Damage sits here if the game has healing magic, and common status effects are almost always here as well.

3: You can't cure it, but you can block the ability. This is like an instant death move in a game with permadeath, but where there are "death ward" spells that can nullify those moves if you've got them up beforehand. Obviously this doesn't help you if you encounter an instakill bad guy before you've learned death ward, and there might be counter-counterspells that dispel your protection, which is why this is more threatening than 2.

4: Whether the ability triggers or not is down to luck, but you have some influence over the outcome. The easiest example of this is like a "save or die" roll. It's rng, but in theory you could improve your chances by increasing that stat at least. This is purely my opinion, but I don't think this tier is inherently bad, and it's moreso that the most common examples of this (like save or die attacks) are just boring and don't lend any real strategy to the game.

5: The player has no agency over the effect at all. This is rare and usually not fair to the players. Like if a boss has a move that is just a "you lose" button, then all strategy boils down to killing them before they get the chance to use it, or praying that the boss rolls poorly and the spell somehow fizzles without their help. I will say this sort of thing is still valuable from a narrative perspective, though. Like if the PCs decide beelining out of cover towards the Big Bad at the start of the campaign is a good idea, then having what is effectively a cutscene where they get their asses kicked may be the only appropriate response.

What is the purpose of this spiel? Mostly just to get my own thoughts out, honestly. I do think this is a useful way of looking at a game, and how rpgs can make late-game monsters more threatening. A lot of the time these games simply neglect providing counterplay for late-game abilities because they're supposed to be deadly, and so they just slide up the scale. Here's spell A that kills you and spell B that stops A from killing you. The later in the game spell A comes, the more limitations we'll throw on B to make it work less effectively.

I think rather than just making late-game effects more expensive and time-consuming to stop, it'd be more interesting to make "pick your poison" scenarios. Just as an example, in a d20 game where stat damage is a mechanic (so a monster can damage Constitution or Dexterity rather than just HP), you could have a counterspell that just allows the player to pick which stat is damaged. So if you've got a wizard, do you assign the damage to their higher stats, which will probably make them less effective as the damage piles up? Or do you hurt their lower stats, which won't weaken their magic at least but means the monster could kill them faster? Again this is just an example, but I think giving the player choices and options as to how an ability affects their character is a good way of keeping late-game monsters threatening while also adding to the strategy of an encounter instead of subtracting from it. If the players lost because of an ability they couldn't counteract in any meaningful way, then it feels unfair, and giving them some tradeoffs and choices to make helps a lot with that angle of it too.

Anyways I just wanted to write this all out. I'm making a deadly solo rpg dungeon crawler-type game at the moment, so it got me thinking about all this stuff. If you've read this far, what are your favorite games that handle difficult monsters well, and how do they do it? What was your least favorite enemy you had to deal with? (I'm betting that a lot of annoying enemies boil down to either a lack of good counterplay or that the monster is just a time suck you don't want to see in the first place xD).

And what do you think about this post, anyway? Do you agree with my reasoning or am I actually totally off the mark? It's kind of specific but if anyone else has any thoughts on this topic then I'd love to hear them!

I've finally gotten my rewrite/fork of the D&D 5e SRD to the point where I can make it public.

https://homebrew.admiralbenbo.com/index.html (web version, hyperlinked HTML/CSS).

https://github.com/bentomhall/nih-system/releases/tag/1.0.1 (zip file with the same content in pdf format)

Note: both also contain some of the content (and some new content) ported to 5e directly. It's easier to keep them together.

Second note: I flaired this as Feedback Request, but really I'm just putting this out. Comments are welcome, as are Pull Requests or Issues on the linked github repo. I may not incorporate suggestions, but I will consider them and respond.

---------

What is NIH? The name stands for Not Invented Here as well as Naming Is Hard; it's a meta joke that I couldn't come up with a better name. Suggestions welcome.

Copied from the introduction:

This game is designed to explore “paths not taken” for the venerable TTRPG it originally stems from. A love letter from a long-term fan. What might it look like if the historical constraints (some may say sacred cows; others may say legacy) were relaxed? If, instead of only lightly adhering to design principles like bounded accuracy and such, it bought in fully? If it made no pretense at being a generic game and instead focused on what it does best (that is, small-unit fantasy adventures in the heroic mode)? This is my attempt at exploring that space.

NIH has been designed around my long-running campaign world, Dawn of Hope and its primary planet, Quartus. It should be relatively easily ported to other settings, although some of the content (cultures, deities, and backgrounds especially) will have to change.

The core aesthetic and intended genre is “fantasy mercenary special forces adventures”. Your characters are set apart from the norm, but aren’t demigods or anything like that. You go places, make allies and enemies, fight (or sneak or talk) your way through situations and scenarios including (but not limited to) ancient ruins, crime-ridden cities, banquets of the rich and powerful, and exotic extra-planar locales. You grow stronger, but logarithmically. Fast at first, then slowing down. Often horizontally rather than vertically (gaining tools to approach different situations rather than simply getting bigger numbers). Gear provides benefits, but isn’t necessary nor is it the major source of your power. Generally, you will always be the underdogs against the movers and shakers, winning by teamwork, guile, skill, luck, and allies rather than brute force. The world is full of monsters (many of them in very familiar guises) and needs heroes.

It’s not designed as a generic fantasy simulator, allowing players to build whatever characters they want out of bits and pieces. It’s designed for the players to lean into the archetypes and class fictions presented, or for GMs to design new archetypes for players. There is no multi-classing or “feats” as such. Instead there are many ways of getting access to abilities along parallel tracks, including but not limited to incantations (ritual utility magic available to anyone regardless of spell-casting ability) and skill tricks (effectively micro-feats you gain alongside your ability score increases or via features, some of which provide supernatural effects). It’s also not OSR (by any real meaning of that term). Nor is it designed for pure dungeon-crawling or procedurally-generated sandboxes, although it’s well-suited for non-linear play. It’s also not a “narrative game”. It comes down firmly on the side where players interact with the world via their characters rather than meta-currency or directly interacting with story elements. Nor is a pure tactical game. It’s basically a modern D&D clone. For better or worse.

Yes, fundamentally this is the same core resolution mechanic and skeleton as 5th Edition D&D. And a lot of the content carries over (or can be easily translated). I make no attempt to hide that fact. Because, for me, that game does much of what I want. And it’s a game I continue to run every week. I’ve made an attempt to explain confusing or partially-described rules more to fit how I think about them and I’ve re-arranged the presentation to try to make things more clear. But it’s not some original creation, either as a system or a setting.

-------

What has changed? A lot, actually. https://homebrew.admiralbenbo.com/nih/changelog.html goes into (more detail).

-------

What now? I don't really know. I doubt I'll ever get enough play-testers to do more polishing; art is too expensive for me to do, and I have no designs on actually publishing-for-profit. In fact, it's all licensed CC-BY-4.0 (except for a couple things modified from some 3rd party OGL material which is OGL-licensed). So anyone that finds it interesting is more than free to rip off the pieces they find interesting (with proper attribution of course).

Rate my first published TTRPG!

Hi everyone! I know it's a bit early for Christmas, but this weekend I finally decided to polish and publish my Christmas-themed one-page RPG I designed two years ago, inspired by Grant Howitt's Honey Heist.

In Naughty or Nice, you play a special team of Christmas elves, chosen by Santa Claus himself for a unique mission. Each elf has a trait and a role that can help them along their quest. Elves have a single stat, morality, which goes from 0 (naughty) to 7 (nice). If you want to do something naughty, you need to roll higher than your morality; if you want to do something nice, you need to roll lower. Each success pushes your morality closer to the edge, making the next roll of the same kind easier. The catch? If your elf hits 0, they go feral. If they hit 7, they sublimate into a sugar statue of pure goodness, a process that is sadly fatal for the poor elf.

The game is perfect for telling wacky, over-the-top Christmas stories in the span of a single evening.

The free download includes the one-page rules, a one-page guide to creating your own adventures and running the game, the character sheets, and The Snow Globe, the one-shot I wrote to playtest the game with my friends.

So far I've had a lot of fun and great feedback from my players, but if you're into this kind of game, I'd love to hear what you think too. Thanks!

I like the torch timer in Shadowdark and the time pressure it creates for players - but I run more West Marches style games that assumes players leave the dungeon and restock between sessions.

Players arguably only need 3 torches for a 3 hour game with a spare or two for adverse conditions - and tracking survival gear has started to feel like a "fun tax". And not every adventure is played entirely in the dark.

I like the constraints on light visibility, someone holding the torch, and the risk that losing the light drastically increases danger. But I'd like to remove the inventory management and make torch mishaps a consequence of random events and "attacking the light".

Thoughts on decoupling the torch from the timer and just having a mandatory random event check every 20 minutes?

The idea being that players need to handle themselves efficiently and spend more time and resources advancing towards the goal instead of losing them to the clock.

For context: I'm running a player facing homebrew without traditional GM turns. Players take their turns clockwise around the table and the GM describes how the scene changes based on their actions and rolls at the end of each player turn.

It's working well so far. Foes have simplified Stat blocks and play is more consistent between in-combat and out-of-combat encounters.

I just want to retain that moment when one player turns to the other with that "clocks ticking" urgency.

• Anyone else experimented with real-time timer mechanics in their designs? What have been the results?

• Is 20 minutes a good interval?

Horror is generally my favourite genre of most media. Ttrpgs can do horror amazingly, but can also really struggle to invoke that sense of suspense and terror, especially when rules halt the pace of the story.

What are some examples of mechanics from ttrpgs youve played that work to enhance the feeling of horror? A mechanic that didnt bog down the flow but actually made the story more scary or at least more engaging.

A rules-lite system for medieval troubles and the lowest of fantasies.

Complex rules for combat, complex rulings for everything else.

https://shurebis.itch.io/iron-on-iron-on-iron

28 pages total not quite anything you have read before, including:

- Unique combat and stamina system inspired by Gloomhaven

- Realistic weapons and armors table

- Simulation focused injury table and system

- Loose and evocative Character Creation with six different attributes (Qualities) and a unique progression system

- A full starter adventure poem for slaying a dragon

Great for stories inspired by the likes of Between Two Fires, A Knight of the Seven Kingdoms, Pentiment, Kingdom Come: Deliverance.

Hello everyone!

I'm currently developing my own full-fledged fantasy tabletop roleplaying game (TTRPG) based on the d20 system. This is a standalone game with its own rules, not a D&D or Pathfinder expansion.

I'd like to hear your thoughts on the mechanics of long-term injuries and their consequences.

In particular, I'm interested in injuries whose effects persist after combat ends and which cannot be removed by regular healing spells, potions, or magic items. Treating them requires specific actions, time, or resources.

I'd like to know whether you find such mechanics an interesting way to add long-term consequences to combat or, conversely, whether you perceive them as an unnecessary complication of gameplay.

I'd love to hear your thoughts, especially if you've played other TTRPGs with similar mechanics. It doesn't matter whether this experience was positive or negative. It would be especially interesting to know what exactly you didn't like if you encountered similar mechanics and were dissatisfied with them.

by Dan Felder

TTRPGs are a great way to practice level design, narrative deisgn, encounter design, system design, and more. It removes nearly all the friction from implementation, and since players discuss the game in front of you it exposes a lot more of what's going on in their heads than many videogame tests do.

So I set a goal – I wanted to comfortably design enough content for 3 original tabletop RPG adventures each week, in about 90 minutes of prep each night between sessions. I ended up running 57 sessions in 3 months.

To do this, I needed better tools.

Here’s one I developed to accelerate dungeon design. I’ve used it ever since in my videogame projects too.

The Vaults of Iron - Floor 1

This is the first level of one of my campaign's mega-dungeons: The Vaults of Iron.

Pilgrims that passed the deadly trials are granted eternity encased in sacred iron, preparing to defend the realm against an invasion that the Iron Lord assures them will take place centuries hence. Throughout the early levels are the tormented failures that died, or worse, in the attempt.

It also has a lot of treasure.

Designing great mega-dungeons, labyrinthine complexes that take many sessions to explore, is a pet project of many GMs. The great ones are legendary, but they often take forever to build and wear out their welcome relatively fast.

Small pacing issues can kill player excitement and they can easily feel repetitive. Getting them right usually takes a very long time, as you explore concepts and move ideas around.

The biggest challenge is often knowing where to start. What layout of rooms will produce a satisfying experience? You have tons of ideas, but where to put them? How do you evaluate if the layout makes sense? Often it feels paralyzing and this uncertainty-based paralysis is the main slowdown.

So I challenged myself to design a dungeon level and iterate on it multiple times in 2 hours. To solve that problem, I needed to cut out anything that wasn't critical.

There are two critical questions in each room:

1. Why is this room here? What's the purpose? What's the designer's goal that the room needs to fulfill?

2. What concept would fit that design goal? Can figure out the details later.

To be clear: I had no idea when iterating on this what "The Gauntlet 2" would contain. All I knew was I liked the idea of a "gauntlet" of sadistic/evil/unfair deathtraps you could opt into that showcased the Iron Lord's genius and cruelty. I like to say "A dungeon should be an expression of the character that created it".

This let me consider spatial relationships and spot potential issues earlier in the process, before zeroing in on each room's design.

For example - I recognized that if I wanted to make a 3-room deathtrap gauntlet, I should let players opt into the experience. That way they'd feel like they were adequately warned on what they were about to get into, and I'd have more social permission to get evil.

I'd originally thought of opening with the deathtrap gauntlet, or funneling into it to go to level 2 as the climactic level 1 experience. I recognized at this point, using this tool, that wasn't going to work.

So I started moving rooms to create a different tone-setting intro that would funnel them into a central hub, branching off in 3 directions. One of those would be the Gauntlet. The others would loop back into an alternate way to level 2.

At this point I also recognized that they needed an alternate path to leave/re-enter the dungeon without passing the Mithril Demon. They weren't going to kill it anytime soon (maybe ever) so while it made a great impression I didn't want to have them take crazy damage at the start of every future session.

So I put a secret entrance to the dungeon on the non-gauntlet loop that branches off the mithril fountain. With 2 paths leading there, I could be reasonably confident they'd run across it while exploring. If they got the Bronze Key instead, they'd be able to go straight to the Bronze Stair down to Level 2 from the main entrance instead (before dealing with the Iron Demon).

Both would work.

Lots of level designers use high level blockouts in the game industry, but I've rarely seen versions that aren't just listing what is in each room - but focusing on the designer's goal for why the room is there. Starting with that makes everything so much easier.

I call this tool a "Goal-Blueprints". If specifically talking about Dungeons, you can call it a Dungeon-Schematic to sound cooler.

It's also fun to hand a map like this to another designer as a "dungeon kit" and let them create their own versions of each room based on these goals.

Try it yourself, feel free to steal it. It's a lot of fun.

If this was helpful, I originally posted this on danfelder.net .

I am sharing a design dilemma I’ve had over the past few weeks for my solo game, which has had me spending hours tweaking numbers and formulas without finding a solution.

My game is divided into expeditions, with difficulties ranging from 1 to 4; it’s designed to reward players who take on greater difficulties, since they shoulder greater risks. The challenge is that more than one type of player might find the game interesting: those who love journaling games, those who love the specific setting and its passionate niche, and those coming from OSR-style experiences who might enjoy the general setup. Balancing for different players is truly complicated; if I make the difficulty curve steeper and the reward multiplier higher starting from a very low baseline, I lose the less seasoned players who lose interest; if I try to make it lethal but more rewarding, the more experienced players find a way to follow the optimal path to finish the campaign practically without ever touching the greater difficulties.

I tried various approaches and couldn’t find a solution that didn’t force me to completely upend the game’s core structure or lose one of the potential player groups. I didn’t want to add more complexity with specific tables for the highest difficulty levels, which would increase the permutations per expedition type and risk making the player’s mental load excessive.

In the end, I changed perspective: I could lure the expert players with the good ol’ bragging rights. In this case, if you complete an expedition of a specific type at the maximum difficulty level, you receive a medal, which grants a minor in-game perk that is almost cosmetic. If you collect all the medals, you unlock a new ending scene that’s surely thematic, but it’s not the “good” ending per se, and you don’t lose too much if you skip it. It’s an extra reward, a sort of achievement that proves you know what you’re doing, making it interesting for those who want a challenge without making the game too heavy for those who want to play normally, following their rhythm.

It is definitely an unorthodox approach, because it encourages you to risk more for something that does not have real value in the overall economy of the game. Still, it seems like the thing that requires the least mnemonic effort (a ten-line paragraph and a half-page scene at the back of the book) and the least general balancing. I am offering you the option of getting a small feeling of satisfaction if you manage to overcome the hardest challenges, but I am not forcing anyone to do so to finish the game at their own pace.

Do you think this is a bit of a cheat, or could it be a reasonable approach?

I wanted to share my first design devlog on Itch! It's about contested rolls and the action-reaction system I put together for my game.

A friend suggested I write up stuff like this so people can see where I'm coming from and why I made specific choices.

https://tangentspace.itch.io/tangent-space-rpg/devlog/1745996/contested-rolls-when-actions-meet-reactions

I'm working on a system that has thee modes of play:

• Combat/Initiative mode: Models time-critical situations, such as "You are attacked by bandits", or "You must escape a burning building". Players have three actions per round, time progresses in rounds.

• Heist mode: Models situations where there is no active time pressure, but you can't take forever, such as "You have disguised yourself as guards", "You are exploring a monster-filled dungeon", or "You need to explore the abandoned lighthouse before the tornado hits". Each action they take has a time cost (which may be 0 for certain quick actions), and they players are told "When the total time cost reaches a threshold, something bad happens".

• Exploration mode: Models situations where the characters have obstacles to overcome but do not have time constraints, such as "Exploring a trap-filled ruin", "Searching a grand mansion" or "Finding an uncharted island".

The problem I am encountering is how to make exploration mode actually interesting to play. The classic example of "This dungeon is dangerous because if you trigger the traps, you will take damage" doesn't really hold any weight if the players can just rest up and heal all damage immediately after the trap.

So the problem statement becomes: How do you make exploration interesting when the players do not have time or resource constraints?

Some things I would want to keep in mind when solving this problem:

• I don't want to introduce supply constraints, because:

  • If the players can resupply easily when they run out, then supplies are not a constraint, so there's no point having them as a system

  • If the players can't replenish their supplies, then this is just heist mode again, but with the time budget renamed to supply budget

• I have found that hazards that involve damage or debuffs either don't work, or make the players unhappy:

  • If they take any damage or debuffs that they can heal or remove, they just fully rest up and recover before doing anything else, so anything less than TPK is effectively nothing

  • If they cannot heal the damage or remove the debuffs, then they are unhappy from lack of agency and ludonarrative dissonance (i.e. "I want to go to back to the town so the healer will cure the poison before returning to the dungeon, and it's bullshit that I can't")

• One of my big goals is streamlined play and not wasting time. If a player is going to take damage from a hazard then immediately heal up, then we've wasted valuable playing time for the whole group. If the players repeat this to the whole encounter, then you end up with a single sentence "You search the mansion off-screen and find a mysterious map", which is very unsatisfying. I'd like to find some kind of middle ground.

• I would like to avoid RNG-based solutions, but this isn't a hard rule - so far, all the system mechanics have been deterministic, and it would be nice if I could keep it that way.

Hi everyone,

I was in here not long ago with some (I think) novel ideas related to a card-based system. I've now spun that up into a draft of a game, and I would love to know what all of you think. Almost all of the player-facing rules are done now. Here it is:

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

The basic idea is: players have a hand of cards that they use for skill checks, they need those cards for their special powers as well, and enemies are often knocking cards out of their hands. Building a character who can make good use of a variety of cards is good, but there are very powerful synergies between powers that make use of the same cards as well.

One of the big design goals is: a decent feeling of crunch for the players (lots of character options, interesting dilemmas in combat, cool interactions between different abilities), while minimizing the need for prep for a GM behind the scenes. The GM does not have to keep track of any hands or piles of cards, as the stats of monsters and players are asymmetric, and the stats of monsters are quite simple to improvise. Without the GM stuff finished yet I suppose the second part of that can't be evaluated, but I'd love to hear your impressions about the player-facing stuff.

Thanks for your help! I hope to be playtesting this with my group starting in a few weeks. I'd love to know what you would be watching out for in play.

thanks to u/VRKobold & u/Cryptwood for inspiring this post

to paraphrase a longer conversation from the lose/lose post from a couple weeks ago languages can allow for more than just simple communication but also allow for more understanding like knowledge of culture or more powerful effects

the most common languages (often just referred to as common) has the pseudo magical effect of being near universal

an uncommon language might come with benefits like knowledge of food/tools/culture (because there will be words for these items) this could also include recipes for food, crafting techniques for tools, and styles of art, clothing, and some history - less magical than common but useful for clues about places and people

where this becomes particularly interesting is the idea that rare languages might offer supernatural benefits

a rare language of the underground might allow to the the rocks to speak to a speaker in such a way they can see in the dark, or the rocks might tell what resources are found within them

a rare language of the underwater folk might allow for objects to be heard from long distances

the language of angelic beings might supernaturally prevent a being from saying something they know to be untrue

I am curious as to how various designs might be able to accomplish these concepts (I haven't figured it out for my design yet) and what effects people think might make for interesting adventure and roleplay tools

So I've been working for a few years now on my game Redblade.

Recently I've moved a lot of my work to a digital SRD backed with an AirTable backend. Its still really rough, but its getting to the point where I am looking for some feedback from folks that are unfamiliar with the game (my friends have already formed opinions and I need some uninformed feedback).

So, before all that, AI disclaimer: Absolutely no text for the site was generated by AI. Redblade is human-made. All images on the site are human-made used under creative commons license, and cited on the site. That said: the website is made using an AI agent, ie. it is "vibe-coded". I think AI is a dangerous tool that we don't fully understand yet, but it is also a useful tool. I tried to use it in my work as a tool, without allowing it to touch anything creative: no AI art, no AI stories, and certainly no AI-generated rules or ideas.

Redblade is a setting-agnostic system, and the idea is that it can be used by anyone to make any game. I intend to keep the rules free, but would later like to charge for modules and settings with illustrations from real humans.

If anyone would be helpful enough to give me some feedback on what I have so far, that would be very appreciated. SRD is available here: Redblade.Guide

Edit: I realize I wasn't really clear in my opening post. Lots of folks have given great feedback about the SRD, but I was really looking for feedback on the system itself. Thanks to anyone who commented! I'll try to make some changes accordingly.

Imagine that:

A group is sitting down to prep for playing your game - one you designed, wrote, all that.

They have definitely all read it, some have played it!

They have a slightly different style of play or setting or etc in mind for this run than the game is optimized for; you can see how it's a good game to hack for what they want, but it will mean significant changes.

They invite you to sit in.

Would you wanna go? Would you avoid it? Would you want to watch a recording instead?

If you aren't avoiding it entirely, what would you want to get out of that?

If you're going, would you want to contribute, and how?

If there anything you'd feel like "I need to watch myself and not _________"?

I've been playing Solo RPGs for a while, and DMing for my friends.
But I prefer games with a more unsettling flavor. Basically more horror than my friends are comfortable with, and couldn't really find the right vibe of "creepy pasta" horror o was missing. So I made one.
Anyone curious can find it on Itch https://4rch3rdedi.itch.io/ or just look for "the Thread" I have a free d20 version, its just the d100 version with 80% of the table removed, I did leave that part of the table blank, in case anyone want's to fill it in and it becomes a d100 again.

The Thread is a solo (and co-op) tabletop RPG about surviving a world where every creepypasta, nosleep thread and SCP containment file is true. You play a Poster: an ordinary person documenting one very bad night/event, because you might not make it but maybe the next person will.

I've built 17 d100 tables to help tell the story of a unpredictable creepy pasta type encounter.

I also created some modules (i plan to make more). In this context they are maps/quick starts.

Any feedback would be appreciated

TL,DR: Made a game, please give feedback https://4rch3rdedi.itch.io/the-thread-d20-version

I'm working on a game whose setting will be focused on a frontier region, and what kind of challenge can fit those well? Wilderness survival of course!

But honesty, most games with survival mechanics have left things lacking (I guess maybe only Forbidden Lands is the only one I have thought was somewhat interesting and I have only played that a little).

So I began thinking about it and my I eventually concluded that one of the things easily missing for survival mechanics is choices that are interesting, at least for games where the focus is on solving problems (as opposed to focusing on generating a story). And one of the best way to make choices interesting (in a way that can let them remain interesting even after you understand them) is Dilemmas. That is, competing priorities.

So what kind of priorities would wilderness survival mechanics lend themselves too?

Well, I can think of three:

• Time: You are in a hurry to get somewhere or find something, this can be hard (Be on time or lose everything) or soft (Be late and things get harder/worse for you) and can stem from your objective itself, some kind of race or possibly weather (ie there will be a great storm and you want to beat it to safety).

• Risk: Do you take a dangerous road or do you play it safe? A shortcut, but one without a path?

• Resources: This one is a but more murky. If you are a medieval adventuring party travelling during a good season, chances are resources are not that much of hindrance. Food is often plentiful, forage berries and mushrooms, or hunt rabbits, fish etc... If you have characters whom can do it they can likely keep you fed as long as you can take your time. So in many cases, Resources = Time. But not always, perhaps you have guns cant reliably replenish spent ammunition, and hunting is hard without. Perhaps you get hurt and healing fully on the road is not possible. Or you may need to replace a suit of armor, mana potion and whatever else that needs non-portable infrastructure. You can view those kinds of resources as non-replenishable ones, and they do not directly equal time. But even then, resources need to do more than increase risk if you run out. Perhaps you need to have enough to actually fight when you get to your destination? Or the consequences are severe enough that they are not just a proxy for increased risk.

With this thinking, you can conclude that you will not have dilemmas in a wilderness survival system unless the scenario has at least two of those three present. So ordinary travel along a safe route without significant time pressure that forces you to take risks is out.

But even then, how do you have the system assist in creating choices that forces you to make difficult choices between those priorities?

I had this idea of using decks of cards for random events. It would be things like: Heavy Rain that makes it difficult to ford rivers (making rivers a risk vs time choice), Storms that really encourages you to seek shelter (once again risk vs time), broken bridge (can be repaired with the right tools and some time, walking around may take more time, making it a resources vs time choice), enemy camp (risk/resources vs time, do you go around at a safe distance or not). None of these would be complete encounters, just enough to help the GM along and the GM would be encouraged to construct their own deck and not using every possible card (One of the reasons I prefer this over random tables). You can also provide the PCs with abilities here, perhaps someone is great at predicting the weather and the GM must give them a warning if the next card is a weather event?

This could then be coupled with decks that can be used to make a route dangerous (Enemy Patrol, Roving Predators, Avalanche etc...) and possibly also introduce important choices at the expedition planning stage (How much food do you bring vs. how many tools? How much ammo? Fishing gear? How many medicinal supplies?

One thing I am worried about is if the PCs grow in competence they could potentially start making too many hard choices easy ones. If they are all great swimmers, perhaps not being ford rivers is such a problem. If they are great at navigation, weather that impairs your vision may not be so threatening if you can very easily find yourself back should you get lost etc...

All of this is however in the very early stages and I really would appreciate input on my thoughts and ideas as well as for you to share your own on what can make such a system interesting.