A new game system in the making...

So I've been thinking of a totally new game system.  Yes, that means ditching my beloved, overhauled, Homebrew version of rolemaster and going with something new.  Something rules-light (actually my Homebrew system is very rules-light), and as story-focused as I have a penchant to be.  It'll be interpretive, because that's the direction I've always been heading (and largely encompassed).  And its going to feature:

d10s! - cos I have a bag of 'em.  Plus they just smack of RPG better than a d6.

It's going to be a dice pool game.  Because I think picking up a fistful of dice, and rolling them all is fun.  Plus that gives a lot of freedom in terms of throwing in extra dice for particular reasons... luck points, fate points, bonus dice, blah blah blah.  Don't worry, I'll expand on all this in another, more lucid post.

It's going to have bonuses to those dice.  So the player will end up rolling xd10+y... i.e. say you have three ranks in a skill, thats 3d10. A basic success chance is a 6 on any of those d10.  The harder the action - and several elements come into play there - the higher than success number is.  But a player can modify their rolls in a number of ways, and add dice to the pool in a number of ways.  So another example might be: try and get 12 or more on 6d10+3.  i.e. a player need only get a 9 or more (with the +3) to score 12 and succeed in that action.

On top of that, I want to include a d20. For no other reason than a d20 for me (probably because I cut my teeth on D&D, back in the day), signifies roleplaying.  Despite the fact that I have not used a d20 in any of my games for years... decades even.  When that 20 comes up, its a special moment, and one I want to include.

So the d20 will work like this:  You roll a d20 as a modifier to any action.  It signifies critical success... or failure.  It's the 'tweak' die.  The higher or lower the number indicates a tweak to the success or failure of the dice pool.  Furthermore a critical is obtained when a 20 is rolled (or a 1 in the sake of critical failure).  At the GMs discretion these numbers may be modified - i.e. a critical is afforded on a roll of 19 or 20, failure on a 1-3 etc. Regardless of a critical, if the tweak die is higher than twice the number required to succeed, the player earns a bonus point from the action which they may use in a future roll.

If a 20 is obtained and the dice pool has been a success - then the action is deemed to be a critical success. In this case the result is extremely beneficial to the player and they get a bonus die and bonus point (which can be added to a future dice pool), i.e. a 1d10+1.  The bonus die and the bonus point are considered separate entities and do not need to be used together.  These bonuses derived from critical success are referred to as being 'on a roll'.

If the dice pool (xd10+y) roll was a success, but the tweak (d20) roll was a 1 indicating critical failure, then the action still succeeds, but the player is left in an awkward position.

For example, a PC attempts to make a jump between rooftops.  The player has 4 ranks in jump so gets to roll 4d10 by default.  As a standard manouevre a roll of 6 or more on any of the dice would indicate success.  However the distance is quite far, so the GM states a roll of 7 is requried. The GM also determines because they are being chased (+1), are wounded from a previous encounter (+1) and its raining (+1); the action is complicated by a further +3, resulting in a 10 being the success marker.  The player determines that this is an essential action for their character, and from their bonus pool adds two more dice and two more points to the equation.  So they're intending to roll a 6d10+2.  The +2 means the result of any dice is raised by 2. So now the player has 6 chances to roll and 8 or more, with 8+2 = 10 = success.  They roll and get and 8 and a 9 (as well as some lower numbers) and so success has been achieved!  However, the d20 tweak roll they make at the same time comes up 1.  This means that despite them having made the jump, something bad has happened.  To determine how bad, the GM looks at the lowest number they rolled - in this case a 2 - and interprets that as them having taken some damage from a poor landing.  A 3 or 4 may have indicated some non-essential piece of equipment was damaged from a poor landing.  If a 1 was present, then maybe something important was dropped into the street below.

In this way perfect flexibility can be brought to bear on interpeting the outcome.  Such rules-light games are fast to play, not bogged down by multiple table checking, and the mechanics hinge upon the imagination of the GM and the players - which is what makes roleplaying so special.  Such rules-light systems harness what is special about Pen & Paper, and what makes it a unique form of entertainment -  i.e. a collaboration of imaginations.

On with the example: if the outcome of such an action fails - nothing 8 or above is rolled, but the tweak die comes up as a 20, it means the action failed, but something nevertheless beneficial happens.  In this example, the PC does not make the jump, misses the other rooftop and plummets down, but lands in a passing haycart.  Again the GM can take a look at the dice pool rolls for some inspiration or guidance.  Because this was a critical success the GM looks at how high the dice were ( though clearly not enough to warrant success in the desired action).  In this example we can say the player had terrible rolls, nothing above a 3, so the GM decides that the passing cart was actually transporting manure, not hay, and the PC is now rather stinky!

