Around and Around

There was a lot of traffic regarding my last post about incorporating playing cards as a game mechanic.  I didn't think it would have generated that much interest, so I was a bit surprised when I saw this.  It's definitely a mechanic I'll continue to dabble with here and there when I have time, and there's even a setting that would fit in very nicely to accommodate the unique system.

Other than that, I've been doing more system work and writing for the setting.  The setting is post-apocalypse science fantasy, set roughly 100 years after a planetary disaster.  Magic has been wiped out, but traces of it can be found here and there.  Survivors have started rebuilding, and search for forgotten technology.  Humans, robots, and a couple of new species are the norm for the game, along with swords and the occasional sidearm.  I plan on giving some more details about the setting in upcoming posts, so be on the lookout!

Regarding mechanics, I've been toying around with the idea of further simplifying the dice pool.  Here's the proposal:
Pools of d6, where the numbers have the following values -
1-3 Hit
4 Null
5-6 Block

When attacking, your objective is to score Hits, and when defending, you want Blocks.  Blocks remove Hits in opposed rolls, and leftover Hits are added to a weapon's damage rating to determine any damage.  As of right now, I included more Hits than Blocks to speed up combat; less chance of stalemates and/or no damage.  Damage can be reduced by wearing armor, so it won't necessarily be "deadly".  I figured that I would simplify the rolls for success, while allowing more creative range with weapons and armor.

I'm looking to play test this new mechanic with my group soon, but as always, finding the time is key.  Once I've seen how it works in play, I can determine if it's worth making it a permanent change, or to remove it altogether.  As usual, sound off and let me know what you think!

Midnight Rambler

I'm always open to new systems, and what they bring to the table (pun intended).  New mechanics are very interesting to me, whether they are heavy crunch, or narrative focused.  I do admit that I'm partial to "old school" when it comes to mechanics; I'm very much a product of early TSR, so sometimes the newer narrative-based systems feel "off" to me.  Still, I endeavor to learn as much as I can, and see what's out there.

One particular mechanic that I've been interested in is playing cards.  There's a whole list of games that utilize playing cards in some fashion or another, so I won't bore you with the details.  The thing that draws me to cards as a mechanic is the potential depth.  Suits, color, face cards, jokers, discard pile, draw, hands, and number value can all be used in a game (or not).  It's possible to use just the numerical value of the cards, but that would be such a waste.

I've dabbled with using a playing card system in the past, but never committed to it.  It just didn't seem like the right path at the time, although I can't tell you why nowadays.  Maybe because it was different, or not the comfortable route.  Say what you want, but familiarity is a selling point, and a big one at that.

Now I'm starting to come back around to cards.  I have some basic ideas so far, nothing too mind blowing.  Ace(1) through 10, face cards count as special abilities, Jokers are GM devices, that sort of thing.  I was considering using a player's Hand Size as their stamina/health, which can be increased through experience.  A character takes damage, and their hand size is temporarily reduced. 

Players would play a card from their hand to beat a TN set by the GM.  If the Suit matches the skill being played, they get to play another card from their hand.  Players also have the option to play from the top of the deck, but that can hold some potential consequence.  Not sure about the discard pile, and how that would come into play.

Another idea is that a player starts off with a set number of cards in their deck, and they can buy cards with experience.  You would only be able to buy a rank higher than your current rank in a suit, so no skipping  over to the higher number cards.  Face cards would activate some kind of special ability that was purchased, such as a second attack, or a distraction that gives an enemy a negative modifier.

One thing I'm struggling with is target numbers (TN).  I'm either going with an approximation of a d10, or a d13; face cards either cap out at 10, or increase in value up to 13.  Since I haven't made up my mind, I'm not sure what a good range for easy, average, and hard difficulties would be for players.

So, whatcha think?  Good idea, bad idea, or indifferent to the whole thing?

Moon Is Up

I figured that if there's a Super Blue Blood Moon Lunar Eclipse, then there's no reason I can't post a short entry. ;)

This is more of a, "get in the habit of posting" post than anything.  As you can tell from my anemic post count, I'm not used to posting a lot on social media.  I don't have a Facebook account, or Twitter, and I read more than post on G+.  I've only recently discovered Reddit, which is sad, but true.  I could go on, but I think you get the point.

So no real RPG update at this time, just me trying to be more consistent.  Hi!

Dancing with Mr. D (Part II)

I've received some feedback from a few of you, requesting more information about the core system I've been working on.  I appreciate the feedback, and am more than happy to oblige!  I've separated this into two parts; the original core mechanic, and the revised core mechanic.  Please read on for more detail, and ask questions.

