Showing posts with label Pendragon. Show all posts
Showing posts with label Pendragon. Show all posts

Wednesday, June 04, 2014

RPG Conversion Work

I have a newfound appreciation for even the worst of the d20 conversions from the heyday of the d20 Boom. You see, I've been working on converting part of one game into another game. For personal use - but I think other folks might get some benefit from it.

Let me explain a bit:

As I'm sure you know, I'm a huge fan of the Legend of the Five Rings RPG. I have at least one of every product published since first edition (with one frustrating exception). I love the system. I love the setting. I just plain love this game.

But there's one thing that's always been lacking for me: Any sense of the passage of time. This is a big deal because of the metaplot. The setting has several large overarching storylines which are running at any given time - and it's really not realistic for PCs to be at every single event that is part of this story.  At the same time, GMs don't want to Infodump on the players. Because infodumps are No Fun.

Not only that, but player characters are eternally young and vigorous. Right up until the point where they are cut down by a foe on the battlefield ...

This is glorious and all, but when you read the fiction, elderly samurai retire from active duty and serve as teachers. Characters do die of old age and natural causes. Admittedly, we see this more from Emperors than from characters who are on the same level as the PCs, but it does happen.

On the other hand, having your character gradually degenerate into unplayability due to advancing age is not going to be a ton of fun, either. Because we'd much rather focus on the Epic Glory Days of our characters.  So a way to introduce new characters to the mix is also important.

There's another game which I very much like.  It's called King Arthur Pendragon, and it has a feature that was 100% unique at the time it was introduced. Several features, really, but one that's relevant here.  It's called the "Winter Phase."

During the winter phase of the game, your character will age (and eventually die of old age or retire). To keep it from being a frustrating spiral of PC decay, however, KAP added a family.  Your character will, by the time he is too old to continue, have an heir ready to step up and become your new PC. Every year, your children will age - and some of them won't survive to adulthood.

It also has another effect on the players.  Suddenly the game isn't about your character, it's about your character's legacy.  It's something I think a lot of games could use.

If you're at all curious about it, I heartily suggest that you check out the current Bundle of Holding which will be Pendragon for the next day or two. If you miss the bundle, it's always available in PDF and print-on-demand via DriveThruRPG. And it's a phenomenal game.

It's something I very much wanted to add to my L5R game. So I decided to make it happen.