In the case of very poor dice pool rolls resulting in a failure of the attempted action, and a critical failure (1) generated by the tweak die, the PC is in a rather tricky situation:  They didn't make the jump and suffered a critical failure to boot, which could be translated as landing badly in the street below.  The intrepetive scale here, I would suggest, is based on what the 'scene' was trying to deliver.  In our example the PC was being chased across rooftops, so the ultimate failure here would be capture.  So this is essentially what is delivered by a critically failed action.  However, the GM does have a requirement to present an interesting, atmospheric and thrilling story.  So whilst they can suggest the player falls to their death, I would suggest avoiding that outcome in all but the most dramatic moments.  I.e. if they 100s of feet up and fell, it might be difficult to realistically avoid death.  And now we come to a potential cardinal sin of GMing.  Despite the fact that IMHO PC deaths should be rare and handled with care, they MUST be delivered if the situation requires it.  One cannot shy away from these moments.  Because nothing ruins atmosphere and verisimilitude faster than GM intervention.  By that I mean when a GM unrealistically pulls a PC out from a certain death situation.  If players feel they cannot die, it removes risk and tension, which results in a lack of excitement and a lack of atmosphere.

In the above example of a critical failure, the interpretive scale has PC death at one end, and something along the lines of a sprained ankle on the other, with broken bones, unconsciousness and capture somewhere in between.  As a GM, one should strive to deliver the next thrilling scene, which in this case might just be the PC hobbling off down a dark alley, having evaded the pursuers (as they're on the rooftops above) but now the PC is wounded and in a bad neighbourhood.

These, as basic mechanics, I think will be a lot of fun. They are of course intended to work for non-combative actions.

The 'Legion' game...

So continuing from my last post about the kidnapping scenario idea.  In the first paragraph I mentioned my 'Legion' scenario idea, and wanted to expand on that a little.  As an unorthodox scenario it necessarily has some atypical elements which need to be considered.

First up, types of daemons:

Due to the unusual nature of the game, I feel it would be most successful with smaller numbers of players.  But at least two of course. Three to four would be my preference, five or more may start getting troublesome due to the probable perceived 'downtime' of (temporarily) subjucated entities.  Although it is considered that all entities will be able to converse - with potential multiple conversations going on in one head.

So the sorts of daemons that might be fun to play in such a game are those concerned with:

Blood - This entity is attracted to and grows stronger in the presence of blood, blood-letting, drawn blood, and any situation where blood is present.  You may want them to have vampiric tendencies or capabilities.  They are also (i would suggest) immune to infections of the blood whilst dominant. So, they get bonuses to their 'control rolls' whilst in the presence of blood - from battlefields and infirmaries to paper-cuts or menstruarion.  Yes, that feisty bar-girl just might bring out the daemon in you.  If you're gamesystem or gameworld has a pre-developed daemon which fits this (or any of the other archetypes below) you may want to use it.  But I tend to make all my stuff up.  And if it works, keep it, and give it a history, and tie it into the legends of my gameworld.

Sex - This entity is probably the force behind succubi and/or incubi visitations.  Acts of lust or blatant sexuality will trigger this influence, and prime its powers of seduction.  You may also wish to go gender-specific with it.  Make the daemon a succubus or incubus, and thus have a target gender for your affections.  In my games, the base idea behind such entities is they wish to impregnate, or be impregnated, so that they may produce a half-daemon offspring whose natural world via birth is the prime material plane and thus they cannot be banished from it.  That said, I see no reason why such an entity cannot revel in 'sex in general' and thus flirt with members of the same sex either.  If you want a player to play this seductive entity I would suggest making the host a young adult - we don't condone any pre-teen perversions here!

Violence - This entity is chaotic, barbaric, psychotic and likely bezerk to boot.  It thrives - and it thus likely to manifest - in situations where violence (or at least aggression) is present.  It will endeavour to create these situations where possible, or be attracted to and found in locales exhibiting them.  So this ranges from battlefields to bar-room brawls, but also some sporting events if reflected in your world: Jousts, bareknuckle boxing / fight clubs etc... or even combat training grounds or scenes of domestic violence.

Fire - This entity seeks out and encourages the flame.  So from bonfires to episodes of arson, this pyromanic entity will thrive whenever naked flames are present.  Thus in some cases even a candle might be enough to trigger its dominance and thus control over the host.

Love - Do all daemons have to be bad?  No. It may be fun stroke interesting to throw this one into the mix.  Perhaps as the counterpoint to sex or violence.  The love daemon thrives on genuine displays of affection.  Whether romantic love; the love between siblings; or parent and child...  or you can even extend it to other forms of love like gustatory or the love of fine art.  Either way, should add an interesting dimension to what would be without it, a faily dark and negative entourage.

Mischief - Although possibly more difficult to engage with, the idea behind this entity is a creature which thrives on practical jokes and generally causing havoc.  Accidents may be a useful trigger which can then be exploited.

Death - The obvious necromantic angle, but one which would be foolish to overlook.  This beast is there to carry you over.  It thrives on the point where life ceases to be and when consciousness drifts to the other realms (depending upon you gameworld).  This entity will thrive in exposure to death, and perhaps in areas attributed to death, like graveyards, mausoleums and charnel houses.

So now we have some basis for events which may allow, certain daemons to have a chance to become dominant, and perhaps even have bonuses to their rolls for dominance.  I'd also suggest using these archetypes to trigger ideas for special abilities.  Furthermore, when a special ability is being used, or a trigger event is being witnessed and a daemon comes into dominance, this act should be visibly signified in the host somehow.  Shadows creep around the boy when then in the presence of death and the death-daemon takes hold.  The eyes go black.  Just as they do when that daemon commits murder through the boy.  The canine fangs elongate and the boy begins to drool when the blood-daemon is present at a blood-letting.  I could go on, but you get the idea.  Draw up a list of abilities, behaviours and triggers for each daemonic type.

So, how does a particular daemon exhort control over the host? Well, the way I'm thinking is a straight-forward battle of wills.  Quite simply, each 'entity' rolls the dice (I'm deliberately keeping this system-neutral in case you want to run a similar game), and the highest roll dominates.  As has been mentioned, you can add bonuses if any 'trigger events' are manifesting at the time.  You should also allow for daemons to willingly relinquish control in favour of another daemon at a particular time.  For example: the way I see this game developing is after awhile, the various 'Legion' daemons will have to start cooperating (at least for the most part) and a fairly typical party behaviour should emerge.  A constant battle for control will draw unwanted attention to the host, and in the long-run it would probably suit all parties to go unnoticed for most of the time until they can trigger some form of special event.  And to this end you need to give each daemon a specific goal - these can emerge during the game, or be present and in mind from the off.  i.e. the sex daemon's aim is to impregnate 13 women.  The death daemon's aim is to deliver 11 souls (read: kill 11 people).  And so on.  Give them objectives.