Original Core Mechanic
System uses pools of six-sided dice.  The numeric value of a d6 holds a different value, listed below:
1 - Miss
2 - 2 Misses
3 & 4 - Null
5 - Hit
6 - 2 Hits

Hits determine success in a die roll.  The greater number of Hits, the greater the success.  A player must roll a minimum of one Hit to succeed in a task.
Misses remove dice in an opposing pool, increasing the chance for success.  Dice are removed on a die-for-die basis, so a 2 (2 Misses) cannot remove two single Hits (5, 5).  A single Miss (1) can reduce a 2 Hit (6) to a single Hit (5).
Nulls do not contribute directly to a player's dice roll, but may activate a special ability.

Dice pools cannot exceed a total of 10.

The player is Active when acting on their initiative turn, while all other players are considered Reactive.  The Active player can take an action on their turn, such as using a Skill, move, and so on.  When engaging in combat, the Active player acts first against their designated opponent.  As a result they remove dice first.

The Active player must score at least one Hit to succeed in their action.  A result of Nulls or Misses does not constitute success.

The Active and Reactive players determine their actions and roll the appropriate number of dice.  The Active player may then use a Miss die to remove a die from the Reactive player’s pool.  Only one die may be removed at a time.  Once the Active player has removed dice or passed, play passes to the Reactive player, and they may then use a Miss die to remove a die from the Active player’s pool. 

Dice removal continues until either players pass, or no more dice are left to remove.

Revised Core Mechanic

System uses pools of six-sided dice.  The numeric value of a d6 holds a different value, listed below:
1 - Hit
2 - 2 Hits
3 - 3 Hits
4 - Null
5 - Miss

6 - 2 Misses

Hits are utilized the same way.
Misses remove ONLY Hits in an opposing pool.
Nulls are the same.

Dice removal is handled a bit differently.  Instead of the back-and-forth style gameplay, the Active player removes all dice at once.  Play then goes to the Reactive player, who then uses their Misses to remove all dice at once from their opponent.

FAQ
This is a VERY basic outline of the mechanic.  I haven't included special abilities, skill use, powers, and so on.  Why?  Well, because that would be exhaustive.  I don't think a blog post could hold a book.
This is also a work in progress.  Rules are subject to change (and already have!)

Why uses Misses?  Misses are just like Hits, and the numbers come out to be the same.
I've heard this a good number of times.  Misses are important because of the potential of Critical Success.  Normally a player must score at least 1 Hit to succeed in a task.  If the opposing pool is reduced to zero dice, then the player succeeds in their task, no matter the die type left.
There's also the potential for re-rolls for skills, but that's for another post.

What are you trying to accomplish with this mechanic?
I had this idea of combining the "To Hit" process with damage, so everything is done at once.  There are plenty of games out there like that, but I wanted to make the dice actually mean something in the game.  The number of dice in a pool expresses how skilled you are, how difficult a task is, how strong you are, and so on.  Plain numbers do the same in other systems, but I wanted to express everything with dice.

How did it play test?
Playtesting went fairly well, with players picking up on the mechanic easily.  Players did mention that combat could be slow, with the dice removal taking up the most time.  I realized that I needed to speed things up, so I made the revision.  I've tested it a couple of times, and it's made a big difference.

What type of setting will you be using?
I have a few settings in mind, which I plan on releasing (eventually!).  Right now I'm focusing on a Post-post-apocalyptic science-fantasy western.  Say that five times fast!

Hopefully this sheds a little more light on things, and I plan on discussing more of the system as time goes on.  Feel free to fire back in the comments.

Sittin' On A Fence

The past few months has brought some changes to my core mechanic.  This has forced me to take a hard look at the system as a whole, and re-evaluate my work thus far.  In effect, it was time to, "Kill my darlings."  This is never an easy task, especially if you've hitched your wagon to a particularly sweet mechanic, which you're convinced is The Greatest Thing Ever (Monte Cook be damned!).

So what brought about this change?  Basically, speed.  There's a bit of back-and-forth for resolution, which slows the game down quite a bit.  It's a neat concept, but doesn't belong in a game where people roll dice often.  As badly as I wanted to keep this mechanic, I couldn't fool myself any longer; it was time to do some slashing, and speed things up.

Instead of back-and-forth die removal, I decided to go with a sweeping resolution.  The player removes an opponent's dice, then the opponent gets to remove their dice.  A simple enough solution that nets results in a fairly quick manner.  Although this mechanic did improve speed, it added new wrinkles to the core mechanic as well.

