This is still in the very early stages, but I thought I'd get it out and see what you think. It's a combat system for a squad-based tactical game. I'm trying to create a fast and strategic mechanic to mimic the actual firefight experience.

Players and Cards

A standard 52 card deck is used, with the cards in each suit ranking as usual from ace (high) down to two (low). There is no trump suit.

Each heart is worth one Success per pip (ie: the 4 of hearts is worth 4 Successes), face cards are worth 10 Successes each and the queen of spades is worth 13 Successes. The other cards have no value.

Object

The object is to avoid taking hearts, or in game terms, taking damage from opposing player's attacks. The confrontation is ended when one side of the conflict retreats or loses all participants.

Deal and Passing

Deal and play are clockwise. All the cards are divided evenly between the Players and NPCs involved in the combat. Any excess cards are turned right-side-up and included in the first trick. If there is a heart or the queen of spades in the excess cards it doesn't deal damage to the winner of that trick.

The Play of the Hand

Unlike standard Hearts, the first trick is played by all players simultaneously. Each player puts down their card of choice in front of them and all are revealed at once. For this initial round, cards are all taken at face value with no trump. Highest card takes the trick.

What I like about this is that the highest card wins so if someone wants to try to throw a heart in then it has to be low to be certain they wont just be throwing it away (by winning the trick).

Another difference in this version of Hearts is that hearts can be played on the first trick. If a heart is played on the first trick then any player can lead with a heart from then on. If no one plays a heart on the first trick then a player can only discard a heart if they don't have a card of the suit which was led, as usual. 

The remainder of the tricks are played like standard Hearts. The other players, in clockwise order, must play a card of the suit which was led if possible (ie: react to the situation). If they do not have a card of that suit, they may play any card (ie: react unexpectedly). The person who played the highest card of the suit led wins the trick and leads on the next trick.

Success and Failure

Each player takes damage for hearts the receive in the tricks which they win. A player will not receive damage from his own hearts or allied players hearts, only from hearts laid by the opposing team. Each heart scores one Success per pip (ie: the 4 of hearts is worth 4 Successes), and the queen of spades scores 13 Successes. Face cards are worth 10 Successes each.

Each Success represents one level of damage for the weapon that the opposing player is equipped with.

You cannot "shoot the moon" in this version of hearts.

Combat ends when one side of the conflict retreats or loses all participants.

How Player Actions in Hearts Translate to Character Actions

Taking Hearts = Taking Damage
Leading with a Heart = Making an attack & risking exposure for a counter-attack
Leading with a Low Heart = Blind fire / Suppressive fire (low accuracy, low chance of counter-attack)
Sloughing Hearts = Attack/Pointed shot (moderate accuracy)
Sloughing Heart Last = Aimed shot (high accuracy)

Taking Trick = Getting initiative
Yeilding Trick = Waiting

Sloughing Suit = Anticipating opponent
Slouging High Cards - Taking cover
Sloughing Queen = Critical Success

Taking Your Own Hearts = Miss
Taking Hearts From Teammates = Miss
Taking Your Own Queen = Critical failure
Taking the Queen from a Teammate = Friendly Fire

I haven't worked out exactly how really large fights will work and this system doesn't really lend itself to a 1 on 1 fight either. So I need to work those issues out. I also would like to incorporate special abilities that perhaps give bonuses, but I haven't worked that out either. (Like I said, this is still very rough).

I love the idea of using an established mechanism from a traditional game and twisting it to reflect something new...

...the roulette wheel in Fastlane...

...the poker-style mechanics for magic in Deadlands...

...the Jenga tower in Dread...

They each take something that non-roleplayers are familiar with, and use them as a doorway into the hobby. Personally I think that can only be a good thing.

This being said, I considered using Hearts as a game mechanism a while back. I abandoned it because the game is strategically complex in it's own right and I felt that it was overly complicating things when I tried to add new factors like character skills and special talents.

Rereading through your interpretation of a Hearts based combat system, I'd maybe allow certain special abilities to activate based on the cards played. If you played a spade this turn to may reduce any incoming damage by a number of pips equal to your skill. If you played a diamond, you may deal extra damage to someone equal to your skill level.

Then allow some really cool suit based abilities to kick in if you manage to win the trick while playing that suit.