Start the game with a roll for dominance, and any time the host encounters a trigger event, give the corresponding daemon(s) a chance to take dominance.  The host passes a burning building, such a sizeable fire should give the fire daemon a bonus to take control.  The host wanders onto a battlefield, here violence and death abound, so both these daemons get a chance to take over.

I think this game has a lot of mileage in terms of creating an atmosphere of 'dubious collaboration'. And should be a lot of fun as the players attempt to develop and exploit their various triggers in search of more control in order to exact their particular agendas.

What it isn't is straight-forward.  But that should never deter anyone.

Kidnapping game...

As some of you miscreants might know, I have a penchant for coming up with unorthodox scenarios for games.  One of my favourites, which I haven't had the opportunity to run yet, is a fantasy game in which each PC is a daemon summoned by a sorcerer and all bound schizophrenically (a la Legion) to the same host body.  In this case to the body of a young boy.

So the gist of it is: one physical form, several personalities. Thus all players attempt to vie for control of the host.  Each daemon has its own triggers which may at particular times make it more powerful and more able to dominate the other daemons and control the host.  But I'm not gong to talk about that here.  That's for another post.

The game idea I want to discuss here, revolves around a kidnapping.

Now, this should be a great idea for a quick, one-off game, maybe lasting a day (perhaps two).  And shouldn't take (relatively) too much prep.

Each player plays a character who is an ex-con of some sort.  Let them within reason decide who they want to be.  With the only real caveat that they must have all spent time in the same prison.  Prison is how they know each other.  Shortly after release, they decide to commit a kidnapping to get some money.  Why they need the money should ideally be explored - comments welcome, I've only just come up with this idea.

These PCs are on the whole a pretty bad bunch, as they need to be the sort of people that would realistically commit a kidnapping, and thus inflict such a horrible experience on another human being.

The beginning of the game involves the ex-cons meeting up and discussing the initial planning of the kidnapping.  Everything is important about this phase, right down to where they are when they're first discussing the plans.  The game can then evolve into target selection, safehouse selection, whom amongst them are performing which roles.

The bulk of the work in defining the 'adventure' will be by the players.  As the GM, you'll need to know what sort of things can likely go wrong.  What sort of things can tie people together, link people to scenes, etc.  A list of these 'trigger points' should be defined prior to the game, and the GM should make notes on possible trigger points as they arise from player discussion.

There should also be a few key scenes that the GM should 'pull out of the bag' should the players' situation lead to them.  Police chases etc.  A list of these potential scenes should be defined by the GM prior to the game also - and any that may arise mid-game should also be noted.

Lastly, some of the players should have hidden agendas.  These should be worked out with a few key players beforehand, and kept very secret.

My name is Richard and I'm a roleplayer...

...tonight I have done something special.  I have announced in my hometown that I am interested in setting up an RPG group.  We'll see where this leads.  O, we'll see alright.

I've introduced people to roleplaying before, but I tend to play with a subset of the staple roleplayers I've gamed with for years.  I have never really played with strangers.  Let's give it a go.

The important elements of combat...

Okay, continuing from my last post, I - for my own benefit really - am going to list what I think the important elements of combat are, and what a good combat system should endeavour to achieve.  I still think I might be trying to reinvent the wheel, as I expect smart people have already done this, and I should just get out there and try some new game systems.  (Have I mentioned the D6 system yet?  Must try the D6 system... I've got a thing for d10s though.  Maybe I'll just read the D6 system, and turn it into the D10 system, to make use of the 126 d10s I have lying about).

So, what must a combat system cater for?

• The skill of the attacker
• The skill of the defender
• Situational modifiers like weather, position, surprise etc.
• Multiple attackers or defenders
• Speed of resolution
• Bleeding rules
• Stun rules
• KO rules
• Death rules
• The random element
• Luck of the Gods (bonuses added by the players when they need them most)
• Armour
• Targeted strikes ("I'm aiming for his legs")

