View RSS Feed


Blog Play System

Rate this Entry
As announced in ´Foreword´, I present here a set of guidelines for play-by-post&comment within the blog section of thetangledweb. A suitable acronym for the system is BPS+, the ´+´ standing for the fact that play here can be continued in the PbP forum section .

A few words on how this system extends the range of PbP options:

  • Play within one´s blog pages has as foundation the fact that a single person can drive the story forward, independently of anyone else´s input.

  • That person is both GM and player. Depending on certain criteria, some GM rights may be shared with other people. When play is moved to the PbP forum section, all major players involved could have equal GM rights; and responsibilities.

  • Play within one´s blog pages gives everyone else a greater freedom of participation than usual PbP. Anyone could suggest a continuation at any time the story is open for input. In addition, the system is very flexible with regard to how much a player can get involved: Those interested can take on a character as simply defined as a NPC, as complex as a usual PbP character can be, and anything in between. Also, one can play for as short or as long a time as liked, and can leave and return at any time. However, to make this freedom possible, and at the same time maintain the story´s integrity, a number of limitations will have to be imposed.

  • Blog play would constitute a means to circumvent the less pleasant situation where more players apply for participation in a campaign, but only a handful are selected. Of course, not everyone interested in a blog story would have equal participation. But still, the system is more open than usual forum PbP. The nature of blog play should also prevent other happenings that I, for one, find less agreeable: the making of introductions about who everyone is in real life, and the hiding of a story behind a password lock.

  • It may be worth mentioning also that blog play gives to the main player the opportunity of setting the pace and style for her or his character´s development. The story of Errandûrr will be, at first, about his growth into the role imposed by the chosen class; with no recording of experience points gained, only a testament to his increasing abilities as a Ranger.

  • To me, PbP play is, first of all, a context in which to express and share the better aspects of ourselves. I believe that blog play, with its flexibility of content and means of interaction, increases everyone´s chances at experiencing that freedom of being, and the joy that it brings.

The guidelines are organized into sections, which deal, in order, with: ´conduct´, categories of players and characters, storytelling rights and responsibilities, the mechanics of blog play, the complexity of character definitions, and migration towards a PbP forum thread.

For a quick look at the guidelines, see the first comment.

Section A. The Matter of ´Conduct´

  1. The first limitations to the nature of input content would, of course, refer to moral and humane aspects of interaction, and to a differentiation between what is acceptable from personal and professional points of view. I believe they come down to a gentleness between souls, and that can only be truly understood and followed with one´s heart...

  2. The next in order are limitations set by the blog owner´s choices, in particular with regard to the evolution of the main character. In Errandûrr´s case, for example, I wouldn´t like him to be exposed to dangers he cannot handle; which would most likely result in his death. Nor would I want him trapped in some dungeon or to spend much time in a city if the plan, at one time, is to improve his wilderness skills.

  3. Each would-be participant would agree to the limitations and liberties already established between the previous participants. Each new writer would present their own requirements, if necessary, and upon their participation being accepted, everyone else would have to comply with the resulting new specifications of conduct.

  4. Therefore, before accepting a new player´s participation, the blog owner would have to judge how everyone already present´s wishes are observed; as well as how the potential of future players joining in is influenced by the resulting new set of allowances and forbiddings.

Section B. The Categories of Players and Characters

Subsection 1. Categories of characters

  1. A character can be a NPC, a PC, or a Main Character (MC).

  2. The MC is that character, the unfoldment of whose destiny determines the core of a story.

  3. There would only be a limited number of MCs during one major period of a story´s duration.

  4. MCs are like usual PbP campaign PCs.

  5. Beside MCs, a great number of PCs can take part in the story, much less frequent, and within short segments of play, each time.

  6. A NPC that a player takes control of becomes a PC.

  7. A MC is implicitly a PC.