The idea here is that the skills and abilities don't make a difference to the way the cards are played (no single player gains more cards than anyone else...because that gets really messy...trust me.), it only affects the way the round of hearts filters across to the game world.

And by the way, I'd consider including "Shooting the Moon", to allow for players who want to take incredible risks for the chance at ultimate glory. It all depends on the types of stories you're hoping to develop through this system.

Just some ideas...

V

What this is missing is opportunities for the game fiction to impact on the mechanics of the game.  For example, your game has "you played a high card - therefore you're taking cover" rather than "you're taking cover, you can play a high card".  What this can lead to in play is that the fiction - i.e. what's happening in the game, gets ignored or glossed over, in favour of focussing on the cards.  If what's happening in the fiction doesn't matter to how the cards play out, then players will ignore it.

An easy way to introduce this is with the "trumps" rule from Hearts.  Each hand, the players say what their squad, character, or whatever is doing, and the GM (if there is one) decides which suit is trumps based on that action.  Something like:

Laying ambush, sneaking, hiding: Spades (This interacts interestingly with the Queen of Spades)
Holing up, defending, retreating: Clubs
Gathering information, getting the lay of the land, taking the high ground: Diamonds
All out attack: Hearts

This skews the game heavily in favour of the players, if they coordinate right.  I think that's ok though.

What I like about your mechanic is how leading with hearts has a really visceral effect on the game.  In Hearts, leading hearts means there's going to be a lot of points won or lost, similar to a firefight, going in guns blazing can be a big win, or a big loss.

You'll want to work out some conventions on tabletalk (is it ok to announce what you've got in your hand?) and on who gets dealt into a hand.  I'd want just one or two hands for NPCs, with a hand representing a squad or a small group, but each player should for sure get their own hand.

Oh, and you should totally take damage from your own hearts.  Think of playing a heart not as "shooting" but as "initiating gunfire".  It might work out in your favour, or you might get shot up.

Vulpinoid wrote:

This being said, I considered using Hearts as a game mechanism a while back. I abandoned it because the game is strategically complex in it's own right and I felt that it was overly complicating things when I tried to add new factors like character skills and special talents.

Simon wrote:
What this is missing is opportunities for the game fiction to impact on the mechanics of the game.  For example, your game has "you played a high card - therefore you're taking cover" rather than "you're taking cover, you can play a high card".  What this can lead to in play is that the fiction - i.e. what's happening in the game, gets ignored or glossed over, in favour of focussing on the cards.  If what's happening in the fiction doesn't matter to how the cards play out, then players will ignore it.

Simon wrote:
An easy way to introduce this is with the "trumps" rule from Hearts.  Each hand, the players say what their squad, character, or whatever is doing, and the GM (if there is one) decides which suit is trumps based on that action.  Something like:

Laying ambush, sneaking, hiding: Spades (This interacts interestingly with the Queen of Spades)
Holing up, defending, retreating: Clubs
Gathering information, getting the lay of the land, taking the high ground: Diamonds
All out attack: Hearts

This skews the game heavily in favour of the players, if they coordinate right.  I think that's ok though.

Simon wrote:
What I like about your mechanic is how leading with hearts has a really visceral effect on the game.  In Hearts, leading hearts means there's going to be a lot of points won or lost, similar to a firefight, going in guns blazing can be a big win, or a big loss.

Simon wrote:
You'll want to work out some conventions on tabletalk (is it ok to announce what you've got in your hand?) and on who gets dealt into a hand.  I'd want just one or two hands for NPCs, with a hand representing a squad or a small group, but each player should for sure get their own hand.

This post on Vincent Baker's blog might be useful to you - he's talking about just this topic, i.e. how to maintain focus on the fiction with strongly procedural rules like the ones you're developing.

http://www.lumpley.com/comment.php?entry=438

don't worry if it doesn't make sense to you.  What he's basically saying is that you need there to be some point at which the mechanics referr to what's actually ocurring in the fiction, otherwise it stops mattering.

Simon wrote:
This post on Vincent Baker's blog might be useful to you - he's talking about just this topic, i.e. how to maintain focus on the fiction with strongly procedural rules like the ones you're developing.

http://www.lumpley.com/comment.php?entry=438

don't worry if it doesn't make sense to you.  What he's basically saying is that you need there to be some point at which the mechanics referr to what's actually ocurring in the fiction, otherwise it stops mattering.