I had to re-calculate the value of the dice, and how often successes should occur.  Before any changes were made, the amount of Hits equaled the amount of Misses that could be rolled on a die.  I increased this number slightly, but I had to make yet another change to do so.  Once again, I had to cut a favorite of mine, or at least, trim it down.

Strengths and Weaknesses had to be tweaked into something a bit different.  I had to separate them into distinct categories, and redefine their meanings.  They would no longer be two sides of a coin, but separate abilities that can be purchased.  I'm still playing around with them, so it's not completely written in stone.

As you can see, one change can make sweeping revisions in a core mechanic.  I found it necessary to make the game move faster, and ultimately, more enjoyable.  Next up is play testing the new revision, to determine how deeply it effects the system.  I have a feeling that it may have inadvertently made the game more deadly, so I'm interested in seeing the results.

Time Waits for No One

I love Autumn.  There's a crispness in the air that feels energetic to me.  I can't really comment on the change of colors, because where I live, it's not as glorious.  Everything turns brown, and that's about it.  Still, something about Autumn invigorates me.

Now that we have that brief interlude out of the way, what else have I been up to?

I've been reviewing my rules for Vehicles, and how they are incorporated into the rules.  I wanted to avoid too much complexity, so I decided to treat vehicles like characters; same abilities, similar skills, and same dice pools.  The same amount of build points can be used to build a vehicle, but the scale would be different.
Speaking of scale, I came up with a simple mechanic to differentiate between vehicle scale and damage/armor.  Vehicles range is size from Small, Medium, Large, and Gigantic.  As an example, a Small Vehicle would be a motorcycle, or a car; a Large Vehicle would be a space cruiser, or a battleship.  A Vehicle that is a size larger than an opposing Vehicle will double the amount of damage and armor; this doubling occurs with each size category.
As an example, a single manned fighter(Small) faces off against a space cruiser (Large).  The space cruiser's damage and armor are x4 against the smaller craft.
Although this may seem like a nearly impossible task to damage a larger vessel (it should!), a pilot's skill and weapon loadout can make a difference.  There are also some game mechanics that can swing in a character's favor, but more on that at a later time.  ;)

Another consideration was Vehicle Movement.  How fast does a motorcycle go?  What's the move difference between an F-14 and the Space Shuttle?  How does movement of a Vehicle translate to Character Movement?

I took a page out of FATE, and decided not to go into finite detail.  Movement and Range is broken down in increments; Close, Short, Medium, and Long.  Instead of wracking my brain trying to come up with an algorithm that best divides range into different scales, I deferred to a less time-consuming alternative.  Movement occurs at the speed of plot.  A character shouldn't move as fast as a Corvette, unless the setting allows for such incredible feats.  Chases can be resolved with a skill roll and appropriate modifiers.  I'm a big fan of keeping it simple, with the option for more depth.

That's it for now.  Please comment below, and let me know what you think!  I'm also open to any questions you may have, so feel free to ask away.

Hang Fire

It's been one year since I've started this blog.