Now, firstly, can all these be distilled (read: simplified) into a single roll?  Probably, yes.  (Note to self: must check out the D6 system).  But if so, how do we cater for complex mechanics like bleeding and stuns?

Okay, for the sake of exploring this notion, I'm going to go out on a limb here.  I'm itching to try a new system (D6! D6!).  And I'm liking the sound of these systems that use multiple dice.  Like.  You have six skills ranks in something, and so you roll six dice. Maybe luck of the gods, can add some extra dice into the mix.  So say you roll eight dice.  Maybe you need to get higher than a 4 to succeed, on any one of them.  For a flat skill check like climbing a wall.  But in combat damage is being dealt.  Hit points are being lost.  Extreme successes should result in criticals - criticals can be extra damage, but they can also be bleeding or stuns.  Screw this post.  I'm going in to town tomorrow and I'm going to buy the D6 system.

And I'm also going to talk to the geeks behing the desk about combat, and see if they suggest any other systems which deal with combat well.

In the meantime, I'm going to find some geeky RPG forum and ask what other people think are good combat systems.

I feel a change coming on.

Combat evolved... or maybe just overhauled

So, as you may have picked up by now. I use my own system.  But I still rely on the odd Rolemaster (RM) table.  I'm going to check out GURPS soon, and probably the D6 system, as I haven't played either of those, but in the meantime, I'm in a position to try out my new combat system.

Combat in RM is a bit too lengthy for me.  Roll d% add your combat score, subtract enemy defense bonus check table, and if that gives you a critical, roll again on the critical and check result.  I've been wanting to for some time resolve this far more quickly, and ideally with one roll.  Trouble is, there are many elements to factor in.

Also, the issue I have with RM is, even if you roll a natural 100, because you roll again on the critical table, you can roll an 01 then, and ended up with a worthless critical.  A critical in name only.  A critical that isn't a critical at all.  That is perhaps the suckingest.

So this is what I'm thinking:  after winning initiative (if appropriate) attacking player rolls d100 and adds their attack bonus (from whatever weapon they are wielding) and the enemy also rolls and adds their their defense bonus to their roll (they may also at this point parry with a portion of their attack bonus, but if they do so, they only have the remaining attack bonus, when its their turn to attack).

Also, at this point, any extra bonuses the player has, can be added to the roll.  And the GM may apply any modifiers applicable to the situation, i.e. +10 due to superior positioning, -10 due to inclement weather (have you tried duelling during heavy rain, you're certainly not at your best).

The result of this formula is directly applied to the critical table, i.e. any positive result.  The attackers roll + attack bonus + modifiers is greater than the defenders roll + defense bonus + any modifiers the result is damage done.  Also, RM's exciting 'open ended' rules apply, though modified.  If a natural 100 is rolled, the player may roll again and at that to their result too.  This is in itself open ended, i.e. if the player rolls a second natural 100, they may roll for a third time.

If the defender wins.  Their 'excess' - how many points over the attack they were - may be added to their next initiative roll.  Initiative is rolled between every bout of combat.  So combat follows the format of:

Both parties roll initiative (adding any applicable bonuses, reflexes, quick draw, etc.) whomever wins becomes the 'attacker'.

If more than one enemy is attacking a defender, the defenders roll is divided between the attackers, as they see fit.  i.e. you can choose to be more cautious and defend yourself more thoroughly against one particular attacker.

I'm going to visit my Dutch friend Joost soon.  I hope to test the system with him.  If it works, great.  If it doesn't, I'm tempted to try a far simpler system without any funky critical tables.  Back to the good old days of straight hit points and double damage.  All the detail takes place in the imagination anyway.  It's all interpretive.  I'm not sure thats even a word.  But what I mean is, over the last ten years I've moved further and further away from actual printed rules, and closer and closer to rolling dice, adding bonuses, and interpreting what has occured.  I'm not sure I even need a table to say his leg is severed.

The serpent game...

Okay, so I've had this game in the pipe for quite some time and haven't gotten around to running it yet.  I normally have at least three games on the back burner.  And by that I mean the bulk of each written so it would only take me a couple of days to get up to speed and roll one out if I need to.  But this particular game I'm going to give you the background for is one of my favourites, and I want to take this opportunity to discuss it, primarily because it underpins important concepts in preparation.  And GMing is all about preparation.  Even a good off the cuff ad lib adventure is generally only any good because the GM running it has such a previous body of work to draw upon, they can take a few memorable story lines, a few memorable characters and a few memorable scenes and just string the thing along, resurrecting previously used material, and mixing it up for a new audience.

Anyway, I, as is my want, digress... onto The Serpent Game.

This is a fantasy game set during the 3rd Age of my gameworld, when the sorcerers were rising to the height of their power (having disposed of almost all the nobles and the monarchy at the end of the 2nd Age).

Off the western coast of the principle continent, ten miles out to sea lay a large volcanic (fortunately quite stable, very dormant) chunk of fertile land which people from all sorts of backgrounds had settled on and lived in relative harmony.  The name of the island is Senjaket - which roughly translates from the tongue of its inhabitants as The Isle of Free People.  This name being a legacy from the 2nd Age when travellers first settled there seeking refuge from the draconian laws of the established monarchy present on the mainland.  Senjaket opened its arms to anyone, regardless of race or background, as long as they considered all islanders equal, and agreed to abide by their laws.

Leylines course all over my gameworld, providing sorcerers with natural arcane energy.  For the record, no leylines cross Senjaket.  The nearest node (a minor conjunction of two leylines) occurs at the Mage Tower raised from the sea roughly halfway towards the mainland shore.  It is usual for sorcerers to construct towers from which to work magick at any conjunction (crossing of leylines).

Senjaket is a sort of horseshoe shaped island, with the 'prongs' of the horseshoe pointing east. I'll sketch a little picture of it for you, when I get around to it. In the prong's of the 'horseshoe' is a natural deepwater bay, and the islanders have created a structure of wharfs and jettys to dock the many boats and ships which seek harbour there.  The island itself is predominantly rocky, with cliffs running all around it.  On the western (oceanward) side, the cliffs rise an impressive 1000 feet or more from the crashing waves and the land is quite mountainous.  Heading eastwards these mountains fall away to hills which in turn give way to dense woods as the land slopes gently down toward the bay.  Much of the centre of the island has subsequently been given over to farmsteads and the rich volcanic land is extremely fertile.  A smaller cliff of only 100 feet or so overlooks the bay, and the vast majority of the island's stone structures are built atop this cliff and project back towards the mountains forming a highway down the centre.  The cliffs overlooking the bay are also punctuated by many interconnected caves which have all been taken over and used as shops, inns, storage chambers and in some cases dwellings.  At the base of the cliffs, are myriad wooden structures, inns, brothels, warehouses, shipyards, boatfitters, fishing stores etc.  At the end of each 'prong' is a lighthouse, which serve to mark out the passage for night-time sailings.  The deep bay itself has had some defenses constructed.  Stone bars, risen by mages which almost break the surface of the water at low-tide, make entering the harbour (without prior knowledge of their locations) treacherous.

The island is self-sufficient.  Farmers grow crops and raise livestock, but the bulk of the island's wealth comes from its fishing trade.  The waters around the island are the breeding grounds for an array of different serpent species, and some naturalists come here just to observe and study them.  I based some of the concepts of this island on the Whaling community of Nantucket, after reading In the Heart of the Sea which I heartily recommend.  Its a great sourcebook for RPGs.  Like many historical works, take what works for you, warp it into your setting.  Seem original when in fact you're a terrible thief.  =)

