Game Mechanics refer to the rules and agreements between players that foster play and story advancement.

The basic goal of the game is to collectively create adventures.

 

The major rules of the game exist to allow story advancement between participants.  You may not force characters to do things which are beyond their abilities, or unlikely given their characters motivation.  Disputes are resolved by moderator approval.

 

How to play

Write the actions of your character in third person.  You can also control NPCs (within limits; see below)

 

Basic permissive mechanic

Any character can perform a reasonable action provided that:

a) it advances the story in some way

b) the rest of the players agree it's plausible

 

The plausibility factor is really where the cooperative aspect of play comes in.  Other players and the DM need to decide what is reasonable in any given situation.  If it is something fairly routine, then there is no reason to nit pick and all can just accept it.  But if the proposed action is not guaranteed, that's when dice rolling comes into play.  Dice rolling is a way to use probability, the characters statistics, modified by the difficulty of the action to test if it can happen or not.

 

Expenditure of energy to stretch limits

Dice rolling need not be the end all of a situation.  If the player has a very slim chance, they can expend points to increase their roll. 

 

Relevant links

Dice Mechanics

opposed rolls

novel action

screen layout discussion

combat

SAPTIS

Character Design 

 

 

 

Below are further exploration of rules that apply to collaborative storytelling.

---

No unreasonable suprise attacks

 

A basic rule is that you cannot assert unreasonable harm to an opposing player without warning.

 

For example,

The Vibenyolo suddenly unleash a massive fleet of superdreadnoughts (which

they have built in secret) and burn the Shashnimyn homeworld to dust,

simply becaue your name starts with S like the great defilers the

Sith.

 

He He He, No.  This is not allowed.  The Vibenyolo player in this case may launch his reserve but has to attack the Shashnimyn homeworld properly.  Presumably there already defenses waiting for an assault.  This is comparable to a block in acting.  You can play through these though, there is not always a need for correction.

 

But the Vibenyolo had forgotten the dense network of system satellites that were deployed near the homeworld.  There was also a standing fleet within the system prepared to greet them.

 

At this point, the two players would roll out battle results and then add a story to it, unless they had another point to wager.  The Vibenyolo might want to add that he is sending all his fleets in tail of the SDNs.  In some situations the block might be accepted by an opposing player but they put a twist on the story.  In the above example the players might agree that this was part of a war-game simulation and doesn't actually have an effect on the fates of the worlds directly.  If a block cannot be resolved or ignored, it should be deleted.

 

There is some degree of auto-hitting allowed, but these attacks cannot cause fatal damage.  A roll to check for surprise is suitable depending upon the situation.  Basically, you cannot write the other players into an inescapable position.  The goal is not to kill each other, but to challenge and build an engaging plot.

 

So, even if a player decided to chase the evil wizard over a dilapitated rope bridge high above a lava stream, they will not be killed with one hit.  The wizard can cast a fireball and set the bridge on fire, but the player still has a chance to crawl up the remnants of the bridge before burning to death, or even using a grappling hook, self-stretching magic, or glide to precarious safety on the cliff wall.

 

---

Basic game physics to follow are a modified version of the OGL core ruleset.  The magic is the largest system change, but the discussions of how to play these out to create freeform persistent adventure stories are some of the mechanics discussed here.

html SRD for d20 rules

 

and more rough draft bits continue below

---

NPCs can be controlled by any party so long as they stay in character

 

 NPC control is allowed provided they stay in character. PCs are the property of their owners. Therefore you cannot make each other say things but you can make other PCs do reasonable things:

 

eg. I take point and Khan, Kara & Kirin approach the edges of the shadows. Then I burst into the light ready to engage.

vs

Josh says "I think the beans at lunch were too much" and stinks up his containment suit.

 

Controlling other characters is meant to move the action forward quicker, but if you are in doubt, ask. Story control of this magnitude can also be used to advance the plot.

 

eg. As the last surviving Shashnimyn are cornered in the outpost an embryonic hive has awakened in the Destroyer that just...

 

 

Players may take control of NPCs as well as their PCs as long as they play in character. Characters inactive more than a week can be put on standby by other players. No one can kill your character but yourself. If you put yourself into a jeopardizing situation with no hope of survival, expect to die. eg. you blink into a room with 8 Shashnimyn in full battle gear.

 

Combat and action involving opposing intentions is resolved by negotiation. The first player can say what their actions to initiate the situation are and the second player can respond with what they think would happen, and back again till a scenario is agreed upon. The goal is not to beat each other up as much as make a fun and gripping story that makes sense.

 

---

Allowing a degree of autohitting could really speed up the play. Here's what I propose:

 

1. The first hit in an action sequence can be a freebie, doing a reasonable amount of damage given reasonable situations.

-An ambush can allow players to knock down the opposition a notch before they can respond, making an autohit logical.

-A lone Gorge isn't going to engage a pack of Shashnimyn in combat, you cannot place other PCs in such an unreasonable situation, though an NPC Gorge might be caught unaware.

-The first hits can NEVER kill the other player. If they are severely wounded and running away, your action can be to initiate a combat, but can do no damage.

 

2. Responding to an autohit or combat action, the player has two major options:

Fight or Flight.

-If the player responds to engage, combat is on! and then play it out as you like.

-If the player runs away to regroup, call for back up, or whatever else that advances the story but doesn't start combat, the attacker should play along with that storyline or back off.

 

3. Story points (earned like experience points (XP)) can be expended to undo (or increase) damage dealt to a character. Lets start with a conversion of 1 story point to 10 HP for now. This expenditure should be accompanied by story text. Again, this cannot be done in unreasonable situations to prevent autokilling and power-hungry munchkins.

 

eg. *Mindara falls to the floor after being hit by the Fade's projectile. Less hurt than expected, she notices her amulet magically exploded and deflected the damage. Thankful for the thoughtful gift now destroyed, she rises and prepares an energy bolt for when the Fade next appears.* <used 4 story points>

 

 

My reasons for wanting options like these is because even you mentioned that an 11 post battle could span days. More elaborate pursuits and combats could take even longer in this manner. In my experience, most of the games that fall through are due to time constraints; hard to organize meet ups, or players that are crucial to the next phase of the adventure tied up by deadlines. I don't know what level of commitment all the players are willing to have and I don't want to exclude the creative and excited simply because of real life demands.

---

the scout network the Shashnimyn had prepared