Boy, that went by quick.  :(

Companies usually give an annual update on their progress.  It usually includes what was accomplished, what goals were and were not met, and plans for the future.  I'd like to celebrate this occasion with the same kind of update, and give it a spiffy name, too.  In honor of the title of this auspicious Blog, I welcome you to the first ever Dumpster Fire!

The mechanic I envisioned grew from a very basic concept, to something a little more concrete.  It was going to be a D6 system, but utilized in a different way.  The basic mechanic was developed, tested, updated, and tested again.  All of this was done before I even had any type of stats, or character development.  It was just the mechanic, and nothing else.

Once that was fine-tuned, I quickly moved to stats.  I wanted to keep it as simple and clean as possible, so I decided upon a three stat system.  I also wanted to keep the skills light, so I took my time and came up with 10 skills.  Of course, this led to an issue of "sameness" when it came to character creation.  A simple solution was the creation of specialized skills, called Focused skills.  The skill would play off of the parent, or Broad skill.

Another step was to create stats that would be derived from a combination of the main three abilities.  These derived stats would focus on health, speed, and willpower.  There would be no "dump stats", as each one would have value in determining the derived stat.

As I continued developing the system, I soon realized that it was growing to be a little more complex than originally intended.  I knew that this was a possibility and rolled with it; I didn't want to set hard limits while creating, and determined that I would save that for later on.  Still, the system I had in mind began to change with each pass.

Once I had a skeleton of a system down, I began play testing with my local group.  I received a lot of good feedback, and they weren't afraid to tell me straight what worked, and what didn't.  I looked for trends, and cast a critical eye upon the mechanics.  There were some additions here and there, and I created a new mechanic that incorporated more options with dice pools.  This was a key element, since I really liked the idea of dice actually meaning something.  It wasn't about target numbers, or the number of dice you get to roll; it was about how the dice rolled, and the values having a deeper meaning than just a one or a six.

I increased the play testing to a second group, and fine tuned the system.  I added options for spells, called Powers, and included vehicles as well.  The easiest way to handle vehicles was to stat them much like characters.  They would have the same stats, but their meaning would be different; hull size, automated systems, AI, etc.  The main difference would be size, which would increase the armor and damage of a vehicle.  It was simple, but effective.

The system was coming along great, and I was very pleased with what I had so far.  I even had an idea for a setting that was bumping around my head.  I had a very clear picture in my head what the cover would look like, down to the facial expressions of the three characters and their stances.  All in all, I was pretty happy with the progress.

Of course, all of that came to a grinding halt.

I hit a brick wall.  It was a combination of a lot of different things; lack of motivation, confidence, and just Life in general.  It was a mish-mash of crap that's pretty stupid in the grand scheme of things, but it was enough to keep me from working on my little project.  I wasn't going to give up, but I really wasn't doing anything, either.  So time passed, and I felt guilty each day.

It took a friend of mine to snap me out of my haze, and it was a simple thing, at that.  He asked how my game was coming along.  Just a simple question, and I kind of snapped out of my funk.  It was most likely because I didn't have an answer for him.  I went back to my notes, looked over what I had, and the gears started turning again.

So here are the Cliffs Notes:

• I'm a little behind on development, but still have a decent sized completed
• Play testing continues, and the system has been streamlined
• Setting is being developed, with lots more to do
• Don't have a release date in mind, because I'm not a project manager, and can't really work with Gantt charts or Project
• Lots of stuff compiled on Google Drive, need to start moving it to a different format for eventual layout
• Started taking down artist names for eventual contact, even though I have zero dollars
• Started researching layout programs, and realized quickly that I either have to spend time learning a new skill, or hire someone
• Kickstarter is number 567 on my list, and I'm only on 6

Hope you enjoyed the wall of text.  Come back again, and I promise to be more succinct.

Oh No, Not You Again

Ok, boys and girls, it's Poll Time!

For those of you not in the know, my game system began as a generic RPG; no setting, just the mechanics.  This was a departure from the norm for me, as I'm usually the one pushing story and fluff over the crunchy bits.  The more I developed, the more I realized that I had unconsciously pushed setting to the side.  I started taking notes on potential settings that I would like to develop, and continued on.

Fast-forward to today, and after several play tests and tweaking, the system looks pretty solid.  Not every aspect has been polished, but that will come with more play tests.  The Powers section needs a lot of work, and Vehicles needs to be put through the grinder, but I'm pretty happy with the results so far.

Now I come to you, dear readers.

I have several settings that are in the works, but it's time for me to make a decision.  I would like to package a setting with the release of the system, but I can't pick which one.  I'm on the carousel of non-development, trying to choose which one to focus on.  I do plan on releasing each one (eventually), but I need to pick one to focus my efforts on.  It's not a matter of which has more material, or which one I like better; how does one pick their favorite child, after all?

This is your chance to actually make a difference in the development of this game.  You get the chance to vote on what tickles your fancy.  Below are the choices, so make your voice heard in the comments!  The more eyes on this, the better, so spread the word as much as you can.  I'll leave this up for the remainder of the month, and then tally up the results.

I eagerly await your responses.  :)

Grey - Hard-boiled crime, neo-noire. Gangs, crime syndicates, dirty cops, and crooked politicians run this town, but there are some decent folks, too. Street knights, downtrodden P.I.'s, and hell, even the occasional street thug try to do the right thing. In this town, nothing is black and white.

Nomad Star - Post-solar system catastrophe, science fantasy. The rogue planet Tiamat collided with the second planet of the Nomad system, shifting the orbits of the remaining two. 1,000 years later, Tiamat has begun to reform, sending an invading force of monsters to both worlds. Both worlds must be saved, not only from the impending environmental change, but the invading force of terrifying creatures. Swords, sorcery, and technology are your weapons.