Yeah, basically.  I think what Vincent's saying is that you need an interaction between mechanics and the fiction - so the mechanics both alter the fiction (e.g. when you "win" hearts you're being shot up), and the fiction alters the mechanics (e.g. what suit is trumps is determined by your character's actions).

mjbauer wrote: I should have the mechanics come from the player's descriptions of their actions and not the other way around. Otherwise the story gets lost to the mechanics and what I'm left with is a card game.

I should have the mechanics come from the player's descriptions of their actions and not the other way around.

Callan wrote:

mjbauer wrote:
I should have the mechanics come from the player's descriptions of their actions and not the other way around.

No, you shouldn't. It should be both ways around, in order to meet your goals (assuming I understand them)

Oh, Callan's making it sound way more complicated than it is.  It's stuff like in D&D (3.5) you get a +2 bonus to attack if you've got the higher ground, and you get a +2 bonus to attack if you charge, and you get +2 for having a certain feat and so on.  Some of the bonuses come from things on your character sheet, and some of the bonuses come from things your character's doing in the fiction.  So sometimes you're going to charge because you need the +2, sometimes you're going to take the higher ground because you need the +2, and sometimes you're going to look at your character sheet and work out how you can get another bonus.

What's important is that there's an element of "judgement".  Someone (either the GM or the whole group) is judging what is happening in the fiction and deciding if it qualifies for the rule/bonus, whatever.

I'm really trying to avoid and even disprove the idea that +2 for 'height advantage' works the same as getting +2 for a feat. I'm 98% sure it's a destructive notion. If I get complicated, it's like I'm getting complicated about how to fold and pack a parachute - I want to make sure it works for you all because the alternatives appear destructive to me.

Can you give me an example of how this works in other games? I'm having a hard time visualizing it.

This is really discouraging to me, even though it shouldn't be. In a way this system does exactly what I intended it to. But, finding out that "exactly what I want" is exactly wrong, is a bit disappointing.

My biggest complaint about combat in other games is that it takes too long. Overall, it takes too long. Each individual turn takes to long. Each roll, check stats, add bonuses, counter roll, check stats, add bonuses, compare, takes too much time. The feel of combat is lost. The adrenaline-filled step into the unknown is lost. The disorienting, loud, chaos is lost. It seems less like combat and more like a careful, deliberate chess match. All of the components of a fight are there, but the atmosphere is completely lost. To me, that is the biggest disconnect in roleplaying combat.

Every way I've tried to simplify my system has either failed or has made it too restrictive. The reason for trying this specific method out was to eliminate (or consolidate) variables. I think it worked. However, it sounds like in doing so I removed the interesting part of the game, the part that connects the fiction to the mechanics and vice versa.

My biggest worry is coming up with a seemingly good system and later finding out that there is a way to combine or twist the rules to give an unfair advantage. Then all the options that have been carefully included become worthless because any other option besides THAT ONE is just a decision to handicap yourself.

I really need to get some of these ideas out of my head and off of forums and just try them out. Too much talk, not enough test.

Well, is it wrong? I said 'Assuming I understand your goals'. I might not, or you might not have even set certain goals in concrete yet. You might want to test, not so much to test if something works, but to test what your goals are. Bringing in the imaginative factor (and to what extent) is simply one component in design you could use. You might not want to use it. Or you might. Wherever your creative urge takes you.

I would recommend buying and playing the card game 'Lunch Money'. It would be interesting to compare play with what your aiming for in your post. Several years back I tried using it as the combat system for dungeon run with my partner, with a few tweaks. In that case though, it felt like several disconnected games of lunch money (which had been watered down with the tweaks) with some narration of tunnels and such in between. There was no overall game each one tied into, so it felt like just playing it over and over when typically one game of it is satisfying. They didn't blend into one bigger game just because there was a bit of narration between them. So it's funny what you think is going to happen but yeah, testing shows otherwise.

Though, with a bit of spiteful humour, perhaps that's why combat is slow and boring as you put it, in many RPG's? So people aren't actually satisfied and stop after the first combat? Heck, come to think of it, world of warcraft works that way too.

I hope I didn't put you off playing lunch money, I really think it's a good idea, but also thought my playtest account might help somehow. I agree with doing more testing - test the hearts game! Good luck!