Monday, February 25, 2013

Play by Blog Posting Manual

Welcome guys, I thought I would make the first post a little rundown of how play by posting will work.  To start, here is an example.
 
A) Start all posts with your character's name, and an optional "mood description". The format is [name, mood], for example: [Malachai, infuriated] (The reason we do this is to let people following along with the story know which character is doing what, without having to remember that your google account name goes with "x" character.)

B) Below your character's name, you have two options:
1- Post Fluff or
2- Post Fluff and Crunch.
Option 2 will be the most commonly used. You cannot only post crunch without also providing a fluff portion to describe those mechanical aspects. To further explain, refer to sections on Fluff and Crunch below.
 
C) [FLUFF]
 
When posting in-character descriptions, interactions, dialogue, or otherwise anything that does not involve the mechanical or crunchy side of the game, give that portion of your post the following designation: [Fluff] (Followed by the actual body of text.)
 
D) [CRUNCH]
 
Most likely, the fluff text will need to have some sort of resolution by using the mechanics of the game (die rolls, card draws, &e). Below the Fluff text, start the Crunch text with the following designation: [Crunch] (Followed by relevant info like your trait die being used, the damage to be rolled, the location you're moving to on the map, etc...) Do not roll these yourself. Just list what needs to be rolled so that the GM can resolve the rolls and "respond" with a result.

E) Do not "respond" to comments, always continue with a new comment. Exceptions to this are:
1) GM will always "respond" to comments to reveal the results of any rolls that were made [TECH].

2)When dialogue between characters is going back and forth, use the respond option instead of a new comment, so that the conversation is contained.

3) OOC (Out of Character) comments on specific comments. (only if necessary, will likely start an email chain or something to handle the buk of this)

And lastly, as far as OOC discussion goes (e.g. tactics, planning, meta-related talk), this should be conducted via email between the players.

Below, in the comments section of this post, I have given some examples of "correct" posting. I know at first it seems like a hassle, but you'll get the hang of it, and it keeps everything organized.

2 comments:

  1. [Krint, At ease]

    [FLUFF]

    Krint feels even more comfortable after discovering the captain to be a lover of his family’s brew, and he reminds himself to see if he can share an evening’s drink with the man at some point during the journey. He looks over any of the deck hands he passes to see if they appear competent and trustworthy as he makes his way to the crew quarters. Once there he spies a curious sight. “By the gods, is that you pokin’ about Melgin? Are ye testin’ the hammocks abord’ this ship as well?” ‘HEARTY LAUGH’ “I assure ye’ they’re likely to be as piss poor comfortable as they are abord’ any flyin' boat!” He throws his hand out for shake.

    [CRUNCH]

    Roll Notice d4 to examine any of note regarding the deckhands

    ReplyDelete
    Replies
    1. [GM]

      The deckhands consist of seven individuals (Krint included) plus one captain, Viktor Vantage. Three male humans, a female drakin, a cat wildling, a glowborn, and you, the dwarf.

      Viktor stands as he notices Krint raising his eyebrow. "You're used to men working for you, right Meadbrash?" He points to the many intricately knotted ropes, the dias for the soil, the helm, and says, "I can make this baby fly without much help, but each of ye will be pulling rigging, and working up a sweat while we sail. Every now and then we catch a nice gust channel, and I can handle her on me own."

      Krint looks around at the crew members currently aboard and doubts their boating competency. He also notes that he's hasn't been aboard a non-Dwarven ship in a long while, and has nostalgia for the easier, steam-powered ships that his kind construct.

      [Tech]

      Notice: (3) and (6, ace! + 4 = 10, success with one raise)

      Delete