Purgatory - Judgement Day came and went, and no one cares. The Heavenly Host and the Infernal Horde used the earth as their battlefield, leaving ruin in their wake. In the wake of the Apocalypse, humanity struggles on. The population has been drastically reduced to almost nothing, and the survivors have renamed the planet to Purgatory. The living (and un-living) find shelter in massive cities, with towering walls to prevent gibbering horrors from overrunning the citizens. These people have a Karmic debt to pay off, if they wish to travel beyond this wasted realm of pain and anguish. Death isn’t always a guarantee, and sometimes, not even undeath.

JadeLamp - Victorian Age of Gothic horror, set in China. New technology is slowly being introduced, but there are still things that go bump in the night. Sometimes, the old ways of dealing with such threats are best. Wuxia, ancient magic, and a little technological ingenuity can push back the darkness.

Dancing with Mr. D (Part 1)

Several months ago, I had an idea.  Actually, it was more of a question that I posed to myself.

I had just wrapped up another game session, and was going over some points in my mind.  I was half asleep in my warm bed, passing through ideas in the ether of pre-unconsciousness.  

I remembered another game that I had played a long time ago, where success and damage were determined in one roll.  "I wish the game could do that," I thought to myself.

And then a little voice in my head said, "Why not?"

My eyes snapped open, and I was wide awake.  It was a very weird feeling, something I hadn't experienced before; a kind of buzz, but not brought on by any kind of medicine or drug.  It felt like I had to write something down RIGHT NOW.  If I didn't, it would be gone forever.  I shuffled into the living room, sat down in my chair, and opened up my laptop.  

Success and Damage in one roll.  Lots of different systems handle this, and do it well.  Why would this be any different?  I thought about dice pools, and thought of d6; it's a tried and true dice pool, even set of values, and easy to get.  It can also be broken down to different variables, depending on what you want to represent.

Dice pools can be cumbersome, especially if you're rolling a fistful of dice.  Some kind of limiter would need to be in place.  I started thinking about how to accomplish this, and thought about how it could effect other aspects of the system.  Character creation, advancement, averages, just about everything.  That's how I came up with the Rule of 10 - a dice pool cannot exceed 10 in total.  It seemed like a simple and effective way to limit massive dice pools, and I was pretty pleased with the concept.  Little did I know how deep this simple rule would shape the system.

Target numbers were no good to me, and didn't seem to fit the flow of the system.  I wanted it to be more about the dice, rather than their face value.  Skills and Attributes would be measured in the amount of dice you allocated to them.  How many Attributes, though?  I wanted to remain as simple as possible, so I decided on three; Body, Mind, and Spirit.  These Attributes would also form the basis of derived stat pools; Health, Speed, and Grit.  

Skills were tricky, mainly because I wanted to stay away from a long exhaustive list.  I wanted a simple list, but have the option for complexity and specialization.  I came up with a two tier system of Broad and Focused Skills, with each group granting a benefit to the character.  Broad skills represent general knowledge and aptitude in a field, and Focused skills represent specialization and expertise.

There's a lot more to talk about, and it's still evolving.  Stay tuned for more!

Memory Motel

Another update?!?  

*Insert Princess Bride Inconceivable gif here*

I don't want to jinx anything, so I'll leave it at that. ;)

I've come across a bit of a block recently, concerning time management.  It wasn't an issue in the past, because I was able to access my working documents on Google Drive.  Unfortunately, that avenue has been closed, and my access has been restricted.  As a result, I have a small window of time that I can work during weekdays, and thus, productivity has suffered.

Although this is a hindrance, I haven't let it trip me up completely.  I've been taking notes and writing up what I can on a few notepads, and then transferring those notes into my docs on Google Drive.  It's a little more work, but I'm kind of enjoying it; call me Old School, but I like writing stuff out with pen and paper.  It gives me the opportunity to really think about what I want to put down, and flipping through pages of notes is cathartic (at least to me).

So what have I been coming up with?  

Setting specific mechanics is one thing.  This includes Races of a sort, but it's based more on location.  There are four species total, which includes human; the others will be revealed here as teasers.

Another item I wanted to focus on was more dice mechanics, and I think I've come up with a neat little addition.  I'm calling it Elements, and they enhance your roll in very specific ways.  Each Element has a positive and negative quality, which is activated by the type of roll you make.  Players have the option to purchase an Element at character creation, or ignore them completely.

Finally, I wrote up some more planetary history, and a few culture specific details.  The world(s) are really starting to take shape, like they have a life of their own.  It's pretty exciting!  Ya, I'm kind of geeking out on this, but it's cool watching something take a life of its own.