Subsection 2. Categories of players, character ownership criteria

  1. With regard to ownership of characters, players fall into 3 categories: Main Character Owner (MCO), Character Owner (CO), and Not Character Owner (NCO).

  2. While designing BPS+, I found the syntagm non-Main Character Owner useful in differentiating between players who own a MC and those who don´t.

  3. The Blog Owner (BO) is implicitly a MCO.

  4. The MCO is implicitly a CO.

  5. The character of a CO is a PC.

  6. The BO was also called main player above, designation which refers to the fact that the BO is likely to have the greatest frequency of participation with story content. Next in order of participation frequency are the other MCOs, also called major players, above.

Subsection 3. Categories of players, storytelling rights criteria

  1. With regard to the rights of influencing the story, players fall into 3 categories: Story Host (SH), Story Teller (ST), and Story Guest (SG).

  2. The ST is similar to a GM(DM).

  3. The SH is the BO.

  4. The SH is implicitly a ST.

Subsection 4. On the use of the names defined in this section

  1. Beside the usual NPC and PC, I will not be using, throughout the guidelines, any acronym from this section.

  2. The acronyms were employed here only for the purpose of helping you familiarize yourself with the full names.

Section C. Storytelling Rights and Responsibilities

Subsection 1. The duties of the Story Host

  1. The Story Host has the job of putting the story together, by taking into account all available input and the wishes that players have for their characters´ evolution.

  2. The final decisions with regard to content belong to the Story Host.

  3. The Story Host can grant and withdraw rights of the other players.

Subsection 2. On some criteria for granting rights

  1. Normally, the Story Host would be granting rights depending on the players´ availability for play, their compliance to the established rules of play and conduct, and their proven capacity of moving the story forward in a satisfactory way.

  2. However, in the case of Errandûrr´s story I will probably be inclined to favor the participation of the few people I exchanged words with so far; in the desire to strengthen our social connection. I assume this to be a criteria that also other Story Hosts may adopt.

Subsection 3. The implications of having a Character

  1. The Story Host can grant others the right of having a Player Character, which could be a Main Character.

  2. While a Story Host could, theoretically, control any number of Player Characters (and Non Player Characters*), the number of Player Characters allowed to others should be limited, so that the focus of the story would not be lost. (*This is an exception to B.1.f. Here I adopted the custom of GMs having control of NPCs. Only the Story Host would have this right.)

  3. I propose that a player, other than the Story Host, should not be allowed to control more than one Main Character and one, or at most two other Player Characters during a certain, meaningful period of time. Having just one Main Character throughout the story should also fit the Story Host well.

  4. A Main Character is supposed to take part in the story as often as a usual PbP campaign PC does.

  5. A player may be allowed to take control of a Non Player Character; thus converting it into a Player Character. The character´s owner would then be allowed to develop its definition.

  6. Player Characters that are not Main Characters could take part in the story for as short a time and as less often as their owners see fit. However, their inclusion in the story should accord with whatever takes place at each moment, and should be handled in an ordered fashion: both their entry on the scene and their exit should be described and should be justifiable.

  7. A Player Character could be upgraded to Main Character.

  8. A Player Character can be turned into a Non Player Character if the owner chooses so.

  9. In such cases when a Character Owner discontinues play without specifying whether or not their Player Character is to become a Non Player Character, the conversion should not be implicitly assumed, unless the general rules of play demand so; as in the case of an ongoing fight. If possible, the abandoned character should be left in the last mentioned place and condition.

Subsection 4. The right of influencing the story in other ways

  1. The Story Host can grant others the right of influencing the story otherwise than through their characters´ actions.

  2. This refers to the description of events (a change in weather, animal life activity, a NPC´s actions) or static game world elements (a place where the main characters arrive, the front of a building, a book´s cover).

Subsection 5. On Story Teller rights

  1. All the grantable rights mentioned so far are Story Teller rights.

  2. The extent of a participant´s Story Teller rights can vary.

  3. Story Teller rights can be temporary; one-time even.

Subsection 6. On Story Guest rights

  1. Story Guest rights refer to choosing between options made available by Story Tellers, or to making content available, while understanding that the content has a much less chance of being taken into account than that provided with Story Teller rights.

  2. Expressions of Main Characters described by Story Guests would most likely not be taken into consideration.

  3. OOC comments of visitors also fall within Story Guest rights. Everyone making a comment is, first of all, a Guest.

