|
Below are the rules and guidelines for participating in the Star Wars - Tales from the Outer Rim simulation. Any questions about posting requirements, character interaction, or post formatting should be found below. If you have any questions, send an email to the GM. 1. Posting Length Posts should be a minimum of four paragraphs. In general, you can't really say much in just a couple paragraphs. A lot of times, not much can be said in only four paragraphs.
2. Paragraph Format Paragraphs should NOT be indented. Additionally, a blank space should be left between all paragraphs. When sending out your posts, make certain your email program is configured to send in "Plain Text." If you are uncertain how to change the settings in your email, let me know.
Because posts are sent in plain text formatting, there is no way to emphasize text. So, in those instances when you would like to have text emphasized in some way, use the following:
3. Styles and Attachments With most email programs capable of sending out posts using rich text and HTML formatting, it may be tempting to send your posts using that format so that you can use some of the features of those styles. Don't.
Not all email programs are created equal, and not all email programs interpret rich text in the same way. What looks great on your computer may look like garbage on someone else's. So, please avoid sending in any format but Plain Text. Additionally, if you use Microsoft Word to format your posts, be very careful. By default, it is designed to change certain text combinations and punctuation that is not readily viewable or translatable in Plain Text. If you use Word (or any other editor that makes these automatic changes), we strongly recommend that you either disable that feature or change to a different editor. Attachments should never be sent to the Tales from the Outer Rim mailing list. Not only do most computer viruses travel as attachments, but they're difficult to work with due to differing file formats. So, when sending messages to the list, make sure you're not sending attachments. If you've written your post in a different program, just copy and paste the text from the other program into your email message. 4. Narrative Format Posts should be written in third-person, past tense.
Example: From the cockpit, Liam grinned. He plugged the data Yelara had given him into the computer. They'd be able to pull up the information from the device from any station on the Kestrel. "Perimeter security is still green," he said. "No one knows we're here. But, I'd like to keep it that way, so I'm taking us away." His hands flipped through the knobs and switches on the pilot's console and the Kestrel climbed upwards in the atmosphere. 5. Punctuation, Capitalization, and Spelling Every attempt should be made to use punctuation and capitalization in your posts. In a sim that allows global membership with such widely varying levels of skill with the English language, perfect English won't be required. However, it is much easier to read a post with punctuation and capitalization in the proper places. Also, be certain to spell-check your posts.
For new players, and players wishing to bring in additional characters, make sure you proofread and spell-check your bios. 6. Member Posting All members of the sim are expected to submit at least one in-character post every two weeks. If you find you are unable to maintain this posting frequency, you should contact the GM and discuss a means to keep yourself active in the sim.
Any member of the sim who fails to either submit a post to the listserver or notify the GM of an inability to meet the posting requirements for a period of one month will be removed from the sim as inactive. 7. Joint Posts and Character Interaction Any interaction between characters should be contained within a single, completed post (or more if the post is very large), not spread out over a dozen small posts. Do not end your post tagging another to pick up in a conversation. Your character should never injure or harm another player's character without that player's consent. If your character and another character get into a fight, and neither you nor the other player can decide who wins the fight, the fight should end in a draw. 8. Post Headings Make sure your posts all contain the proper heading. It should include a title and all the player characters involved. If you write a post with several NPCs, do not list the NPCs in the heading unless they have a significant contribution to the post. Character occupations are not necessary, and are optional for the header.
When the posts are archived, they are archived by date. Because of this, including a date in the headers of a post is very important. If you send out a post without a date, expect a message from either the GM or AGM. Headers should follow the following format: "Title" A normal post written by one author should look like this: "The String Is Cut" A joint post written by two authors should look like this: "Turren Honeymoon, Part 1" The use of "by" and "and" may be eliminated for the header if you wish. But, the other information should be included. In a joint post where one player writes for a player character and another writes for an NPC, use the following format: "Competition" 9. Dates and the Karadan Calendar The Karadan calendar is composed of nine months, each consisting of twenty-eight days. The current year is 4ABY (four years after the Battle of Yavin). The months (from the beginning of the year to the end) are: Praeda, Niothe, Eos, Selene, Saris, Thaniss, Lythe, Vadris, and Rheudis.
You can find the current date by looking at the Archive page. The last linked date will be the current one. When working on your own posts, make sure you don't get too far ahead of the current date. We're trying to keep a steady pace with the sim, and if a storyline pushes too far ahead it could have an effect on other stories. 10. A long time ago, in a galaxy far, far away... Star Wars: Tales from the Outer Rim is set in the Star Wars universe. The technology used in posts and stories should reflect that genre. Weapons should be energy weapons, comlinks are used to contact one another, and ships should have hyperdrives. If you are ever in doubt whether something you're going to add to a post belongs there, just ask yourself: "Could I see something like this being shown in a Star Wars movie, comic book, or novel?" If you can't picture Luke Skywalker pulling out a 9mm semi-automatic pistol with integral laser sight, then you don't want to add it into your post. If you can't see Han Solo whipping out a cellphone and making a call to Chewbacca in the Millennium Falcon... You get the idea. When in doubt about the technology, turn to the Star Wars films, novels, and such.
11. Multiple Characters Some players on Tales from the Outer Rim have multiple characters in the sim. In order to be eligible to add in a second (or more) character, you will need to prove that you can handle the character you already have on the sim. For the first month after joining the sim, all players are limited to only a single character, plus any NPCs associated with that character. Once a player has proved that they can handle their current character, they may request to add a second character. The GM and AGM will review the player's posting history, and decide if they feel that the player can handle the additional posting a second character will require, they will okay the player to add a second character. Then it's a matter of going through the normal creation steps for the bio.
Truly enthusiastic players may add more characters as long as they can prove that they are capable of handling the additional characters. When a player leaves the sim, their character will be placed on inactive status. These characters will not be available for use as player characters on the sim. 12. PC, NPC, NPC+
13. Jedi and Force-Sensitive Characters
14. The Point of It All The point of simming is to have fun. These rules and guidelines are to help everyone have a fun time in Tales from the Outer Rim, and yet still maintain some order in the sim. If you have any questions, contact me.
|