One last thing I need to address is the actual game mechanics.  Would you like me to talk about the core mechanic, and give more details?  If there's enough interest, I'll go into more detail for the next post.  Let me know!

High and Dry

Hi there.

It's been a while since I've posted; sorry about that.  I could go on a long tear about work, life, and whatnot, but I'm sure you'd be bored to tears.  The short of it is, I've been busy and totally neglected this poor little blog.  I'm hoping to rectify that over the next few weeks, with more updates and activity.

Even though I haven't been active here, I have been doing a lot of developing and playtesting.  After receiving some feedback, I've made some changes to the mechanic in an effort to streamline gameplay.  It's yielded positive results thus far, and players seem pretty happy with the change.
Another theme I've been revisiting is the emphasis on dice.  The mechanic uses six-sided dice, but not target numbers, per se.  Numeric value of each side has a different meaning, and each die has a purpose.  You're always doing something, even if you fail at a task.

While we're on this subject, let's talk about the core mechanic.  First and foremost, everything is represented as dice (or more accurately, d6).  Whatever number you have in an Ability, Skill, or Health is the number of d6 you have in said trait.  The same goes for task difficulty; picking a lock would be represented as a 5 die difficulty.  While this may seem similar to a target number, the action and resolution is very different.  The player's dice roll not only determines success, but how the dice effect the target difficulty as well.

Confused yet?  Don't worry, more on the core mechanic later on.  Hopefully this piques your interest, even if just a little.  I'll post some more details next week, maybe even a sample encounter.  Until then, thanks for checking in, and I'll be more diligent with staying up to date.

Who's Driving Your Plane?

Vehicles.
It can be a tricky mechanic to tackle, no matter the game system.  I've brainstormed, come up with some potential rules, and even run through a few test scenarios.  All of this led me to scrap it and start over again.  The main issue I kept running into, was that the mechanics became overly cumbersome and complicated.  It's hard to pitch a simple game system when one of the mechanics isn't.

As a result, I've kind of avoided the vehicles section for a while now, focusing on other parts of the game.  I ran another playtest, gathered some feedback, implemented some rules, and moved on.  The problem wasn't going to go away, but I had no real answer.  In the meantime, I watched a few of my favorite movies/TV shows for inspiration, and wouldn't you know it...I got inspired.

In many movies and shows, the ship itself IS a character.  It has personality, charm, and a soul (sometimes literally).  Why not stat out a vehicle the same way a character is built?  Use the same attributes, skills, and so on, but on a different scale.  It seemed a little too simplistic, but I tried it out.  The results thus far are very encouraging.  I'm really looking forward to test driving (ha ha) these rules in the next playtest, and getting some feedback.

I hope you've been enjoying my ramblings so far, and would like to hear back from you.  What would you like to see in the future?  Sound off below, and let me know what you think!

Don't Be A Stranger

Hey folks, sorry for taking so long to post.  Time just warped by at light speed, and now we're in February.  I had a bout of flu and strep last month, so that knocked me out for a while, and work has really picked up.  I'd like to get in a post at least every other week, but it all depends on what's going on.

I managed another playtest this past weekend, and was able to incorporate elements of the setting I've been working on.  There was some pretty good feedback on both the system and the setting, and I made a few discoveries along the way:

• The average target number for non-opposed test is way low.  Players were able to easily overcome these tests, and I had to adjust on the fly.
• Good news is that the system was able to compensate quite easily, and I was able to input the new adjusted target numbers with ease.
• Huge difference between having a skill, and not having a skill.  Seems like a no-brainer, but it really showed in the rolls.  Even a single rank was enough to really differentiate between the haves and have nots.
• Not having a skill for an opposed roll was killer.  The system incurs a -2D penalty when attempting an unskilled roll.  Really punished the players for not having a skill.
• The system can be pretty gritty, in its current incarnation.  Getting shot or stabbed really hurts a character.  Go figure. :P
• Emphasis on specialized skills is a benefit, and possible hindrance.

Overall, I believe that the potential remains for the system to be utilized as a universal game system, with options to adjust for any setting the GM wishes to use.  I intend to test this out with another playtest, using a completely different genre and theme.  There are mechanics that allow for more pulp, over the top game play, but I'm undecided if I want to include it as the default, or not.  

Another thought I had was what setting would be the initial "Selling Point".  I have a few that I'm working on, and there's one that I had a hand in creating that could be easily converted.  I know it's a long way off, but it's something that may influence how the system develops.  Right now everything is vanilla; there are no setting specific rules, equipment, races, etc.  I'd like to go the route of including setting specific rules in each new setting book, but I'd also like to have a free setting when you purchase the core rules.  

