A short time back in 2025, I had a bit of an epiphany around generic tabletop RPGs. On that I think, extends into a lot of SRD documents as well. Namely that we’re using them wrong a lot of the time and as a result, we’re not getting the best out of them. So let’s dive into how to use an SRD!

Background

To see how this all started, you need to head back and check out this article here.Up to speed? Okay. First I need to say that I conflated “SRD” (system reference document) and generic RPG in that article. My bad, I take that L. Broadly speaking, an SRD and generic RPG differ in scope and purpose, but they can have serious overlap. But what I’m focusing on today are SRDs like those for Black Flag Roleplaying, the Year Zero Engine, FATE Core, and 2d20 System. Well, specifically at those four because they give the spread for SRD types.

The Spectrum of SRDs

SRDs need to be approached slightly differently than generic RPGs depending on where they fall on the spectrum. Spectrum? Yeah. Spectrum. The thing with SRD documents is that they range in completeness from “the numbered filed off version of the game for sale” to “is functionally a generic tabletop RPG, a collection of mechanics you build your own game from.”

Highest at the developed end of the spectrum is the “cut down game”, and this is where you’ll find Black Flag Roleplaying by Kobold Press. This SRD is effectively a complete, playable game on its own. What makes it an SRD, and what makes other SRDs like it SRDs, is that its IP (intellectual properties) have been scrubbed out. And sometimes there’s also other cut content that the publisher has reserved for the full game. But, on it’s own, it’s game.

Next on the spectrum are games like Modiphius’ 2d20 SRD. It’s presented as the complete mechanics for a game, but without game “parts”, like character classes or archetypes. In the case of this SRD, the only hint you get about what it’s made for comes in the equipment section, which is decidedly modern. As a document, it’s leaning towards being a game as opposed to a generic system to make games.

Moving on comes the Year Zero Engine by Free League. YZE is a lightweight system that’s living on the line and leaning towards being a generic game. Why? It’s a catchall system. There’s the mechanics, tech stuff, vehicle stuff, magic stuff, and no specific details about characters or real setting implications. If it presented as a generic RPG, people would likely believe it.

Finally there’s FATE Core (and well, all the FATE games). These are generic RPGs that have SRDs that are the complete book. Is it an SRD? Yes. Is it also a generic RPG? Yes. And honestly, I’d make the argument that it’s actually a professionally printed and bound SRD. But the point here is that it’s complete, usable game, but one that is very much DIY.

How to Approach SRD

Using an SRD is slightly different from using a generic RPG, depending on the kind of SRD it is. So for example, if you’re using something like the Black Flag Roleplaying SRD, most of the work has been done for you. You have a reduced version of Tales of the Valiant, and while there’s some homebrew work to do, it’s mostly playable as is. The story is different if you’re using Year Zero Engine though; sure, you have the mechanics and a few examples of things like tech and spells, but you need to do a lot more heavy lifting in terms of homebrew because it’s just the skeleton of a game. Almost all the substance is coming from you. So approach SRDs with cautious enthusiasm. There’s a lot of people online who’ll make it sound like SRDs are the cure-all for the ailments of one game or another, but in reality, they’re simply one more tool in your tool box. And like all tools, and SRD will work best when it’s properly applied.

Getting the Most from an SRD

In order to maximize your returns from picking an SRD over a full and complete game, you need to do a few things. Foremost, you need to make sure the SRD you pick supports the kind of gameplay you want and the playstyle at the table. Next, make sure you have the time and energy to take on the needs of the SRD you’ve picked to make it work, remembering the points above about how SRDs exist on a spectrum.

Once you have your SRD picked, get familiar with it. Dig into it and see what’s there and what’s missing or needed. Then plan what you need to create. Archetypes, equipment, powers, spells, psionics, vehicles, monsters… the list goes on. And finally, you need to sync it all up with the setting you plan on using. THere’s nothing worse than doing a tonne of leg work creatively and then discovering it doesn’t pass the vibe check for the setting.

Next is communication. Communicate to your players what SRD you’re using so they can read up on it. Communicate any changes or mods you’ve made to them. And above all, Make sure they understand that just because an SRD comes from a certain game doesn’t mean you’re using it for the kind of game it was developed from. Building on the communications piece, this is where I recommend using a free website or service to collect all your information in one place for ease of accessibility. You’re using an SRD, so like when you use a generic RPG, you need to make your player facing materials available and easy to access.

Finally, listen to the player feedback in what’s working and what’s giving the trouble. This doesn’t automatically mean water it all down and make it easier. In a lot of cases, you might effectively be doing beta testing, so listen, take notes, and adjust as needed. And if there’s some core issue that seems to be a point of contention, explain why it is like it is so they can either understand how to use the mechanic better or give you better critical feedback.

Final Thoughts

SRDs are a great tool, but not all SRDs are made equally. Nor do all SRDs perform the same tasks and functions. Picking an SRD to use for your game is as careful a process as picking a generic system, and can involve as much work on your part as a generic system too. I love SRDs, and have used ones like Breathless and 24XX to create my own games. I’m working on some stuff with FATE and the Year Zero Engine. But it’s not always a plug and play situation, so know what you’re getting into.