The populace of the island are governed by a council comprised of a few nobles (literally ex-noblemen which fled during the war of the 2nd Age) and some notable members of the community, a couple of farmers, sea captains, a resident mage. The council are on the whole a pretty decent bunch.  They mete out the law via the island's enforcing militia, which are known as constables.

The island has a practise of asking every man and woman sometime between the age of 17 and 19, to spend one year as a constable.  Those that function well in the role are asked to stay on for an additional year as a special constable.  And it is hoped some will remain beyond that.

Each year the island holds a festival.  The festival, held at the beginning of summe,r marks the return of the serpents to their breeding grounds in the waters around the island.  At the end of autumn both young and mature serpents migrate south to warmer waters, returning each summer to breed.  A large contigent of the island is involved in the serpenting trade.  From boat builders to sailors and all the shops and stores that support such an industry.  Serpents are hunted on great 'serpenting' ships, mounted with massive ballistae.  Serpents caught are largely 'processed' on the vessel out at sea.  And the vast majority of each serpent has its uses.  Its flesh is sought after, and its skull contains a light viscous oil which is highly flammable.  Serpents also contain a variety of glands and organs which can be used in various medical and alchemical pursuits.  Some serpents are venomous, and the toxins of such beasts is also harvested.  Sailors may also take the fangs of serpents and turn these massive curved teeth into weapons, swords, knives and arrowheads.  Very little of a serpent is wasted, and even the remnants which are cast back into the water acts as chum, bait attracting more serpents, because like wasps, a dying serpent will release a chemical which attracts others and whips them into a frenzy.  This is particularly true of an egg-carrying female.

In the run-up to the annual Slangwha festival, the town atop the cliffs, overlooking the bay, is painted in bright colours and adorned with flowers and lanterns.  Townsfolk make costumes, the most magnificent of which are the 'slangwhadooks' literally 'paper serpents' - which are the equivalent of those chinese dragons - several people wearing a massive serpent 'puppet come costume' running and leaping through the streets.  The festival is also famous for its drummers, which sit poised, waiting to play, until the first bellow of the first male serpent calling for a mate is heard on the island, and then all the drummers begin, pounding out their rhythms on the animal skins, and there follows singing and dancing; street entertainers and of course the Slangwhadooks charging over the terraced streets and flat rooftops.

The festival attracts many mainlanders, visitors and merchants a like, with boats arriving every day for at least the preceding week.  At festival time the island hosts one of the most magnificent markets as travellers come to sample the freshest serpents around (and bring their fine wares in exchange)  because, of course, when the serpents are heard and the festival begins, serpenting boats also take to the waters.  But in those early days, when the serpents return to their breeding grounds, hunting is strictly controlled.  Only a handful of vessels take to the water and hunt.  Allowing the bulk of serpents to breed and renew their stocks.