I'm slowly inching towards a full blown playtest document, so stay tuned if you're interested in participating.  I can't say if it will be sooner rather than later, but it is on the way!

Brand New Car

I have a couple of ideas, and would like your input.

I'm considering implementing a Career mechanic into the system, which would give certain benefits to the character.  It wouldn't be mandatory; the system isn't level-based, and you can build your character as you see fit.  The chosen Career would be a template to build upon, at the cost of build points at character creation.

I've also been developing a setting that is a mix of Sci-Fi and Fantasy.  Right now, it's pretty localized; 2-3 planets, maybe a moon or two.  Space travel is fairly new and expensive, so you won't see a lot of tramp freighters blasting across the sky.  The other option would be a full blown Space Opera, with all of the trimmings; multiple planets, lots of different races, and space transports galore.

So what would you like to see out of these options, and why?  

Ride On, Baby

Hope everyone had a great time celebrating the New Year!  I'm really looking forward to this year, and seeing how things develop and progress.  It's easy to get caught up in the excitement during this time of year; New Year, New Me philosophy and all of that.  I can tell you that my local gym is beyond packed right now, which is fairly routine for January.

The downside is that the luster soon wears off, and instead of a positive outlook, it becomes more of a chore.  Things aren't going as fast or as smooth as you anticipated, other commitments take priority, or Life just gets in the way.  This isn't meant to be pessimistic, but rather a lesson in expectations.  Don't go nuclear, just burn bright and steady.

In short, my development philosophy is approach it like a marathon, not a sprint.

With that said, where am I currently in development?  Let's take a look.

Update #6

• Mechanic update - The Story Dice I mentioned in the last update really seem to mesh nicely with the core mechanic.  This separates the dice into quantity and quality, as well as open up avenues for interpreting the dice in a dramatic fashion.  
• Although I've mentioned it elsewhere, the system utilizes a D6 pool.  The core rule is the Rule of Ten - no dice pool can exceed 10D.  This comes into play when creating your character, as well as advancement.
• Characters are further defined by Strengths and Weaknesses.  These are qualities that either give your character a mechanical, or roleplay advantage or limitation.
• I will be conducing longer playtests with a local group in the next few weeks, which may lead to a campaign.  
• Not enough setting has been developed to really jump into anything long-term (yet), but will continue to be fleshed out.
• The longer playtests will determine how close I am to creating a full-fledged playtest document for others to test drive.
• Setting development has been a bit slow.  Lots of ideas, but not all are conducive to the setting I'm creating.  These are jotted down for later, maybe for another setting book if this proves to be a successful endeavor.
• I'm sticking with the science-fantasy route, as it really appeals to me.  It will lean more towards fantasy, with hints of tech (plasma pistols and minotaurs?).
• Transferred all of my docs to Google Drive, as well as Google Docs.  Even though I was backed up, I don't want to take any chances.

I look forward to posting more updates throughout 2017, and look forward to hearing from you!

All Down the Line

Here are several descriptive phrases of the setting I'm currently working on:

Science-fantasy

Exploration and (re)discovery

Magic, technology, and science

Post-cataclysm era

Fantasy themes using different mythologies

Multiple planetary system (not Sol)

I have some vacation time coming up, and I'm hoping to get some work done during that time.  

Although I'm not a Project Coordinator, I do see the need for a project plan to keep things on track.  It helps to establish project milestones, and track what you've accomplished, as well as slippage and what needs attention.  I used to be a bit of a procrastinator, and it still rears its head once in a while, so anything that keeps me focused is a welcome addition.  

I'd like to accomplish a few things before the end of the year, so I can have a smooth transition and keep moving forward.  I continue to write as much as time allows, even if it's just a sentence to two.  I've also started collecting various images for inspiration, and examples of art I'd like to incorporate in the book.  I'm a visual person, so this helps me in many ways. 

So, short an sweet for an update.  Hopefully you're enjoying the peak behind the curtain thus far.  Feel free to post below, and share your thoughts!  :)

No Use in Crying

I had my laptop stolen this past weekend.  The same laptop that has all of my notes and development for the RPG I'm currently developing.  Yeah, that laptop.
I'm just thankful that I did a backup a couple of days before, so it wasn't a total loss.  Still, it's a bit of a blow, and I've been a bit "out of sorts" lately.