Subsection 7. A hierarchy of the players based on their rights & responsibilities

  1. Story Host;

  2. Main Character Owner with Story Teller rights of describing their character´s thoughts, behavior, speech and actions, and of describing events or static game world elements;

  3. Main Character Owner with only the Story Teller rights of describing their character´s thoughts, behavior and actions;

  4. (non-Main) Character Owner with Story Teller rights of describing their character´s thoughts, behavior, speech and actions, and of describing events or static game world elements;

  5. (non-Main) Character Owner with only the Story Teller rights of describing their character´s thoughts, behavior, speech and actions;

  6. Not Character Owner with temporary Story Teller rights of describing events or static game world elements;

  7. Not Character Owner with only Guest Rights.

Subsection 8. Closing words for this section

This is an incomplete list. The following sections will introduce concepts which will make it necessary to specify new rights and responsibilities.

Section D. The Complexity of Character Definitions

Subsection 1. Preliminary remarks

  1. The freedom to have a very simply defined character is intended to allow easier and quicker establishment of interaction between players; through elements of the story.

  2. In order to keep a character´s actions within reason, it should be understood that to assume any role would also mean to assume some limitations, and to assume power would also mean to assume responsibilities, proportionally.

  3. No matter how simply defined, a character´s expressions, including actions, should be as accountable, according to the rules of game-world system adopted (DnD, Pathfinder etc.) and to the realities of the game world, as if the character would be fully developed.

  4. While an experienced player would find it easy to enter the story with a simply defined character and participate in various ways, the inexperienced players should perhaps limit their characters´ expressions until they grow comfortable with what goes on.

  5. The complexity of a character´s definition should not be a factor in its becoming a Main Character.

Subsection 2. On the necessity of a character sheet

  1. The character sheet is a collection of character relevant informations, so organized as to make it easy to access them. For a very simply defined character, a usual character sheet may prove too complex to be of use; hindering access to information even.

  2. Therefore, in the case of a very simply defined character, a list of defined traits would be a sufficient replacement of the character sheet. The list could be attached to each comment, or referred to through a link.

  3. It is a good idea for each participant to the story to attach to every comment made a list of links towards relevant matters like the character sheet, personal preferences for the character´s evolution, a journal etc. It should be kept in mind that comments don´t display a user´s signature; where usually people place links.

Subsection 3. On the various elements of a definition

  1. A character may or may not have a name defined. In the second place, the character could be called: a person, a woman, a man, a child or another similar name. To identify the character for the purpose of making a specific reference, actions should be preferred to any known traits; i.e. the man who said this or that - instead of the old man with a blue cape.

  2. A character´s appearance should be defined to some extent. The elements I took into account so far, in the case of Errandûrr, are: race (which usually determines certain special physical traits), gender, age, height, weight, build (which usually refers to the distribution of flesh on the body), skin color, eyes color, hair color, any scars, any posture irregularities, any movement impediments, the kind of clothes usually worn and any clothes colors preferences, any other distinctive features (for Errandûrr I specified a walking stick here; which could not be considered a weapon). Of these traits, I believe a minimal definition should specify: the race, the height, the build, any visible scars, posture irregularities, and movement impediments, the kind of clothes and maybe their colors, other distinctive features - like the walking stick of Errandûrr. These would all be traits more easily distinguished. A character´s portrait drawing should be optional.

  3. A character may or may not be classified according to the current game-world rules used (DnD, Pathfinder etc.). In the DnD 5e system, with which I am familiar, the classification would include the character´s class, background, alignment, level, and number of experience points; the race having been specified under ´appearance´. The level and number of experience points would be needed to calculate the character´s progress, if that is desired. The class should be defined if it is intended to use specific spells. Otherwise, the class and background would be defined as a means to manage the access to specific skills (in a broad sense of the word), or restrictions to that. The class and background also incline towards assuming a certain role in the game world. Not having the class and background defined allows a great freedom of action, but also makes accounting of what can or can not take place more difficult. The alignment should be made obvious by the character´s choices.

  4. A character may or may not have numerical values defined, as for such things as attributes, or any matters of a character definition that are quantifiable. In the second place, the result of any calculations which become necessary would be replaced with approximations of the effects.

  5. A character may have the equipment defined only up to the clothes worn. Any object worn, held, or used could be included; depending on the duration of possession and the context. Any other items in permanent use, or quickly replaced once they are broken or spent, may be mentioned at the time of their first active employment. If this kind of definition is chosen, then a good enough justification for having had that item in possession should be offered at the time of use. Also, some information should be offered that would allow everyone to estimate the character´s proficiency in using that item.

  6. A character may have the personality traits gradually introduced throughout play. This would allow the participants to determine what I consider to be the core of their characters based on the events that take place in the story. Of course, if anyone has a good idea about who their character is, a more complete initial definition would be the choice. Personality traits may just be left to be deduced from the characters´ actions; just as the moral alignment could be.

  7. A character may have a back-story defined, if their owner likes. It would serve to justify some personality traits and abilities, as well as the characters´ goals. But the definition of a back-story could also be easily left until a good time of sharing about their past (or of revealing it) comes. However, an important aspect which the back-story would have explained is the character´s social and employment status. That may come to everyone´s mind quicker than other aspects of that character´s life.