This file (PDF link) is the current draft of my project. And it's ... it's more difficult than I thought.  It is, by the way, not even close to finished, because that will require playtesting and more playtesting and tweaking and balancing.  But it's at a point where parts of it are written enough to share. Feel free to download it and check it out and tweak it and adjust it. Find out where it's broken (because I'm sure there are places where it is broken).

And re-download it periodically, as I'll be updating it somewhat regularly ...

But if you decide to do so, I have one request: Let me know what you think. Tell me what flaws you find. I need to know what doesn't work so I can fix it.

I'll (obviously) not be releasing this commercially, but that doesn't mean I don't want it to be as good as I can possibly make it ...

Wednesday, February 10, 2010

One-Shots Update

So ... one-shots. Remember last year, how I'd decided not to buy any new RPG books until I'd used my most recent purchase?

It's the New Year's Resolution I broke last year - and didn't renew this year.

But I did run a couple of one-shots. Well - one last year, and one earlier this year.

Last year's one-shot was FUDGE. I actually used The Deryni Adventure Game. I generated one PC per player and sent the characters out a few weeks in advance along with a description of the basics of the system.

Part of the reason I chose FUDGE is because FATE is a flavor of FUDGE, and the upcoming Dresden Files RPG is a FATE-based game. And one of my players is foaming at the mount with excitement. Since The Dresden Files Role-Playing Game was due by GenCon, I figured a quick FUDGE game would get him ready for FATE.

And, before anyone snarks about the game not being out yet, I suggest you grab your copy of this book, and read number 117. If you don't own it, yet, then go to IPR and buy it!

The game was ... okay. The players weren't as into it as I'd have liked, and my usual off-the-cuff GM-ing style didn't seem to work. I had fun, and (apparently) so did the players, but I was left feeling a bit unsatisfied. And I didn't get the enthusiastic vibe from the players that you can get after a good session. It showed a lot of potential - and I'd definitely be willing revisit the game for a sequel at some point - I deliberately left a few plot hooks dangling - but I suspect that, if the players were filling out a report card, it would have received a B-minus or C-plus grade.

For my second one-shot, I grabbed a game that I knew the players were more enthusiastic about - Cthulhutech. I made more characters than players, and I left them incomplete. Not "five hours of work later, I had a character" incomplete - those of you familiar with the game will know what I mean when I say, "I didn't spend the characters' cheats." I had an idea of where to go story-wise.

We had a blast. The game went well - I had a hint-dropping NPC available if needed (something I hadn't thought of - it was a player idea that was easy to insert into the game). And the Big Finish was fun.

My good friend Wade, who is one of the primary reasons I do these one-shots, wrote up his reaction to the game.

My next one-shot (yet to be scheduled) will be King Arthur Pendragon, a game I've wanted to play since the first edition came out - and a game from which I have frequently borrowed bits for use in other games. I'll have to write about that, sometime ...

Saturday, July 11, 2009

System: Player Expectations and Style of Play

Since I'm going to be talking about system and how it impacts games for a bit, I think that it would be good to start by defining system.

For role-playing, I define a system as follows:
System: A set of rules used to determine the success or failure of characters within a role-playing game.
There are other elements which nearly every system has, but they are all designed to support the core success/failure mechanism of the system. For example, most games have a character generation system of some sort.

The most common core mechanisms involve dice, and can be summed up in a single sentence - "Roll one die, add appropriate modifiers and compare to a target number." "Roll a number of dice. Count the number of those dice which equal or exceed a certain number."

Systems also provide reward systems. Most of the time, this takes the form of experience points which allow characters to change and grow.

Each system brings with it certain expectations, which can drastically color how players react to it.

Where do the expectations come from? A variety of sources.

The most important and influential piece of the player expectation puzzle is the game's reward system. In Dungeons & Dragons, defeating monsters1 and disarming traps give you experience points which are added to your total. At certain threshholds, you gain more abilities which make you more effective at defeating monsters and disarming traps. The system doesn't spell out rewards for outwitting NPC's or avoiding combat. This leads to a specific style of play.

In the Tribe 8 (and other Silhouette-system games), you gain experience for being involved with the game, for advancing the story, for staying in character, and for working as a team. Yes, you can get experience for defeating enemies, but you can potentially obtain more experience for a dramatic act of self-sacrifice than for that defeat.

In other games, survival is its own reward. Call of Cthulhu is probably the most infamous game in this respect.

Other games provide additional rewards - King Arthur Pendragon, with its Winter Phase allows players to build dynasties, not just characters.

While it's the major contributor, a game's reward system is not the only element which impacts a game's style of play. So what else influences player expectations?

Rules focus. In Ars Magica, for example, devotes more than two-thirds of the rules to the magic system. Not surprisingly, the game focuses on magic. In fact, the combat system is almost underdeveloped by comparison.

Skill Lists. Tales From The Floating Vagabond had a skill list which included, "Swing Nasty Pointy Thing with Panache." With a list like that players knew from the outset that the game didn't take itself too seriously. It's worth noting that the game (and a number of its supplements) are now available at Drive Thru RPG.

Interior Art. CthulhuTech is illustrated throughout, and there are a number of images that make me think, "I wanna be that guy."

Game Fiction. I'm not talking about the Dragonlance novels, here. Nearly every game includes one or more bits of introductory fiction. These are frequently incomplete and end with a cliffhanger of sorts before introducing the rules elements demonstrated by that fiction. More importantly, they give you an idea what the setting is.

So what about Universal Systems? That is: systems which don't tie to a specific setting or genre. Universal systems generally lack a specific rules focus, they have very diverse skill lists, and the interior art and game fiction are all over the map in terms of quality and flavor. GURPS, FUDGE, Silhouette, and d20 have all tried to be completely universal systems - how well do they succeed? I'll talk about universal systems next week.







1 Until fairly recently, "Defeating" always meant "killing." Now, if you can force them to retreat or flee, you get credit for defeating them.