1.1. Star Wars RP: Legends is an original RP-based Star Wars story, but it is also based closely on the Star Wars "canon" (or storyline, as depicted in the films, books, games, etc.), and players are expected not to contradict canon events or significantly alter the Star Wars storyline; for example, Yoda dying before his appearance in the films. However, minor deviations from the storyline are permitted when prudent or necessary. Refer to Wookieepedia or a Star Wars sourcebook for more information on the Star Wars "canon." This is not an "alternate universe" RP.
1.2. Posts should be as detailed and specific as possible; posts should include information about setting, personality, and other useful information (no "one liners," please). In combat, a player must specify where and how he or she* is attacking, and whether or not the attack is meant to be fatal. All attacks must have a reasonable way to counter them (no "moding").
Note: Computer hacking (or "slicing" in Star Wars terminology) shall also be considered an "attack" for RP purposes. 1.3. Upon his "turn" to post on a thread, a player is allowed 72 hours to respond, after which the next player may choose to "invoke the 3 day rule" and confirm any actions in the previous post or other actions as necessary to continue the thread. However, if you provide prior notice that you will be unable to respond within 72 hours, exceptions to this rule will be made. Management reserves the right to post (or "auto") on a player's behalf if, A.) the player is consistently tardy in their responses, and B.) the thread or character in question is deemed important to a major storyline in the RP. 1.4. Players may have as many characters as they want. However, these characters must not "go out of their way" to assist one another or pool their ships, weapons, or money to the benefit of any one character, or that character's faction. No two characters should have identical goals or desires. 1.5. Killing a character against its player's wishes is discouraged, but permissible under two circumstances: 1.) if it is necessary to advance a major storyline in the RP, or 2.) if a character places himself in an easily-avoidable situation in which his survival is harder to explain than his death. Character deaths are final—no cloning or Force "resurrections." 1.6. Any IC (or "in character) events that occur in a chat room or instant messenger must be posted for general viewing on the forum in order to be considered part of the Star Wars: Legends storyline. Events that occur in the chat room without the knowledge of the relevant characters may not be considered part of the story. Star Wars: Legends has no chat room or chat moderators, but the rules apply to events that occur in a chat room or instant messenger the same as they apply to the forum. 1.7. Do not antagonize the sensibilities or beliefs of other players, do not harass or antagonize a character for OOC (or "out of character") reasons, and respect the work that players put into their characters and factions—do not try to kill someone's character or destroy their faction without a persuasive, IC reason. 1.8. Sex or graphic violence should be described implicitly, not explicitly. Keep profanity to a minimum. Profanity is permissible (within reason) if a character is speaking or thinking it. OOC, players should behave on the forums and in the chat as they would in public. 1.9. Characters will not be allowed powers, abilities, or "modifications" such as cybernetics or certain types of armor, with the effect of making that character invincible, or practically so. Neither should non-playable characters (NPC's) have any such powers, abilities, or cybernetics, "power armor," etc. 1.11. Certain planets are considered "off limits" because their appearance in the RP would most likely result in significant changes to the Star Wars storyline. Among these planets; Ruusan, Korriban, and Kamino. 1.12. Although parody and farce has its place in the RP, players are expected not to cheapen the RP for other players through the improbable actions of the characters. In other words, no Jar Jars. Players who do this consistently may be removed from a thread.
2.2. Personal ships and weapons in a character's profile don't need to be requested. Highly-destructive weapons, and large ships with large crews are not considered "personal" and must be requested. 2.3. Ships, weapons, or other items that were previously requested and approved for one character must be re-requested if sold, stolen, or otherwise transferred from one character to another. 2.4. Corporations in the RP will be placed into the following categories: Class 1.Class 1. A small-sized company operating on a single planet. Class 2.Class 2. A medium-sized company operating on multiple planets in one sector. Class 3.Class 3. A large-sized company operating in multiple sectors. May have Class 1 Class 3.Class 3. and 2 subsidiary companies and sector-specific security forces. Class 4.Class 4. A large-sized company operating in many sectors with competitively- Class 4.Class 4. priced products and services. May have Class 1, 2, and 3 subsidiary Class 4.Class 4. companies, including canon companies, and inter-sector security Class 4.Class 4. forces. Eligible for Senate representation. Class 5.Class 5. An immense, galaxy-spanning corporation. Usually ancient. May have Class 5.Class 5. Class 1, 2, 3, and 4 subsidiary companies and a full-scale army and Class 5.Class 5. navy. Eligible for Senate representation. Each advancement from one category to the next must be requested and approved, based on the success of the corporation and the player's efforts at corporate expansion in the RP. 2.5. Any request for custom-made species or ship designs must be accompanied by an image. 2.6. Requests may not be made in private. There must be a posted, publicly-available record on the Requests forum. 3.1. The catastrophic destruction of planets, property, or large numbers of people with superweapons, orbital bombardment, the Force, chemical or biological weapons or "plagues," or by any other means is not permitted, except as a plot device and with management approval. 3.2. Starfleets in the RP should be composed of a reasonable number of ships, proportional with other fleets in the RP. Fleets should be sufficiently large enough for the defense of one's own planet or faction, or to attack other planets, but not large enough to effectively defend one's own planet and attack other planets simultaneously. 3.3. Most worlds belonging to the Republic or to other factions in the RP are assumed to have an unspecified number of starfighters, gunships or other small ships, or space defense platforms, to be specified as needed in the RP. These ships or defense platforms, etc. shall be used only for the defense of that particular planet.
3.4. Numbers of ground forces should be referred to in terms of "regiments," "battalions," etc. that a player is using in a particular battle. The standing army of an entire planet can potentially number in the millions, even billions of troops—listing the total number of them is not necessary, or desirable. 4.1. Players are encouraged to use only those Force powers featured prominently in the films, and certain
books and video games (such as "Pull," "Push," "Grip," "Speed,"
"Lightning," "Absorb," or "Meditation"). Lesser known powers (such as
Sith "spells" or "alchemy"), catastrophic powers (such as "Storm,"
"Thought Bomb," or "Deadly Sight"), or any Force powers used with
catastrophic effect are not permitted except as plot devices and with management approval.
4.2.
In addition to the "basic" Force powers, Jedi or Dark Jedi characters
should have no more than 2 or 3 specific Force powers or techniques at
which they are particularly skilled. No one, not even Yoda or Darth Plagueis, can be expected to master more techniques than this.
The more Force powers your character studies, the less proficient,
overall, your character will be in all of these powers.
5.1. Players may have as many Senate characters as they wish, but only two may vote on any one measure. 5.4. New bills or resolutions may be proposed by any Senator or Representative and must be debated and passed by a simple majority vote. The Supreme Chancellor decides when the debate/voting period is over. The Chancellor has the authority to veto acts of the Senate only for the security and stability of the Republic. The Senate, in turn, may override a veto with a 2/3rds majority vote. 5.5. A "motion of confidence" or "vote of no confidence" may be filed if the Supreme Chancellor is no longer fulfilling his duties or is conducting himself in a manner unfit for his office. Such a motion must be proposed by one Senator and seconded by another (neither of these characters belonging to the same player). A confidence vote requires a 2/3rds majority to pass. 5.6. Name-calling and other outbursts should be restrained in the Senate Rotunda. If a Senator, Representative, or Ambassador is out of order, the Supreme Chancellor may issue a "Call to Order" against that Senator, Representative, etc. If the Senator violates a "Call to Order," the Chancellor may suspend the delinquent member for up to 7 days, OOC. Once suspended, that delegate cannot participate in Senate discussions or vote on any proposed measures. 5.7. Any Senator, Representative, Ambassador, etc. may be expelled from the Senate by a 2/3rds majority vote. 5.8. Before addressing the Senate, speakers who are not Senators or Representatives must request to speak and be recognized by the Supreme Chancellor or by a Senator of Representative (except when a new candidate is requesting admission to the Senate).
5.9. The Supreme Chancellor has the authority to appoint the chairmen of the various Senate committees. Each chairman, in turn, has the authority to appoint the members of their committee. Additional committees can be established by a simple majority vote of the Senate. 5.10. The Senate must approve, by simple majority vote, any movement of Republic judicial ships from one "Rim" to another (the Outer Rim, Mid Rim, etc.). The Chancellor, however, may dispatch ships wherever he chooses within the Rim where they are currently stationed, without Senate approval. 5.11. The Chancellor may, without the approval of the Senate, direct an Admiral of the Core Worlds to requisition a planet's naval forces into Republic service, under the Admiral's command, as needed for a particular military action. However, the Senate may, by simple majority vote, direct the Admiral to relinquish his command of those forces and return them to their planet. 6.1.
Management shall be comprised of one Administrator and no more than three Moderators. Each has one vote on requests and rulings, which shall be decided by a majority of Moderators and the Administrator. However, the Administrator can veto any ruling on which the Moderators are not unanimous. 6.3. When commenting on a player's request, a Moderator or Administrator
should provide thoughtful and respectful feedback to the player, and
explain the reasoning of his or her decision, citing specific rules or
canon events as necessary. Moderators and Administrators should also
review character profiles (specifically history, weapons and abilities),
and be vigilant of the forums and the chat for profanity or harassment. 6.6.
Moderators or Administrators demonstrating a consistent bias in favor
of themselves, or in favor of (or against) specific players, will be
removed from management with or without prior notice; abuse of power
will not be tolerated. In the words of Chance Allison; "Enforce the
rules, no matter how much you'll be hated." In the rather more eloquent
words of Lucius Calpurnius Piso Caesoninus, "Fiat justitia ruat caelum." ("Let justice be done, though the heavens fall"). * For simplicity, these rules refer to "he or she" simply as "he." |