And so it is that the game is placed against the colourful backdrop.  All the player-characters are young men and women who have been engaged in their first year as special constables.  Their job is to police the festival and keep everyone safe, as the festival attracts criminals as well as visitors and merchants.  Having provided the players with this backdrop, the game will start just prior to the first serpent bellow, and the drumming.  But it is not long after that a human scream is heard and the players find themselves investigating a gruesome murder, the first of many to come.

...(post unfinished)...

The strangest character I ever played...

I think I've mentioned before how I have a few recurring themes that crop up in a lot of my games, across a variety of genres.  And this is body-swapping, or indeed, mind/soul absorption (which is essentially body swapping turned on its head).  Body swapping is the idea that you can transfer your consciousness between bodies.  Thus you can radically change your appearance, but retain your mental (and depending on the genre), spiritual, magickal and/or psionic capabilities.  This theme has cropped up in numerous of my games, in a variety of ways.

I have even convinced other GMs to incorporate this notion into their games, to let me player a character with that kind of ability.  Perhaps the strangest of these characters was a relatively small blob of psionic jelly.  This was an example of a strange kind of alien that existed in one of my brother's sci-fi games.  Arguably the best game he ever ran (to date, I'm still hopeful he'll run another, but its been several years now).

In his game, my character, as said, was this blob of jelly.  I communicated telepathically (with limited range, a few metres).  I could change colour a bit, a kind of chameleonic ability.  And I could sludge around slowly.  I could seep through small cracks, and in fact through most porous materials...stick on walls and ceilings, but I was prone to all sorts of physical attacks.  Especially fire and acid, extreme cold and a variety of other chemicals.  Slashing, crushing and puncturing damage didn't effect me an awful lot, as I could kind of divide around the blow and then join up again.  Unless the weapon used to inflict the damage was so large it cut me in two and then swept one half of me away so I couldn't readily join up again.  I was slow moving and could form rough shapes, produce pseudopodia, little jellied tentacles with which to grasp and ensnare things.  O, and if I formed a sphere I was a little larger than a grapefruit... or a little smaller than a football.  I could also change my density a little, sink or swim.  And adjust my adhesive qualities, so I could roll like a ball if needed, or spread myself really thin over a fairly large surface area, and elastically 'ping' myself short distances.  Useful if I ever needed to jump off a tall building, as I could kind of turn myself into a sort of parachute by stretching myself into a thin sheet of jelly with dense corners which I could then tuck under and join up beneath me.  Technically, I should have also been able to make myself into a bubble, and then filter out any heavier-than-air gases, and retain any lighter-than-air gases so that I could effectively fly, or at least be blown along by the wind.  Though this I never tried.

Anyway, so that was pretty much the extent to my physical makeup.  However, I had a really neat trick.  I could 'merge' with organic, carbon-based lifeforms and spread myself throughout their bodies and inside their cells, effectively 'blending' with another creature.  In this state I could mimic organs in the host that had failed.  I could improve cellular and organ action to slightly improve the capabilities of the host.  And most importantly I can act like an internal medic repairing damaged cells, detoxifying the body and generally protecting it.  I could communicate with the host via telepathy.  And I could perform all sorts of intricate functions within the brain so I could supress the host consciousness - effectively putting the host into a trance, or a deep sleep or a coma.  In this state I could begin to slowly repair errant brain functions.

And this was my character.  Actually, this was more like my race.  My character was a psychiatrist, which used its unusual biological makeup to cure mental patients of their various illnesses.

As far as all the other players and player-characters were concerned, my character was a human pilot.  Nothing too out of the ordinary.  In actual fact, the human pilot they saw was a mass murderer and my patient, undergoing extensive 'therapy'.  I had blended with the pilot several months ago and had supressed the consciousness whilst I carried out my 'therapy' - curing him of his homicidal tendencies.

This act of consciousness supression worked well on a patient given a particular cocktail of drugs designed for the task, but in most cases, against an unwilling host, the process of attempting to dominate the host and supress the host consciousness and effectively take over the body was a difficult procedure. Virtually impossible if they were conscious at the time, as the process of osmosis took a couple of minutes during which time an active target could just run away.

So the other players thought I was a human pilot, where in fact what they saw as my character was my patient, and I was a blob of jelly within the pilot, attempting to cure him.

The game was excellent.  All the characters had intricate backstories, hidden agendas, belonged to secret societies and no one was quite who they seemed.  My blob was a pacifist - a common trait among the jelly race, and my special task was to prevent the research, design and construction of an organic weapon which could fire a psionic beam at enemy ships and kills all the organic crew within, whilst bypassing all metal, mineral or non-psionic energy structures.  So the threat was high.  A single fast fighter equipped with such a weapon could effectively take down a massive dreadnaught.  As the dreadnaught's shields would be ignored by the psion-beam.