Subsection 4. The possible cases of character definitions

  1. I propose that at least the appearance and some items in use would have to be defined in order to introduce a character to the story. The elements of appearance should include everything that is most easily visually identifiable.

  2. A slightly more detailed definition would include the name, less obvious appearance related traits, some specification of skills, the social and employment status of the character.

  3. A more complex definition than that would have to include a quantification of the character´s abilities and assets. This would most likely imply also giving the character´s classification, according to the game-world rules in use (DnD, Pathfinder etc.).

  4. An even more complex definition would go into psychological and back-story matters.

Section E. The Mechanics of Blog Play

Subsection 1. On the divisions of a story

  1. A story can be regarded as a series made of episodes.

  2. Each episode would, naturally, be defined by a time frame of relatively short span, and would focus on a limited number of story elements; which, customarily, determine a plot (and are sufficient for this purpose).

  3. Each episode would be divided into parts.

  4. A blog post covers one episode part.

  5. A part may sometimes cover a very short period of the story. The cases of dialogs and fights, which usually span across several PbP forum thread posts, are good examples. Each episode part, however, may contain story elements other than the most expected content.

Subsection 2. On the story border between post and comments

  1. In each blog post, the story would be brought up to a point beyond which input from comments may determine how the story continues.

  2. While not mandatory, the Story Host could mention, at the pause point, the known intentions of all Main Character Owners (including the Story Host) for how the story would be continued.

  3. No modifications would be made to the current blog post based on comments.

  4. The content of the comments is supposed to be taken into account while designing the next blog post.

  5. After a predetermined period of time, input would no longer be allowed. This situation would last until the next episode part is published.

  6. Overdue comments may be taken into account or ignored.

Subsection 3. On the decision to bring the story to a pause

  1. Ultimately, the Story Host decides the pause points (like the GM during a usual PbP campaign), but the suggestions of other participants would be taken into account.

  2. Main Character Owners´ choices will have priority over other Character Owners suggestions; and those will have priority over Not Character Owners suggestions.

Subsection 4. On preparing for a possible pause point

  1. Up to the pause point, the episode part would include descriptions of accepted evolutions of each Player Character´s situation.

  2. In view of possible pause points, all Character Owners would be expected to offer the Story Host enough information about what they intend for their characters, so as to avoid any unpleasant surprises.

