✎ courierservice:primer

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
Welcome to DX-30's Courier Service!  Your #1 means of delivering packages across the galaxies.  

This is an experimental RPG campaign happening exclusively on our EotE Wiki.  Below you'll find a list of guidelines and tips for enjoying and understanding the story we're about to create.

**Beginner's Luck?**
  * This is my first time GMing a campaign, so please, be gentle.
  * My desire is to have a strong focus on narrative choices and character interactions.  This is partly due to the fact that those are the mechanics of the system I understand best.  
  * Elements of the system I understand less well are mechanics related to combat and the Force, so I don't anticipate those features to be used as often.  If, for instance, our characters do happen to find themselves in an all-out-brawl, there's a good chance that I may run us through a simplified version of the battle, rather than blow-by-blow coverage of each move.  (Combat takes a long time as it is, and a protracted battle happening by post could take up to a month.)
  * I plan on awarding experience at the end of each chapter.  


**What you need to get started**
  * A log-in to edit on this website
Contact Mike to get one of those if you haven't already
  * A character
There is a blank character template on the sidebar (Application form) that you can copy and paste into your own page and then fill in if you like.
  * Dice
I personally like to use: http://game2.ca/eote/# and I have a google Chrome extension that allows me to roll a d100 from the search bar.


**How it will work**
Here's the plan.  We'll see if it works...
  * Every month will feature a new "courier" jobs.  Each of these jobs will be considered one chapter.
  * Each week will be a new scene in the chapter.  Scenes will start around 1am on Saturday and run until 1am on Friday.
  * Each chapter should be divided into 4 scenes, roughly.
  * The expectation is that all characters would participate at least once or twice a week.
  * I don't have the best impulse management, but I'll try to keep my posts to once a day.  This is to help prevent players who aren't on as often from getting left behind.
  * That being said, if you do fall behind in interactions, the nature of the wiki should make it easy for you to insert your character's responses into the scene.
  * It's my expectation that once a scene is done, it's closed.  If at the end of week 3 we decide to leave the casino, I don't expect that during week 4 someone will be able to take an action that occurred while you were sill in the casino.  
  * I've currently set the page up to use HTML tags, which I think will serve us well.  I'm a total novice at this, so if there's a better solution, I'm all ears!  This is what I've cobbled together, but there are probably more eloquent solutions out there.
  * We are currently working at a nice CSS solution that will allow every player to easily denote their entries in the wiki.  

  * As it stands right now, each player will have a wrap that they will use to mark their post.  This way we'll all know that Sean's posts <WRAP rpg sean>Look like this</WRAP> and you'll be told what to roll <WRAP rpg gm>because of this</WRAP>.

An example of how a scene may begin //(borrowing characters and players from the Rebellion campaign)//

<WRAP rpg alan>  Swift has invited Dash and Damaria over for dinner to talk about how bad the Empire is.  They are enjoying food made by the cook droid (like always).  Midway through dessert there is a gentle knock at the door.</WRAP>

<WRAP rpg mike>Dash is alarmed by the rapping and creeps to the door.  He presses his ear to the knotted wood and listens carefully, straining to hear who is on the other side.</WRAP>

<WRAP rpg gm>Roll a Hard (`ch` `ch` `ch`) Stealth check to listen undetected plus one `se` for being startled.</WRAP>

<WRAP rpg mike>Roll result: `su` `su` `ad` </WRAP>
<WRAP rpg mike oc>There is no way Dash is willingly opening this door.  He's learned the hard way to never open the door.)</WRAP>

<WRAP rpg richard>Damaria draws her blaster and covers the door as Dash crouches listening.  </WRAP>

<WRAP rpg alan>Dash can't hear any voices from the other side, but he recognizes the shoes he sees under the door.  He knows that they belong to Baron Telmar.</WRAP>

<WRAP rpg mike>Dash is excited to see his friend and flings the door open.</WRAP>

<WRAP rpg kyle> As soon as he see Telmar, Swift draws his own blaster and fires at the guest.</WRAP>

<WRAP rpg gm>Roll an Easy `ch` Ranged Light check with one `ad` for the element of surprise.</WRAP>

<WRAP rpg kyle>Roll result: `fa`</WRAP>

<WRAP rpg alan>The blaster bolt deflects off of Telmar's badge and strikes a servant in the head, who drops to the ground dead.</WRAP>

<WRAP rpg kyle>Swift's brow furrows as he re-holsters his blaster.  "I didn't care for him either," he says, gesturing to the hired help, laying in the increasingly large pool of blood.</WRAP>

**And that's it.**
I hope that makes sense and will work for us.  Again, this is all highly experimental.  No way to know where it will end up going or if it'll even get off the ground.  But thank you for taking an interest in the project.  I'm looking forward to telling some fun stories with y'all.
Show page