Many of the other PCs had agendas to steal the weapon once it had been developed.  As far as I recall, I was the only character there who wanted to destroy the weapon.  One night I supressed the consciousness of my host, and ensured he was in a deep coma.  I then sludged out of his body, risking exposure and death if caught.  Lots of PCs had laser weapons which caused me a lot of damage.  I then sludged down into the soil and painfully slowly crept through the earth until I was beneath the scientist's (one of the PCs) hut.  I then seeped up through the soil and into the scientist's hut... this was all in the middle of the night by the way.  Once in the hut I sludged slowly over to the bunk where the scientist was sleeping.  And then I risked an unwilling merge.  I warmed myself up to body temperature first, so as not to wake up my target when I first touched him.  I then slowly blended with him and began the battle of wills to take over his mind.  It was a difficult task requiring many checks but I eventually succeeded.  Once within the body of the scientist I spent the next few hours (whilst most of the PCs slept and some were guarding the camp) smashing up the laboratory.  Destroying all computer equipment, and generally wrecking everything, making sure it was irrevocably ruined.
I then set fire to the place, just to be sure and left the scientist asleep whilst I exited his body and seeped once more into the earth - making my way back to where I'd left my patient, the human pilot, in a coma.  Pretty soon the scientist awoke to the smell of burning and saw his lab had been wrecked.  Needless to say he wasn't happy.

Great game.

My Key Words need trimming...

...I think I need to get rid of at least half of my Key Words. My Key Word Cloud is pretty much unusable.  What's a good limit on keywords, anyone know?

How not to handle death...

So, continuing from my last two posts, on the theme of death... -actually I should point out I've just come back from the pub so I'll lay in the apologies up front if this post goes awry- here's how not to handle death.

The following excerpt is from a MegaTraveller game played several years ago.

So the party had fought their way to the top of a ultra-high-rise building whose top few floors were above cloud level.  Barricaded in the office of an executive whom we had planned to kidnap, with extensive (and homicidal) security en route, we considered various escape plans.  It all looked pretty bad.  A rift had already begun to form between our party of four with two players pairing off against the other two.

My character had an AG harness (which essentially meant he could fly).  I did some calculations and realised the power output of the harness was sufficient enough that the device would effectively slow the descent of three people, if used only as a parachute.  And then only as a HALO jump, as it would drain its batteries rapidly.  My character also had a wall-charge, a shaped explosive device which would blow out a hole in an armoured wall.

So, with tensions rising in the high altitude penthouse office and the party divide causing as much threat to each other as the imminent threat from the security pounding up the stairs (we had killed the elevators by this time). I decided to blow a hole out of the bulletproof window.  So whilst the party was setting up for a firefight with the rapidly inbound security, I set up a timer on my wall-charge and placed it on the window behind me.  I realised the pressure at this altitude would mean we might be sucked out of the window if we stood next to it.  As the timer counted down, I grabbed hold of the executive we were supposed to kidnap, and my buddy (played by the inimitable Chris Hart).

Just before the security got to the office, the explosive went off, blowing a massive hole in the window, and the pressure differential began to suck us out.  Having hold of the executive, and my buddy - with the trust of the other two PCs drawn heavily into question, and blatant hostility coming from one - I jumped out of the window, expediting what the pressure was aiming to do anyway.  Dragging the other two with me, we plummeted through the clouds.

Having now effectively stranded the remaining two party members, the more hostile of the two took umbrage and fired out of the window at us.  Fortunately at freefall speed, we were soon enveloped in clouds and out of his sight, still we heard the gauss needles zip past us.

When ground rush began to kick in I whacked the AG on emergency full power and the harness kicked in.  It took all my strength to keep hold of the other two.  (Strength check made).

We landed in the parking lot, and as the bulk of the security was now several thousand feet above us, engaged in a firefight in the penthouse office of the exec I had just kidnapped, it was a relatively easy stroll to lead him at gunpoint to our waiting groundcar.  Thus ending that session.

Apologies for being long-winded, but that's all backstory.

The next session resumed with us (myself, my buddy, and the kidnapped exec) driving into the starport, with a view to getting the exec aboard our spaceship and blasting off.  I can't even remember why we were trying to kidnap him now.  We got to our ship only to find that the two PCs we had left behind to duke it out with the security were already  onboard the ship!  To this day I still don't know how they'd got there ahead of us.  We had freefalled out of the building and drove straight to the starport, but still they had managed to get there ahead of us.  This was my first questioning of the GM's coherence.  It just made no sense that the other two PCs could have got to the ship before us, and I thought he had done it, purely to tie up the two disparate parties.  My first warning is this: as a GM you have all the power to do whatever you want, BUT YOU MUST MAKE IT COHERENT!  Have a reason for it.  An explicable reason.  Even if you don't explain it straight away, it needs to be plausible, possible.  Events in games which defy explanation and look to the players that you threw them in just to get yourself out of a sticky situation only serve to piss players off.  PLAN EVERYTHING!  (...this is actually impossible of course) but where possible, PLAN EVERYTHING! ...or at least have escape routes / interventions that you can logically throw in.

So... there was naturally some frostiness between us (me and my buddy - with exec in tow) and the other two PCs.  Regardless, we blast off and get the hell out of orbit and into jumpspace before the security start chasing down their kidnapped exec.

I realised it was just a matter of time before the particularly hostile party member came for us, so with much deliberation I decided to jump the gun.