Subsection 5. On the content of participation comments

  1. At the pause point, it would be specified what kind of content is expected in the comments.
  2. Separate indications would be given for the different categories of players.

  3. In general, it would be assumed that content for every Main Character will be provided, by the respective owners, at each pause point.

  4. Content referring to character expression describes: thoughts, behavior, speech, and actions. References to owned or surrounding objects may be made. Unless an on-going event, like a fight or a conversation, requires a specific type of content, character owners should be free to choose the kind of content.

  5. Content referring to static game world elements can describe their properties or aspects of their mode of functioning. The range of possible traits of game world elements would be determined by their general category (e.g. a building) and any specified subcategories (e.g. a small, derelict building).

  6. Content referring to events not directly related to a NPC, may be limited by the specified amplitude, duration, area of effect, and the distance from the main character(s) at which the event might occur.

  7. Content provided with temporary Story Teller rights, or with Story Guest rights can be developed by the participants with higher rank rights. For example, if someone mentions a noise in the room above that where the group of Main Characters is, the Main Characters Owners (or only the Story Host) may decide what the noise was about.

  8. Unless otherwise established, all content should be realistic, according to the game world´s limitations of manifestation, as well as to the opportunities of manifestation made possible by the story (in its current stage).

  9. Each participant should have in view the fact that the Story Host will work to produce a cohesive next episode part. Unless a participant whose content is included in the story has provided enough information for transitions to and from the focus of events from that content, the Story Host would have to improvise the transitions.

  10. Comments content would include dice casts. Some according to the game-world system rules (DnD, Pathfinder etc.). Others to help determine what of the comments becomes part of the story, as described in the Subsections 6 and 7, following.

Subsection 6. On how it would be decided what becomes part of the story

  1. Ultimately, it would be the Story Host´s decision what should and should not take place in the story based on the extent of each participant´s Story Teller rights, and on the compatibility between the comments´ content and the Main Character Owners´ preferences for their protagonists.

  2. The Story Host´s wishes (specified or not, according to D.2.b.) and the specified choices of Main Character Owners with extensive Story Teller rights (of character, events, and static elements description) would form a separate set of content that will be given first priority and importance, story-wise.

  3. Next in the order of importance are the choices of Main Character Owners with limited Story Teller rights and the choices of non-Main Character Owners with extensive Story Teller rights (of character, events, and static elements description). Any conflicts involving the fate of the Main Characters would be resolved in favor of their owners.

  4. Then is considered the input of participants having no Main Character and only limited Story Telling rights.

  5. The input of other participants may or may not be taken into account, and would have the least priority.

  6. If contents of equal priority are compatible, the Story Host would create a blend of them. If, instead, a situation of conflict arises, the Story Host could resort to using the dice for decision.

  7. Players found higher in the hierarchy of decision making, beginning with the Story Host, would decide whether or not to include such content from the participants of lower prerogatives that crosses the boundaries of the story´s current events´ time frame. I am referring here to the habit of adding in one´s PbP forum post descriptions of events from the recent past, the habit of stretching a story along the time scale in order to allow each player a certain freedom of making their character fit the current developments. As the Story Host has the responsibility of presenting a cohesive next episode part, no one should expect to have in the story content specified as taking place at any time. However, it may be reasonably expected that content from the very recent past is considered for inclusion.

  8. The Story Host could inform the participants, in an OOC introduction to the next episode part, of any decisions made with regard to the content from comments.

Subsection 7. On dice based decisions

  1. In general, whenever an element of randomness is found acceptable, within certain, specified limits, the dice may be used to decide what of the participants´ input content may be included.

  2. The percentile dice seems best suited for the mentioned purpose.

  3. Each participant would accompany her or his comment with a d% cast, which could be labeled ´Priority´.

  4. To not provide the cast in the comment would mean to leave it in the care of the Story Host, understanding however that it would be entirely up to the Story Host to show the result of the cast in an OOC section of the next post; or to cast dice (take the comment into account), at all.

  5. With reference to the groupings described in paragraphs b-to-e of the previous Subsection, the dice would be employed for establishing priority within one set of content.

  6. In between one set of content and another, the order of priority of the groupings, as mentioned in the previous subsection would be followed.

  7. The four groupings (sets of content) may be compared to a train. The locomotive would stand for the first group mentioned (D.6.b.). It would be a special kind of train from the passenger cars of which people - as represented by the dice casts - would shout about their desired destinations; and would be heard depending on their distance from the locomotive. And here´s a visual representation: I-100, I-99, ..., I-1; II-100, II-99, ..., II-1; III-100, III-99, ..., III-1; IV-100, IV-99, ..., IV-1.

