The player handbook is also available as a paperback-sized PDF.
Welcome to Outpost Hope One, a part of Star Trek: Borderlands. We are a collaborative group that write stories using original characters within the Star Trek universe. Outpost Hope One is one of several duty stations that make up Star Trek: Borderlands. Each is independant although we maintain a consistent universe amongst ourselves and do crossover from time to time. After 25 years as a group, we have created our own history and our own canon.
This guide will summarize what you need to know to join the fun as quickly as possible, and, to answer your questions about your character, your fellow players, posting etiquette, etc.
The universe of Star Trek is a collection of thousands of hours of television and film and hundreds of novels. Players are more-or-less on the same page as Star Trek fans. What defines canon within Star Trek has changed over time. Even Gene Roddenberry changed his opinion over the years. In general, television trumps film and novel, and, later television series trump earlier series. Over 25 years, Star Trek: Borderlands has also developed it's own Star Trek brand.
Outpost Hope One (OH1) canon includes content from all television series (Original series, The Next Generation, Deep Space Nine, Voyager and Enterprise). Content from feature films is acceptable although it's style of storytelling is notably different than that of the television series. OH1 excludes content from the Abrams film relaunch due to it's blatant break from previous canon. Content gleaned from the hundreds of novels may be included with the caveat that critical details are conveyed to all players beforehand because few players will have read a particular novel. Star Trek Online content is acceptable as long as it is consistent with broader canon.
Content produced by Outpost Hope One (OH1) and Star Trek: Borderlands (ST:B) overrides the broader canon in all cases. Players have been writing together under the ST:B banner for over 20 years and their work stands.
Players should avoid using technology or terminology from non-Star Trek franchises. Star Trek has a strong technobabble tradition that can borrow out-of-franchise. For example, Iconian Gateways instead of "stargates", tricorders instead of "sonic screwdrivers", quantum filament blades instead of "light sabres".
Star Trek: Borderlands (ST:B) is a group of duty stations (DSs) scattered across the Delta Quadrant (DQ). The commanding officers (COs) of each DS create a larger universe within which to write. A list of DSs is available on the Outpost Hope One (OH1) website.
Star Trek: Borderlands (ST:B) includes multiple United Federation of Planets stations and ships, a Romulan Star Empire Ship, a Delta Freedom Alliance ship (unique to ST:B), and, several civilian ships. In the past, DSs have included Klingon ships and planetary governments.
Outpost Hope One (OH1) is located in the Delta Quadrant (DQ) about forty years after USS Voyager reached Earth.
Star Trek fans take on the roles of characters to write their own stories as a group. Stories are written incrementally with a fluid storyline. Outpost Hope One's (OH1s) commanding officer (CO) directs the overall story but every player fills in the details. The story is defined by what each characters says and does.
There are different ways to describe Star Trek: Borderlands (ST:B): play-by-mail (PBM), play-by-email (PBEM), roleplaying game (RPG), simulation (sim), etc.
Hundreds of fans have written their own collaborative Star Trek fiction in one of the most creative groups on the web.
There is no cost to join or play. The OH1 website is hosted at the commanding officer's expense; most duty stations use free or ad-supported hosting. The posting group is hosted by Yahoo!Groups and is ad-supported. At no time will monies be requested of players.
Outpost Hope One (OH1) cannot reliably verify the ages of players. Players must be 16 or older. Age can only be presumed from the maturity of a player's writing. Profanity, vulgarity, crude humour, substance abuse, graphic or cruel violence, and, strong sexual content are rare within Star Trek. Content that goes beyond what can be depicted on television must be discussed with the Commanding Officer (CO). As a narrative medium, a character's reaction to violence, for example, can replace a description of the violence itself.
All writing in Star Trek: Borderlands (ST:B) is third-person, omniscient past tense; the most common style in fiction.
Players cannot write in first-person.
Players write what their characters say, their actions and what they think. A character's thoughts are as important as their actions and dialogue.
Each month, Outpost Hope One's (OH1s) commanding officer (CO) posts a summary of stories-in-progress. The Captain's Log is shared with all players via the posting group and every other CO within Star Trek: Borderlands (ST:B). This is the best place to learn the goings-on at OH1.
Players communicate entirely by email.
Yahoo!Groups hosts our posting group (also called a discussion group; old timers call it a list server or listserv). All emails sent to the group email address, firstname.lastname@example.org, are forwarded to every other player. Each email adds to the stories-in-progress. Every email is archived by Yahoo!Groups at https://groups.yahoo.com/neo/groups/SentinelStation/info is open to the public. Players can read posts as far back as 2001 when Star Trek: Borderlands (ST:B) migrated to Yahoo!Groups (known as eGroups at the time).
Non-roleplay (NRPG) and out-of-character (OOC) discussion is hosted by another group, https://groups.yahoo.com/neo/groups/OH1Discussion/info. Players communicate with each other as themselves rather than as the many characters they portray. Emails are sent to the group email address, email@example.com. The non-roleplay (NRPG) archive cannot be accessed by the public.
As a member of Star Trek: Borderlands (ST:B), Outpost Hope One's (OH1s) has four seats (commanding officer (CO), executive officer (XO) and p to two player representatives) on the Borderlands Council. The council coordinates communication and story amongst duty stations (DSs), decides on policy and manages recruitment. Any player may join the Borderlands Council with the permission of their commanding officer (CO) in consultation with his or her executive officer (XO).
The Star Trek: Borderlands Constitution is the document that defines the powers and responsibilities of the Borderlands Council.
Joining Outpost Hope One (OH1) is not like picking up an episodic television series. Stories overlap with each other and play out over the course of weeks and months. The Captain's Log provides a good summary for new players. Characters may enter the story in a natural break in the narrative. For example, the appearance of an unknown ship requiring the expertise of a (previously unknown) tactical officer or engineer. A character can be shoehorned into a story. For example, entering the scene from the rear compartment of a runabout as if they'd been there the whole time. The commanding officer (CO) will always find a place for a new character.
Players are expected to post every two to three days. Each post will take 15 to 60 minutes depending on the complexity of the storyline. As a collaborative medium, we rely on each other to reply timely to posts so that the story can progress. Long delays slow down the story and make it difficult to move ahead.
After five days, the commanding officer (CO) will contact players with unanswered tags. Some allowance is given to posts with tags for multiple characters; the story may not be stalled if one player takes a few extra days. An unresponsive player may find their characters' tags have been written around and the storyline continued without their characters' involvement.
Players stepping away from Star Trek: Borderlands (ST:B) should inform their commanding officer (CO) or executive officer (XO).
A short-term leave of absence (LOA) may be because of a real-life vacation or crunch time at work. That player's characters are not tagged in the meantime.
An extended leave of absence (ELOA) involves stepping away from Star Trek: Borderlands (ST:B) for more than two weeks or for an indeterminate length of time. That player's characters are noted as ELOA on the website and are not tagged.
After 5 days with unanswered tags, players will receive an inquiring email from their commanding officer (CO). If no reply is received within 5 days, the CO will assume said player has withdrawn from Star Trek: Borderlands and will work with other players to exclude unanswered tags, remove that player's characters from the website and inform the duty station (DS) as a whole. At the CO's discretion, the player may remain on the mailing list to facilitate their return in the future.
Under no circumstances may one player write in the voice of another player's character. Player's have spent time effort to create a character, their personality and backstory. It is wholly inappropriate to hijack a character. Character's are the creation of their player.
Players breaking this rule greviously or repeatedly will be moderated by the commanding officer (CO) — all posts reviewed by the CO before they are visible to the duty station (DS).
Ranks for new players are assigned by the commanding officer (CO). Typically, new players begin with a character ranked Crewman, Private, Corporal, Ensign, Lieutenant (Junior Grade), or 2nd Lieutenant. A new player may also begin as a civilian character. Characters in a position of authority are reserved for more experienced players. As a player gains experience, their characters receive promotions.
Players may write as more than one character at the commanding officer's (COs) discretion.
Players with more than one character are more involved with the duty station (DS). There are no Mary Sue characters; characters that fill every role with equal expertise, knowledge and likability.
A player's second or third character should have the same depth and complexity of backstory and personality as their primary character. Every character should meet a high standard.
Short-term, temporary characters are required from time to time to populate stories. For example, a Johvan farmer may be useful in a particular story but does not have long-term prospects in multiple stories. A player can scale up their involvement with Outpost Hope One (OH1) temporarily with short-term characters.
In the first six months, a player may only write for a single duty station (DS). It is important to gauge the demands of writing over a number of months before taking on the additional workload. Writing for multiple characters and writing for short-term characters are a litmus test for deeper involvement in Star Trek: Borderlands (ST:B).
Players must maintain their commitment to Outpost Hope One (OH1); writing for a second DS must not negatively impact Outpost Hope One (OH1).
The date system used by official Star Trek properties is based on that used by Star Trek: The Next Generation (TNG).
Star Trek: Borderlands (ST:B) uses a simpler, easier-to-read system. Today is November 1, 2015 which can be re-written as 2415.11.01. The year is adjusted to reflect that Star Trek: Borderlands (ST:B) takes place exactly 400 years in the future.
Every post to the Outpost Hope One (OH1) posting group follows a specific pattern.
The posting group's name is automatically prepended to every post. For Outpost Hope One (OH1), these are [Outpost Hope One] for in-character (ie. roleplay, RPG) posts, and, [OH1 Discussion] for out-of-character (ie. non-roleplay, NRPG) posts.
The posting group name is followed by the date of the post. (see Date System)
When a character writes multiple posts in a day, the post date is appended with an index. For example: 2415.11.01.01 for the first post by a character that day and 2415.11.01.02 for the second post. The index is by-character rather than by-player.
The location of a post is included as a three-letter abbreviation. There are two major locations where stories take place:
Some locations are used less often:
Sentinel Station is quite large and some sections have their own abbreviations:
A character's short name is included to clarify the speaker. It is usually the surname for Human and Andorian characters and given names for Bajoran characters. Some species use only one name.
The final element of a subject line is a title for the post. It can be descriptive or tongue-in-cheek.
Putting it all together:
2415.11.01.01 SEN Mirel "Taking command"
is a post written on November 1, 2015 with the action aboard Sentinel Station written from the point of view of Commander Mirel (her first post of the day) and a title implying she is taking command.
2415.11.03.02 SEN Eiwan "Still broken"
is the second post written on November 3, 2015 aboard Sentinel Station written from the point of view of Chief Petty Officer Himpanwei Eiwan complaining about something still being broken.
Every post includes a header to identify key details:
The subject line provides a short, three-letter acronym of a post's location that is expanded within the post header. For example, OPS in the subject like is expanded to Location: Operations Centre (Ops) in the header.
The timeline of a post may be simply Timeline: Current or include detail relating it to other stories in-progress. For example, Timeline: After USS Hunter arrives or Timeline: After the reception.
Every character that has participated in a thread is listed.
Characters with pending tags are also listed as a reminder for players to reply to the post. When a player is writing a reply post, he or she removes their character's name from the Tags line and adds the names of characters he or she is, in turn, tagging.
Putting it all together:
Every post requires a signature that identifies the character in whose viewpoint the post is written. The only requirements are the characters name and the players name. It can be as simple or as elaborate as the player decides.
When replying to a post, the content of the email should be copied and pasted into a new email. Clicking REPLY will change the style of the post (eg. indent it, change it's colour, add a vetical bar along the left edge). A newly composed email will retain the previous post correctly.
Tags should be replaced with bold text to clearly mark new content. Existing text should be plain, black text.
The header, open tags and signature may also be bold text so that they stand out.
Players using a mobile device may write *NEW* at the start of the first tagged post to indicate new content where making the text bold is impractical. There should be only one *NEW* tag in each thread to mark the latest new content.
Tags indicate where a response is expected from another character. They may be single-chevron, <Character's Name>, or double-chevron, <<Character's Name>>, brackets.
A player should leave at least two open tags in a post. The bottom-most tag in a post can open the story to any character by using an <Any> tag.
A player may direct the story by placing tags in the middle of a post. For example:
Each player has their own preference for the amount of direction they like to receive. Too many tags, tags that force a pat response or force a character to react uncharacteristically should be avoided.
Some players use non-standard forms such as Tag: Name or (Name) or [Name]. They are not to be used within Outpost Hope One (OH1).
Players may also add out-of-character comments to ask questions, make recommendations or provide information to other players. They can appear at the top of a post, the bottom of a post or mixed in with the text. They follow the form (OOC: Content) or (NRPG: Content). For example:
Players may write alternative content depending on how a character reacts. For example:
Characters communicating via comm badge or ship-to-ship use a “comm badge” character rather than double-quotes.
It is important that players are aware of what is happening in and around Outpost Hope One (OH1). Players are encouraged to participate in storylines where their characters can contribute. It's impolite to expect other players to read one's own contribution to the story without reciprocating by reading every other player's contributions.
Occassionally two players will reply to the same post at the same time with one player's content not included in the other's reply, and vice versa. The first player to notice should notify the CO to repost a combined reply or repost themselves and add [Repost] or [Combined Post] in the subject line.
If combining posts would create an inconsistency, a player should still combine the posts, add an out-of-character note about the contradiction and refer it to the CO to resolve. For example: the appearance of a Klingon ship as written by one player and a Romulan ship as written by another.
Overly long threads can be trimmed by replacing the oldest content with >>SNIP<< or [Snip] or another indicator that a thread has been snipped.
When a thread has reached it’s narrative conclusion, players may request a thread be ended with an out-of-character tag. For example, [OOC: End here?] or <That’s a wrap!>.