Now that I've got the new way potencies work, in a general sense, I can return to NPC spceial abilities. I still don't want resources to manage on the NPC side. We've seen how well that worked. However, creating interesting opposition requires something that can do more than deal damage. No, this game isn't super-meaty in terms of combat, but still, you do want to mix up the violence now and again. Descriptions are great, and I intend to use them quite a bit, but since a player experiences a game in large part through how it affects his character sheet, I want to put in a few special abilities, similar to potencies, that NPCs can use to make them stand out as different from one another.
In the interest of keeping all the calculations on the player's side, however, I'm staying away from the idea of activating them on my own somehow though. I'm not sure if I'll keep the encounter pool, or how it'll work if I do, but I do know that's not going to be the way that I'm going to invoke their abilities.
So how to do it? The same way we're trying to do everything else in this game: margin of success/failure on the player's roll. Since an NPC's stats are the target numbers for attack and defense rolls made by the players, the special abiltiies can things that trigger when certain margins are hit.
For example, a brilliant swordsman NPC might have a riposte abilitiy that kicks off with a margin of 3. He has a defense of 5. A player takes a swing at him, but only comes up with 2 successes for the roll. That triggers the swordsman's riposte ability, which means he gets an automatic, free attack against the player. This happens whenever anyone misses him by 3.
Like potencies, these can be tiered as well, with greater effects triggered by greater margins. And there's nothing that says a player has to utterly fail in order for a special condition to kick off.
For example, a cultist has a special ability that allows him to call for aid from others in the crowd when he's in trouble. When a PC makes a successful attack with a margin of 3 or less, the cultist successfully calls another member to his side to stand against the PC.
Now, I thought Gifts as NPC stats was a good idea too, so this sounds nice in theory, but the only way to be sure is to test it. I'd like to say I'm confident, but the last idea worked out so poorly I'm instead going to say I'm cautiously optimistic.
Thursday, June 9, 2011
Monday, June 6, 2011
Potencies Redeux
With the idea of splitting your main pool into tinier ones and then rolling them separately, potencies need a rework. However, the new combat method does lend itself for a pretty easy conversion. Instead of allocating dice pre-roll to a potency, you allocate successes from your roll to potencies in order to activate them. In fact, this allows for more robust potencies that exist in tiers. For one success, you can get X benefit, but for two successes, you get Y, and for three you get Z.
That's all nice and vague, so let's slap some examples down on the page.
That's all nice and vague, so let's slap some examples down on the page.
- Flashing Blades - you can make an additional attack against a target in the same exchange. This action costs 3 successes. Upon activation, you can apply an attack you've already made a second time against the target. In effect, you deal damage two times from a single attack.
- Pain Rage - the pain of your injuries burns red, granting you furious strength. This action costs 2 successes. Upon activation, you may add any current damage you are suffering (in dice, not points) to the damage of an attack.
- Wild Aggression - you throw yourself on your opponent, heedless of danger to yourself. This action costs 1 success. Upon activation, you can apply an attack you've already made against the target. You may not defend or recover this exchange.
- Take It - you steel yourself to take a hit. This action costs 1 success per level; there is no limit to the number of successes you can give to this potency. For each level, you steel a single die by increasing the amount of damage required to knock it out of your pool. Thus it takes 2 points to knock out a Destiny die and 3 points to knock out a Hope die. You can only apply this potency once to a since die, but may apply it to multiple dice.
- Berserker - you throw yourself into a howling rage, allowing you to temporarily overcome your injuries. This action costs 1 success. Next exchange, you may roll all your dice, including the injured ones. However, you may not recover or defend in that exchange.
Thursday, June 2, 2011
The New Combat Procedure
In theory, combat already works the same way that non-combat checks do. In our playtest, however, the players never tried to do more than one thing at a time when making non-combat checks, so that similarity never appeared. However, once we got into combat, people were splitting their pools and rolling all over the place, which was exactly how it was supposed to work.
Fluidity was a problem though, so this is an attempt to make it a faster, simpler resolution system. Here's the new proposed combat procedure:
Fluidity was a problem though, so this is an attempt to make it a faster, simpler resolution system. Here's the new proposed combat procedure:
- Declare your actions
- Roll your Pool
- Apply modifiers for talents and trainings
- Sort out your successes
- Allocate your successes toward your declared actions
- Compare them to your target numbers
- Record the consequences based on margins of success and/or failure
Monday, May 30, 2011
The 10 Die Limit
One of the things all three playtesters wound up begging for in unison pretty quickly when we got into discussing what worked and didn't in our playtest was a cap on The Pool. 10 dice, they said. 10 dice was a great number. Don't mess with it. Take away from it for injury if you like; that's okay, but please, dear G-d please, no more. Between endangering dreams, seeing your dreams in actual harm, and acting according to your ideals, you could wind up with a mountain of dice. Mountains of dice are nice in theory, because everyone loves powerful characters, but in actual play mountains of dice suck. They're too much to manage, and the game becomes more about moving dice around than playng the game.
Please, Cliff, they begged, keep a hard cap of 10 dice for The Pool, and find another use for all that other stuff.
A rough rule I've picked up for evaluating playtest feedback is that if one person says something needs to change, but the other two seem not to care, I'll make a note about it but won't necessarily do anything right away. If two people seem to think there's something wrong, however, it needs to change. When all three agree there's a problem, it's a big problem.
Thus, without any further hint of consideration, there's now a 10 die limit on The Pool. You don't add to it. Nothing grants bonus dice. Maybe some things can grant bonus successes, meaning it's still possible to score more than 10 successes in a single roll, but you will never have more than 10 dice in your pool. Ever.
Please, Cliff, they begged, keep a hard cap of 10 dice for The Pool, and find another use for all that other stuff.
A rough rule I've picked up for evaluating playtest feedback is that if one person says something needs to change, but the other two seem not to care, I'll make a note about it but won't necessarily do anything right away. If two people seem to think there's something wrong, however, it needs to change. When all three agree there's a problem, it's a big problem.
Thus, without any further hint of consideration, there's now a 10 die limit on The Pool. You don't add to it. Nothing grants bonus dice. Maybe some things can grant bonus successes, meaning it's still possible to score more than 10 successes in a single roll, but you will never have more than 10 dice in your pool. Ever.
Thursday, May 26, 2011
Diceless NPCs, Done Better
In the last playtest report of Heroes of Destiny, I noted that the method by which I set up NPCs to not use dice wasn't effective. Upon reflection, I believe a large part of this is because while I did remove the physical act of rolling dice, I didn't substantively remove the need to manage resources enough from NPCs. In effect, I took out the time required to generate the resource, but the real work in running NPCs remained. Thus in play they weren't any easier to adjudicate.
So, in redesigning them, what I really need to do is take the work out of running the NPCs, not the dice. They're not the same thing. How to do that? Well, if my goal is to make combat roll just like non-combat actions, it means they need to work like any other obstacle. That is, NPCs aren't lists of stats, but target numbers that the PCs need to hit. An NPC's attack score is really just the TN the player needs to make on his defense roll, and his defense score is the difficulty for a PC's attack roll.
In theory, this removes the resource management problem from NPCs. Instead, the GM just needs to get the roll tallies from each player in turn, compare them to the target numbers that are the NPC's stats, and give back the information. Damage is based on how much the PC fails his defense roll.
What about special abilities? Well, I don't know yet. I'll get back to that. Not forgotten, but not for now. That's a little detailed given that there's a lot of basic system work that still needs rework.
So, in redesigning them, what I really need to do is take the work out of running the NPCs, not the dice. They're not the same thing. How to do that? Well, if my goal is to make combat roll just like non-combat actions, it means they need to work like any other obstacle. That is, NPCs aren't lists of stats, but target numbers that the PCs need to hit. An NPC's attack score is really just the TN the player needs to make on his defense roll, and his defense score is the difficulty for a PC's attack roll.
In theory, this removes the resource management problem from NPCs. Instead, the GM just needs to get the roll tallies from each player in turn, compare them to the target numbers that are the NPC's stats, and give back the information. Damage is based on how much the PC fails his defense roll.
What about special abilities? Well, I don't know yet. I'll get back to that. Not forgotten, but not for now. That's a little detailed given that there's a lot of basic system work that still needs rework.
Monday, May 23, 2011
Heroes of Destiny: Third Playtest
The third playtest of Heroes of Destiny was the first one that involved a multi-sessions campaign. Our very first test was a one shot run at the rules in a swashbuckling setting, and the second one was largely a character generation session. Now, we got to sit down with player-generated characters and have a full game session dedicated to gaming.
The rules are still rough, very rough, in places, but I'm happy to report that when this system works, it works.
The game picked up with our group of old west heroes on board a train headed out to Redemption Colorado from the east coast, each for reasons of his own. The three are brothers, and the ties of blood pull them together even though their pasts might otherwise drive them apart. One is a former law man, the other two of more shady occupations, all looking to set up life in the west through a shared stake in an area supposedly rich in gold.
Last game, one of the passengers went crazy, half ate two others, and then proceeded to fight the three of them. He lost to a small hail of gunfire that sent him tumbling off the roof of a train car, falling into the rushing darkness.
We picked up pretty much right there. The session that proceeded was very heavy on role playing and non-combat die resolution. The latter went amazingly smoothly. Despite the long hiatus between sessions, people picked up on the basic roll really quickly. That's not too surprising, as there's not a lot to it. Pick up some dice, roll them, and look for 5s. If that took a long time to figure out, we'd be neck deep in a whole other set of problems.
What was really exciting, however, was how talents and trainings affected play. Without any prompting from me, people would throw their dice, look at their sheet, and then alter their role playing so that they could leverage those bonuses that allowed them to manipulate the pool results. Characters really came to life early in the game, and while good players will always bring that kind of spark to their play (and this group had at least one such player), it happened early in the game, without much of a warm up period.
Even better still, I got to see first hand what it was like to watch a system fade into the background. We played for several hours without anyone stopping to puzzle something out. What questions there were became routine (mostly asking if a particular talent or training could apply to a situation/approach), which left the game wholly uninterrupted by the rules. We played, people occassionally tossed dice with complete confidence, read the results without any difficulty, and we proceeded with play.
One hang up we hit a little early was a question of cooperation, as in how to do it? The on the fly ruling I made was that the primary actor rolled his pool, but all participants could modify that roll with their talents, trainings, and gifts. However, if any participant wanted to include his Destiny dice, he could swap those out for any of the pool's Hope dice. That kept die rolling down while letting everyone participate. The group came up with the little flourish that you still rolled your own Destiny dice, which turned out to be a nice touch. This ruling went over big, and it's become part of the baseline rules from now on.
The play about erodiing Hope and burgeoning Destiny is also growing on people. One player lost almost all connection to his wife during play as he stood up and took over as lawman more and more throughout the session. He remarked at one point that it felt right, both in terms of his character and how it was coming off in play. His wife wanted him to put away the badge and live the simple life, but his ideals were calling him back to action, and he was consistently choosing them over her, and it was straining their relationship. He said there was a small story playing in his head about such things, even though we weren't playing them as part of the game, and that made the whole experience richer for him. I can't say that would happen to everyone, but it was really nice to hear about.
Then we closed in on the end of the adventure and hit combat. Combat hit back too. Even though they were supposed to sprout from a common root, combat was everything basic resolution wasn't: it was difficult, intrusive, slow, confusing, and ground play to a halt. No one was happy with it.
There were several large categories of problems when it came to combat:
The ways I try to make this happen follow in later posts.
The rules are still rough, very rough, in places, but I'm happy to report that when this system works, it works.
The game picked up with our group of old west heroes on board a train headed out to Redemption Colorado from the east coast, each for reasons of his own. The three are brothers, and the ties of blood pull them together even though their pasts might otherwise drive them apart. One is a former law man, the other two of more shady occupations, all looking to set up life in the west through a shared stake in an area supposedly rich in gold.
Last game, one of the passengers went crazy, half ate two others, and then proceeded to fight the three of them. He lost to a small hail of gunfire that sent him tumbling off the roof of a train car, falling into the rushing darkness.
We picked up pretty much right there. The session that proceeded was very heavy on role playing and non-combat die resolution. The latter went amazingly smoothly. Despite the long hiatus between sessions, people picked up on the basic roll really quickly. That's not too surprising, as there's not a lot to it. Pick up some dice, roll them, and look for 5s. If that took a long time to figure out, we'd be neck deep in a whole other set of problems.
What was really exciting, however, was how talents and trainings affected play. Without any prompting from me, people would throw their dice, look at their sheet, and then alter their role playing so that they could leverage those bonuses that allowed them to manipulate the pool results. Characters really came to life early in the game, and while good players will always bring that kind of spark to their play (and this group had at least one such player), it happened early in the game, without much of a warm up period.
Even better still, I got to see first hand what it was like to watch a system fade into the background. We played for several hours without anyone stopping to puzzle something out. What questions there were became routine (mostly asking if a particular talent or training could apply to a situation/approach), which left the game wholly uninterrupted by the rules. We played, people occassionally tossed dice with complete confidence, read the results without any difficulty, and we proceeded with play.
One hang up we hit a little early was a question of cooperation, as in how to do it? The on the fly ruling I made was that the primary actor rolled his pool, but all participants could modify that roll with their talents, trainings, and gifts. However, if any participant wanted to include his Destiny dice, he could swap those out for any of the pool's Hope dice. That kept die rolling down while letting everyone participate. The group came up with the little flourish that you still rolled your own Destiny dice, which turned out to be a nice touch. This ruling went over big, and it's become part of the baseline rules from now on.
The play about erodiing Hope and burgeoning Destiny is also growing on people. One player lost almost all connection to his wife during play as he stood up and took over as lawman more and more throughout the session. He remarked at one point that it felt right, both in terms of his character and how it was coming off in play. His wife wanted him to put away the badge and live the simple life, but his ideals were calling him back to action, and he was consistently choosing them over her, and it was straining their relationship. He said there was a small story playing in his head about such things, even though we weren't playing them as part of the game, and that made the whole experience richer for him. I can't say that would happen to everyone, but it was really nice to hear about.
Then we closed in on the end of the adventure and hit combat. Combat hit back too. Even though they were supposed to sprout from a common root, combat was everything basic resolution wasn't: it was difficult, intrusive, slow, confusing, and ground play to a halt. No one was happy with it.
There were several large categories of problems when it came to combat:
- Too Many Dice - Despite my assumption that the creation of multiple effort pools would make people die hungry, it turned out not to be the case, and all the various options that granted additional dice turned some people's pools into veritable seas. They had so many ways of drumming up more dice upon more dice that they literally had too many options and didn't know what to do with them all. This means that Dreams and Ideals need a complete overhaul, since playtesting showed they were important to play and populat as a concepts, but their mechanical implications need wholesale replacement.
- Hope Limits on Potencies - The idea that only the extraordinary can really let rip with potencies is a good one. Representing this by placing a semi-flexible cap on the amount of Hope you can put into a potency is not. It created confusion and the need to perform a calculation every time someone wanted to roll a potency.
- NPCs Are Hard - I'd designed NPCs to be diceless in order to speed and simplify their resolutions. I did this by listing the automatic successes they had toward several kinds of actions by way of assigning them gifts. Nice theory. In fact, it didn't work so well. The fact that NPCs have gifts means they still have resources that need management. Removing the dice meant that I didn't even have the physical tracking aid to use. I started using dice to help out halfway through, but it still was far more complicated than it was supposed to be.
- Damage - Damage is all kinds of screwed up. People either miss or commit grievous wounds on their opponents. Each time a player took a hit he went from fine to half dead. I wanted injuries to matter in this game, but this is too deadly for the kind of experience I'm trying to create. It needs to be scaled WAY back.
- Different Die Statuses - We've tried it several times now, and the whole fine/bloodied/bruised thing is just not working. Even though everyone gets how it works, people don't like them. The general consensus is that a die should be in play, or not. But having some that can do something when others can't, when they're otherwise identical, is unpopular. Wounding, and by extension recovery, needs new rules that simplify this.
The ways I try to make this happen follow in later posts.
Thursday, May 19, 2011
Shadowitz 2e: First Playtest
Our regular group hosted a guest recently, and so we took a break from the regular game to give Shadowitz 2e a trial run. I used a Die Hard like scenario, where the players would be inside a tower that got taken over by terrorists, initially separated from their weapons and with all their cyberware locked down. The idea was to have them sneak to the security station at the base of the tower, recover their gear and unlock their ware, and then have a series of running gun battles with terrorist groups as they tried to diffuse a bomb set to blow the top 15 floors off the building.
Instead, they jumped the first guys they saw regardless of the fact they had no weapons and little in the way of augmentation. The scenario ended before it began, and we instead settled in for a 90 minute fight that ended with a whole lot of dead hostages and an exploded building. But hey, the combat system got a hell of a workout.
The first thing I noticed was that wounding hurts a lot more than it used to. A lot more than it used to. Maybe too much. I'm not sure. In a single fight it really slapped the group around, but it was a situation that was stacked with near impossible odds (in the hopes they'd decide to do something other than overtly rush the bad guys) with no down time with which to recover from even stun injuries, so I'm not sure it's a fair test of how the penalties impact regular play.
That said, getting hit really messes you up now. You can't blithely ignore the flying lead anymore. Defensive actions are really a must. So much so that I'm thinking that dice put toward yin shouldn't be eaten up by an attack. While I prefer to shade things in favor of offense to move the game along, wounds are simply too crippling to nail someone with without providing a hearty defensive option.
Raising seems pretty cool, but again, with wounds locking down your pool, once you take a big hit, you're not raising anymore. I'm actually fine with that.
The new shot clock works just fine. I didn't expect any problems with it. In fact, the multi-track approach was very well received by any who had a comment about it.
Physical mages are powerful. I had adjusted the rules from what I posted here to make the magic rules a little more forgiving, but with the right suite of powers they are monsters. Again, not necessarily a bad thing. Unfortunately, since the group never unlocked their cyberware I can't fairly compare them to the samurai, who never got to cut loose. That's a comparison I'd really want to make before deciding what, if anything, needs to change with the physical mages.
With a flat target number of 4 and wound penalties changing way more dice into wound dice, I think my initial assessment of the knack list and pyramid is correct. Knacks need to be more specialized and more numerous. There's one other major revision I think I need to look at though, and that's the attempt to keep all pools at 10.
See, when the game judged the level of success based on the number of hits you rolled, having a massive pool just became cumbersome after a while, and once you exceeded a certain number of successes, you hit a point of rapidly diminishing returns in terms of how long it took you to sort your pool. For that reason, keeping the knack ratings capped at 10, and limiting them to 7 to start, was a good idea. But that's not the way the game works anymore.
Now, no matter the hits you roll, you only score a minimal success. If you want more, you have to raise, and to raise you have to drop dice fro your pool. Now, a massive score in a knack doesn't mean lots of sorting. You're looking for the task threshold and that's it. In fact, the new raise rules don't just mean that large pools aren't as cumbersome, but I think they require larger pools. If you want to really shine, you need spare dice you can throw away on raises. The existing knack pyramid needs a revision. While 7 dice to start is probably still okay, if lower powered than it used to be, I think there needs to be more slots for higher rating knacks, and maybe a higher ground floor. Knacks of 3 aren't very useful.
What surprised me most, however, was how many comments I got back immediately upon wrapping up the session about how people would readily return to this game to test it further. One big fight scene didn't give people opportunity to play with their demons, and that was something nearly everyone wanted to explore more. They saw a lot of potential in mucking about with questions of edge and punk and worldliness. I'm not sure when or if that'll happen, as this was a sort of design on a lark and one I wasn't planning on returning to, but hey, you never know.
Instead, they jumped the first guys they saw regardless of the fact they had no weapons and little in the way of augmentation. The scenario ended before it began, and we instead settled in for a 90 minute fight that ended with a whole lot of dead hostages and an exploded building. But hey, the combat system got a hell of a workout.
The first thing I noticed was that wounding hurts a lot more than it used to. A lot more than it used to. Maybe too much. I'm not sure. In a single fight it really slapped the group around, but it was a situation that was stacked with near impossible odds (in the hopes they'd decide to do something other than overtly rush the bad guys) with no down time with which to recover from even stun injuries, so I'm not sure it's a fair test of how the penalties impact regular play.
That said, getting hit really messes you up now. You can't blithely ignore the flying lead anymore. Defensive actions are really a must. So much so that I'm thinking that dice put toward yin shouldn't be eaten up by an attack. While I prefer to shade things in favor of offense to move the game along, wounds are simply too crippling to nail someone with without providing a hearty defensive option.
Raising seems pretty cool, but again, with wounds locking down your pool, once you take a big hit, you're not raising anymore. I'm actually fine with that.
The new shot clock works just fine. I didn't expect any problems with it. In fact, the multi-track approach was very well received by any who had a comment about it.
Physical mages are powerful. I had adjusted the rules from what I posted here to make the magic rules a little more forgiving, but with the right suite of powers they are monsters. Again, not necessarily a bad thing. Unfortunately, since the group never unlocked their cyberware I can't fairly compare them to the samurai, who never got to cut loose. That's a comparison I'd really want to make before deciding what, if anything, needs to change with the physical mages.
With a flat target number of 4 and wound penalties changing way more dice into wound dice, I think my initial assessment of the knack list and pyramid is correct. Knacks need to be more specialized and more numerous. There's one other major revision I think I need to look at though, and that's the attempt to keep all pools at 10.
See, when the game judged the level of success based on the number of hits you rolled, having a massive pool just became cumbersome after a while, and once you exceeded a certain number of successes, you hit a point of rapidly diminishing returns in terms of how long it took you to sort your pool. For that reason, keeping the knack ratings capped at 10, and limiting them to 7 to start, was a good idea. But that's not the way the game works anymore.
Now, no matter the hits you roll, you only score a minimal success. If you want more, you have to raise, and to raise you have to drop dice fro your pool. Now, a massive score in a knack doesn't mean lots of sorting. You're looking for the task threshold and that's it. In fact, the new raise rules don't just mean that large pools aren't as cumbersome, but I think they require larger pools. If you want to really shine, you need spare dice you can throw away on raises. The existing knack pyramid needs a revision. While 7 dice to start is probably still okay, if lower powered than it used to be, I think there needs to be more slots for higher rating knacks, and maybe a higher ground floor. Knacks of 3 aren't very useful.
What surprised me most, however, was how many comments I got back immediately upon wrapping up the session about how people would readily return to this game to test it further. One big fight scene didn't give people opportunity to play with their demons, and that was something nearly everyone wanted to explore more. They saw a lot of potential in mucking about with questions of edge and punk and worldliness. I'm not sure when or if that'll happen, as this was a sort of design on a lark and one I wasn't planning on returning to, but hey, you never know.
Subscribe to:
Posts (Atom)