I'm also at the point in playtesting where I need to do so more consistently.  Unfortunately for me, I have to wait until the new year before I can get a group together; it's a busy time of year for everyone, and just not feasible.

It's still way too early to begin actual writing, because the rules are still in flux.  The mechanic is solid, but the rules are still being tweaked.  As a result, I'm in a weird holding state, where I'm waiting for interaction.

Before you ask, no, I'm not ready for open playtesting.  Believe me, I badly want to get this out to everyone that's interested, but it's just not there yet.  I guarantee that I will let you know as soon as it's ready to go.

So in the meantime, I think I will use my time wisely and begin setting development.  Even though the system will be universal, I want to create the first setting for the system as well.  Who knows, if things go very well, maybe it's the first of many.

Goin' Home

No real updates this week, just wanted to wish all of my U.S. folks a Happy Thanksgiving.  :)

On with the Show

And now, back to our regularly scheduled program!

Sorry about the delay, but Life kinda distracted me.  Nothing horrible or tragic, just...Life.  Work, family, friends all swirling about, and before you know it, a couple of weeks have passed.

Enough of my lame excuses, you're not interested in that!  Let's talk about what I've been up to, and how far along I am with my Mystery Mechanic (maybe I should TM that?).

Update #5

• Mechanic update - Tested alternate mechanic and found that it over complicated the process.  However, I do need to implement additional resolution parameters to make the numbers work.  The percentages are even for certain results except for these two; it's mainly because they're set as a pair instead of being separate values.  I've been thinking about implementing these two values as story effects (Positive and Negative), which could then be used to interpret the dice.  Haven't had the chance to playtest this yet, but it's on my To Do List.
• Speaking of my To Do List, it's starting to really fill up.  I've been so focused on development, I've let other points slip; setting up an LLC, TM a couple of items, registering domain name for the future, etc.  Most of these items are for the future, so I've been ignoring them as a result.  I'm kinda bad about that.  :(
• Setting(s) - I've been jotting down notes here and there, collecting art for inspiration, and doing a bit of research.  I have a firm idea of what the first setting will be, but I don't want to give it away just yet.  I hate to tease, but I want to make sure that it's solid before I present it to a larger audience.  Expect an elevator pitch soon!
• Playtest - I'm starting to think I should create a page just for playtests!  Data was collected, and the players were very informative.  Simple character creation was conducted, which was completed in a short amount of time.  Next step will be to include more character creation options, and see how they effect game play.
• Preliminary writing - Typed out the Contents page, which will change over the course of writing.  Still, it was nice to see what it could look like in the future.  Also started outlines for several chapters, and some initial writing for those as well.
• Art - Not even on my radar yet, but I have high hopes!

Well, that's all I have for now.  I don't have any more testing planned for the immediate future; upcoming holiday and family come first, after all!  I'll be more diligent in the future concerning updates, so stay tuned!

Try a Little Harder

Completed another round of early playtesting this past weekend, with interesting results.
I had a simple outline for the group that evening; give a brief rundown of the core rules, explain character creation rules and create characters, and end with running some combat simulations.  The group understood the rules easily enough, created some diverse characters to test the combat system, and we were off.

Combat flowed fairly well, with some good input from the players.  I was doing one-on-one combat with each player instead of group combat, mainly because I wasn't quite ready to test out that mechanic yet.  Players gave their input after a few turns of combat, and I jotted down notes during and after each combat.

The playtest was pretty much done, and there were some good conversations about the mechanic and how to implement it in this setting or that; I have to admit, I was feeling pretty stoked.

Then one of the players asked a question about the resolution mechanic.  It gave me pause, because I didn't have an immediate answer.  The group discussed the issue, and delved deeper into the root cause and potential fixes.  More testing started up to quantify the issue, and how to resolve it in the future.

This may seem like a failure, but I count it as a huge win.  Sometimes, you're so close to what you're working on, you fail to see what may be wrong; that whole, "Forest for the trees" thing.  I can't stress enough how important playtesting is when developing.  Even when you think you're done, do it some more.

I'm also very fortunate to have some very sharp individuals for playtesting.  They really dove in with little guidance, and put the mechanic through its paces.  That last part about testing and trying to resolve it?  That was all them.

I've run some simulations, using the mechanic as is, as well as a revised version.  Interesting results thus far, and there may not be as much of an issue as previously thought.  I'm hoping to do some extensive testing this weekend, using some scripting to get a large batch of results.  AnyDice is great, but I need something a little meatier.  Hopefully I won't have to reinvent the wheel; developing an RPG system is enough work as is, thank you very much.  :)