Subsection 8. The possible structure of an episode part

  1. The structure of an episode part could be divided into three subparts: an introductory one, a middle one, and an ending.

  2. The introductory subpart could have 3 sections, as follows.

  3. A first section (OOC) would contain a welcoming message, some information for newcomers, and story related links.

  4. A second section would contain a short review of the previous part, placing an emphasis on the main characters´ expectations of what would happen next. This section would be optional.

  5. A third section (OOC) would deal with the processing of the comments made to the previous episode part. It seems a good idea to reproduce content using the ´quote´ tag here. This section could be optional.

  6. The last two introductory sections could be interchanged.

  7. The middle subpart could have 3 sections, as follows.

  8. A first section would reproduce content from the comments, fully or partially, alone or along other story elements, as the Story Host sees fit. The ´quote´ tag would not be suitable here.

  9. A second section would allow the Story Host to act independently from the other writers. The purpose could be to steer the story in a wanted direction, to maintain certain elements in the story - elements that would otherwise be lost, or to add background content that would add depth to the story.

  10. A third section would place emphasis, if needed, on those aspects of the story that the participants are expected to react to.

  11. The ending subpart could have 3 sections, as follows.

  12. A first section (OOC) would contain specifications on what is expected from the participants. This one would always be needed for addressing new, potential participants.

  13. A second section (OOC) could specify the Story Host´s preferences for the continuation of the story, in particular with regard to the fate of their Main Character. This section would be similar in content to the comments of the other participants. The section may not always be necessary.

  14. A third section (OOC) would contain OOC information in the form of useful links; also a parting message.

Section F. Migration Towards a PbP Forum Thread

Subsection 1. A time for migration

  1. Once the Main Character Owners have formed a cohesive group, play could be moved to the PbP section of TTW´s forum.

  2. The purpose could be to bridge any social gap that may have been established between the players frequenting blog play and those who chose traditional means of interaction.

Subsection 2. GMs and players

  1. The Story Host may then become the GM, and the Main Character Owners - the players, although the Main Character Owners could maintain their Story Teller right of making suggestions on the continuation of the story.

  2. It is also possible for the Story Host to renounce the prerogative of having the last word with regard to the story´s evolution. In that case, all Main Character Owners would have equal GM rights.

  3. As a Story Host, I would agree to that only when Errandûrr has reached his goals or when he has achieved the equivalent of that through development as a person and as part of relationships with other characters.

  4. With equal GM rights, it would be possible for each Main Character Owner in turn to take on the role of GM for one small part of the story.

Subsection 3. The other participants

  1. The rules of the forum section would have to be observed. If I am not mistaken, it is specified in the rules that only the GM and the selected players - the equivalent of the group of Main Character Owners - are allowed to participate in the thread.

  2. To make it possible for other participants to bring some contribution to the story, as during blog play, the blog story could be maintained (by the original Story Host) in parallel to PbP forum thread play.

  3. If play in the forum thread takes place too fast, it may suitable for the blog posts to include more than the events of a usual episode part. Consequently, the content offered by non-Main Character Owners would also have to cover a larger segment of an episode. An alternative would be to reduce the time frame for accepting comments, while maintaining the usual size of a story part in each blog post.

  4. The Story Host would mention, as usual, what is expected from the other participants than Main Character Owners. However, the context described in the previous paragraph - of zooming out from the span of a usual episode part - may make suitable, in general, less precise indications of what is expected. There would also be propitious moments for introducing to the story particular elements which can be precisely indicated.

  5. Promotions to Main Character Owner and other granting of rights, below that rank, would still take place within the blog´s story pages.

This is it, this is BPS+. Awfully long, the description, I know... and maybe stuffy, in places... Hopefully, comprehensive enough too. And solid. That was my goal. In a short while you should be able to see the system applied in Errandûrr´s story case. If I would be playing alone, I suppose I could simulate the input of other, imagined participants; for the purpose demonstrating the system. Thank you for your interest ~

Submit "Blog Play System" to Digg Submit "Blog Play System" to Submit "Blog Play System" to StumbleUpon Submit "Blog Play System" to Google