My character was a computer whizz (computers 6 in MegaTraveller terms). He made most computer whizz's look retarded.  And so I set about re-writing the ship's computer to vac the ship whilst we were in deep space.  What I did was set the computer to open up the bay doors (in the ships hull) and then every internal door except for my stateroom door, my buddy's stateroom door, and that of the brig where the exec was being held.  These doors would remain locked, and the ship would vac for 5 minutes before all doors were sealed again.

I had to make several checks against my computer skill to do this, but made them all.  So now we just waited (it was all on a timer).

Prior to the designated time, my buddy and I retired to our staterooms.  As an added precaution I climbed into my vac-suit too.  So I had my own air-supply, just incase something went wrong.

It was at this point that the GM finally seemed to realise we were poised to dispose of half the party (under the remit, as far as we were concerned, they would come for us sooner or later).  So at the horrifying thought that I was about to kill two other PCs, he threw a rather ill-thought-out spanner in the works.  He said an emergency alarm went off.  Now, my character with computers 6 had already made several rolls to make sure I made the necessary changes to the ship's computer to set up the vac protocol.  But somehow I had missed this final alarm.  So one minute before the vac was scheduled to take place, an alarm sounded announcing it was imminent.  WARNING! DANGER! SHIP VAC IN T-MINUS 60 SECONDS AND COUNTING.

What did the other players do?  Well the hostile one, took offense at this imminent ship-vac and pulled out his gauss rifle and shredded out stateroom doors with it.  My buddy hadn't had the foresight to don his vac-suit so was now in danger of being deprived of oxygen for the five minutes the ship would be exposed to space.  So he fled his stateroom in an effort to secure himself somewhere else.  As he left his stateroom he was shot by the hostile PC and rendered unconcious and bleeding to death.  Without rapid assistance he would die.  So having seen all this on the security monitors I had piped to my stateroom, I crept out of my stateroom and went to his assistance.  I managed to creep up on the hostile PC and shot him at point blank range in the small of the back with my shotgun.  But alas, shotguns have a low penetration, and his body armour absorbed the majority of the damage.  The hostile PC was stunned a little, but nevertheless, turned round and shot me with his gauss rifle at close range - crippling my character, rendering him immobile.  By this time the countdown was at T-minus 30 seconds and two of the party were down.  One unconcious and bleeding to death, the other conscious but immobile.  The two remaining party members knew nothing about computers, or the ship's safety systems or much else for that matter.  So they waited, 30 long and drawn-out seconds for the ship's doors to open, and all and sundry were flushed out into space.

In trying to prevent one half of the party summarily wiping out the other, the GM had shortsightedly ushered us all to our deep-space graves.  I sometimes think about that lone exec, imprisoned in our brig, on an otherwise empty ship, lost in deep space.  I guess he must have starved to death.  And probably 200 years later our ghost ship would be found by pirates, or salvagers and boarded and they'd wonder: what happened here?

But there's a warning in this tale.  As a GM if you have to think very carefully about the repercussions of your actions.  One can very easily let things get out of hand.  Like party-rifts.  And once they're in place.  Chances are PCs will start dying.  PC's after all, are generally the most dangerous things in the game.  And when such hostilities do commence, one needs, as a GM, to think very carefully about the repercussions of not just what the players want to do.  But also what you, as the GM, say are the net result of their actions.

I still believe to this day that the GM in that game put that alarm in to give the other two players a chance.  Because without it they would be without warning flushed into space.  But in doing so, set up a pattern of events which lead that game to end ubruptly, and well-short of the story mark.  None of us saw how the game was supposed to end.  None of us got much more than about half of the story.

Sometimes, as a GM you have to let PC's die.  Always you have to think ahead carefully and map out the likely results of actions.  Its kind of in the job description.

Still, a memorable ending to what was a highly enjoyable game.  It still brings a smile to my face.  In a forgotten universe somewhere, there is a ghost ship with a skeleton in its brig.  And no other crew.  And the last entry into the flight computer is a command which told the ship to vac.

If I were GM, how would I have handled things differently?

Well, sometimes its hard to avoid intra-party feuds. Thinking back, in the case of that game, the hostile party member was the root cause of numerous party feuds and PC deaths across multiple games.  It would be difficult to manage him out of most of those situations (which he seemed to enjoy), short of not inviting him to play.  (Lesson X - choose your players carefully).  That said, intra-party feuds are not always a bad thing and can result in some fantastically tense and atmospheric games.  I recall one game in particular which my brother ran, in which all seven players had hidden agendas and secret societies and all manner of subterfuge which pitted most of us against most of us.  But that's for another post.

It is my belief that the game went wrong when the other half of the party that was left stranded in the office, managed miraculously to arrive at the our spaceship ahead of us.  The feud was already underway, and could not be helped considering who was playing.  But it was the GM's decision to blur reason and have us all wind up on the ship at the same time.

With the feud in place I would be tempted to have the other half of the party pursue us.  Run a dual game with the same story now revolving around two competing half-parties.  That could have been good fun.

As a GM, once you let a feud develop to a point where a dice-roll can and may cause the death of one PC at the hands of another.  You must have something pretty special up your sleeve not to just roll with it.  Because it either smacks of GM intervention, or the PC's die.  And in this case, both.