Updated 03-13-2018 at 06:36 PM by Erran (righted a word; don´t guess which - it doesn´t really matter)

Tags: errandûrr, ooc Add / Edit Tags
Frontpage , Errandûrr


  1. Erran's Avatar
    A summary of the guidelines:

    Be nice? [A.]

    There can be other PCs than Main ones. [B.1.]

    It is possible to participate otherwise than through a PC. [B.2.]

    A wide array of Storytelling rights is possible. [B.3.]

    The Story Host runs the show. [C.1.]

    Rights may be granted based on objective and subjective criteria. [C.2.]

    There shouldn´t be more than one Main Character per player, and no more than a few PCs per player, in total. [C.3.]

    Other PCs than Main ones need not play a consistent part in the story. [C.3.]

    A NPC can become a PC. A PC can become an NPC. [C.3.]

    PCs´ evolutions should fit the story line. [C.3.]

    It is possible to influence the story by describing events or static game world elements. [C.4.]

    Storytelling rights can be temporary, one-time even. [C.5.]

    Everyone making a comment is a Story Guest. [C.6.]

    There can be very simply defined PCs. [D.1.]

    A Character Sheet may not be needed for a very simply defined PC. [D.2.]

    Degrees of character definition complexity: something of the appearance and something of the items in use; the name, more of the appearance, something of the skills, the social and employment status; a quantification of abilities and assets, the character´s classification; psychological and back-story matters. [D.4.]

    A blog post would cover one part of an episode. [E.1.]

    Comments may determine continuation pass a part´s end point. [E.2.]

    Participants can make suggestions for the following part´s end point situation. [E.3.]

    Players with Main Characters should have in view possible end point situations. [E.4.]

    At a part´s end point, it may be specified what kind of content the comments may have. [E.5.]

    Content of the participants with fewer Storytelling rights can be developed by those with more. [E.5.]

    Participants should have in view the story´s coherence. [E.5.]

    More extensive Storytelling rights mean higher priority of comments content. [E.6.]

    Between content offered with equal Storytelling rights, the dice may decide priority. [E.7.]

    Beside presenting story content, an episode part contains OOC dialog with the participants. [E.8.]

    Play could be moved to the PbP forum section, while maintaining the blog interface with other players than those having Main Characters. [F.]
  2. Erran's Avatar
    Comment Coding - no JavaScript version

    I present here the contents of the ´spoiler´ from Episode 1, Part 1 of Errandûrr´s story, entitled ´Com. Coding´. The purpose is to make them available for future reference, also for those of you who choose to not enable JavaScript in their browsers.

    [OOC: This is about some coding elements you may wish reviewed:

    Please separate each section by placing it in its own paragraph. When ´Going Advanced´, I use < p > (no spaces) at the comment´s beginning, < /p > (no spaces) at the end, and < /p >< br >< p > (no spaces) between paragraphs; except after a list´s ending tag, when I use < /p >< p > (no spaces). When editing a comment, these are no longer necessary; so you may wish to do the formatting after publishing your comment - or, alternatively, not ´Go Advanced´ when writing your comment.

    However, to separate list elements with a new line, you may wish to use < br >< br >< br > (no spaces) in between; as well as before the list ending tag. (Not that I can imagine what you would need to use lists for...)

    Also in my editing experience, < br > (no spaces) before a table element places it on a new line. (Again, you may not need to use tables...)

    When using the --tangledCoffee style, the comments are displayed on a white background. Please use only dark colors for text. The links to my choice of style settings offer a few examples. Also with regard to colors, it is worth mentioning that, in my case (with standard settings - if any), links are displayed in black, regardless of being placed within a ´color´ tag´s scope.

    Please avoid positioning tags, like ´indent´ and ´center´. The comments are usually displayed on a narrow portion of a page´s horizontal direction. To have everything left-aligned (the standard setting) improves readability, I think.

    The following is a list of names of the bb code tags I expect to have the greatest frequency of use. ´b´, ´color´, ´i´, ´img´, ´list´, ´noparse´, ´quote´, ´s´, ´spoiler´, ´table´, ´u´, ´url´. Please refer to their definitions at the Town Crier section of the forum; if needed. ]
    Updated 03-15-2018 at 01:35 PM by Erran
  3. Erran's Avatar
    Comment Structure - no JavaScript version

    I present here the contents of the ´spoiler´ from Episode 1, Part 1 of Errandûrr´s story, entitled ´Com. Structure´. The purpose is to make them available for future reference, also for those of you who choose to not enable JavaScript in their browsers.

    [OOC: This is about the sections that your comment should or could contain:

    Please consider placing all content in one comment for easier processing; an exception case that allows two comments is indicated below. Thank you!

    Now, given the fact that comments here aren´t accompanied by user photos, you may wish to place a link to that, or a (small size) [img] insert in a first section. However, anyone can click on a user´s name to see their photo, so it is entirely up to you to provide the link, or not. I´m just reminding you that the photo is not automatically published :)

    A section after could mention the rights that you are aware you have, named according to the terminology defined in the BPS+ guidelines (acronyms are accepted), and as detailed as I have granted them to you. You should assume you have the rights I specified last for you or your player-category in an episode part, or at least those I specified for all possible participants. If none are specified, you should assume only that you have Story Guest rights. Please refer to the BPS+ guidelines for a rough idea about what those mean. Please precede this section with ´Rights: ´.

    A next section, at future participations, could contain your comments on my decisions with regard to content of yours not being included or with regard to the manner in which it was included. Please precede this section with ´ComProc: ´ (comment processing).

    The section after could contain any opinions on how the story evolved so far; for now you could be referring to the contents of ´Preparations´ and to Errandûrr´s back-story, as well as to the story content published here, if you like. Please precede this section with ´SoFar: ´.

    The sections until this point I consider to be introductory.

    For this simple participation case, it would be sufficient to have one main section of the comment. If and when you will be handling more aspects of the story at the same time, there should be a main section of the comment for each. Please separate OOC content in these sections by using ´OOC: ´ at the beginning, and ´ :OOC´ at the end; assuming that after ´ :OOC´ story content which could be included as it is (in the next episode part) follows. OOC content could include proposed story content that you don´t also provide a desired wording for - just ideas.

    The following would be ending sections.

    One section should contain your comment processing priority dice roll. Please use the name ´Priority´, no quantifier, the dice type %, no qualifier and no modifier; please refer to the Town Crier section of the forum for dice roll code definitions, if needed. Please precede this section with ´PRoll: ´. Please remember that - You Should Not Preview A Post That Contains Dice Roll Code (or you lose the roll forever after) -and that- You Cannot Rewrite A Post That Contains Dice Roll Code. In case you are not sure about your ability to use the code, it may be better to put all dice roll code in a separate comment; you would thus use a total of two comments. (This is the exception case I earlier referred to.)

    Another section, in your future comments, should contain links to character sheets or their equivalent; for characters involved in the story, of course. Please precede this section with ´CSLinks: ´.

    The next sections could contain OOC addresses made towards participants, including me. The information presented here may be of interest also to those who wish to make comments not meant for participation in the story. These sections are for OOC dialog between participants, or between them and the general public (but hopefully that would never be necessary). You can ask me about anything participation- or story-related that you did not understand, or share your personal opinion on such matters, if you feel like. However, if you think that a matter may not be of general interest, I would prefer to discuss it in the privacy of a PM, if you don´t mind. Please precede these sections with either ´@USERNAME: ´, ´@MCOs: ´, or ´@all: ´, according to the corresponding cases (MCOs stands for Main Character Owners; as mentioned in the BPS+ guidelines).

    A few last things.

    It would be nice if each section would have a full-name title, placed after the entry element (´TAG: ´), especially the sections conveying story content. The title could be set in bold, or marked through some other form of style. Between the title and the section´s content you can place a ´ - ´, or a ´ ~ ´, or a short mark composed of a few symbols; preceded and followed by one space (the space after the TAG´s : sign being included).

    You may wish to consider having ´Hi: ´ and ´Bye: ´ sections too.