Rules & Regulations

Section 1 Section 2 Section 3   Section 4 Section 5 Section 6 Section 7

Section 8 Section 9 Section 10   

  LAST REV. 11/9/2007

Note: "Commanding Officer (CO)" and "XO" also refers to the equivalent position of Gamemaster and assistant in sims not using military ranks. Regulations mentioning Officers and ranks apply to sims with a military-style organization.

Section 1 - General Rules

I) CHARACTERS: Your character should be original, and not a copyrighted Star Trek, Farscape, Star Wars or other Sci-Fi character, e.g. Jean-Luc Picard, Tripp Tucker, Criton, Dargo, Darth Vadar, etc... (Refer to Section 2) However, the character you chose may be inspired by a copyrighted character. Exception may be made with permission of the Fleet Operations manager and the Gamemaster and if the franchise allows fan fiction. 

II) BEGINNING RANKS: Do NOT give yourself a rank and/or past ranks held by your first character. The Gamemaster of the sim will determine that based on your application & training (See Section 2). At the CO's discretion, an optional point system may be used to promote players within a command. Refer to Section 10 for this system. Exceptions may be made for existing sims entering Python fleet.

III) MINIMUM POSTS:  It is left to the discretion of the Gamemaster to determine what the minimum posting standard is within his/her own command.

IV) APPLICATION: Make sure you fill out your application completely!!!! Remember, the better the Application, the better we can place you within the sim.

V) TRAINING REQUIREMENTS: New members coming into Python Fleet will be trained by the Gamemaster of their chosen sim.

VI) LANGUAGE: Cursing, swearing or the use of colorful metaphors in a sim are left to the discretion of the sim’s Gamemaster according to the rating of the sim.

VII) SIM RATING: Mature themes and posts of a sexual nature are left to the discretion of the Gamemaster. Some PF sims have mature ratings and may have sexually suggestive posts. PF discourages scenes of a completely graphic nature in a sim rated below Adult. Think romance novel and not Hustler. Sexual scenes should be written in taste to evoke emotion, not to evoke pure lust. Acts of violence are allowed according to rating.  Alternative lifestyles are allowed according to rating. It is Python Fleet policy to make no discrimination against race, color, creed or sexual preference.  All are welcomed and encouraged to explore themselves and the world around them. (See Section 8 for rating guide.)

VIII) STORYLINES: Do not start the sim on a new mission. The Gamemaster of each vessel is responsible for that. Doing so will inevitably cause a story split. If you have a mission idea, send it to your Gamemaster. The post that causes a story split will be dealt with according to the Gamemaster's regulations.

IX) NEW TECHNOLOGIES AND CROSSOVERS: While the setting for this "fleet" is primarily in the Star Trek universe, Python Fleet incorporates ideas and elements from other sci-fi shows and novels as well as aspects from the genre of fantasy. If you are going to incorporate something such as a Jedi Knight into a Star Trek sim (for example) please be ready to include a reason why your Jedi is being brought into the story line, and be prepared to offer a back story for this new character to support your reasoning. We want to promote your creativity while doing so in a logical manner.  Try to be realistic when implementing ubertech (super technology).  Super-ships should not become common place. If you wish to introduce any extraordinary technology, please consult the Gamemaster first.

X) PLAYING YOUR POSITION: Keep in line with the current plot, and try to keep up with where the other characters on the ship are. If you are playing a Star Fleet Officer, you are expected to act like an officer. If your character is an engineer, you should be running engineering or attending to related tasks and not overseeing Helm or Ops. If you are playing a Klingon, be a Klingon, same goes for dragons and small fuzzy creatures.

XI) CHARACTER LIMITS: There is no established limit on how many characters you are allowed to play. The only basic limit is what you place on yourself. If you can handle playing three characters and have trouble playing four, then only play three. You are welcomed also to play NPCs as the story warrants, and sometimes even these characters can grow to become permanent characters.

XII) FLEET COMMUNICATIONS:  It is expected that each sim will have a primary chat or mail group client through which they communicate. 

1) Communication with the Fleet Operations Manager (FOM) will be by e-mail, Yahoo messenger (ID Adm_TVer) or other chat clients by arrangement.  

 

2) The FOM's e-mail is betazoid@mosquitonet.com 

 

3) Each sim will notify the FOM of changes in location of boards and websites.

 

4) Announcements of a fleet-wide nature will be posted on Starbase Python's forum at http://www.pfrpg.org/sbpforum/ 

Back to Top

Section 2 - Message Board Rules

1) All Role Play is to be posted on the Role Play Board or group set up by the Gamemaster of the sim.

 

2) The Fleet Operations Manager must be a member of the role-play group as an observer.

 

3) All players shall observe the rules of the Gamemaster when posting on the sim's board/group.   

Back to Top

Section 3 - Individual Rules

1)  Members must use common courtesy with all other members.

2) Individuals must represent Python Fleet in a positive and constructive manner.

3) No player shall malign, insult, threaten, harass or in any other way misuse or abuse another player or the player's character.  Any abuse of other players' characters is forbidden, unless both players agree prior to a post and the Gamemaster is made aware of the pending incident.  This is only allowed to further a storyline. 

4) No player may bring personal problems or problems from other organizations into Python fleet, either in real life interactions with players or in roleplay.  

Back to Top

Section 4 - Failure To Comply With Protocol

I) In the unlikely event that one member severely disrespects, even threatens, another member, or otherwise disregards these regulations, disciplinary action may be taken by the Gamemaster:

1) First offence - Verbal warning and documentation of events.

2) Second offence - Written warning and documentation of events.

3) Third offence - Documentation of events and removal from sim.

Gamemasters who arrive at level three shall confer with the Fleet Operations Manager for assistance and further action.

4) Final offence - Documentation of events and expulsion from the organization.

The Python Fleet Command Staff reserve the right to discharge members from the organization if necessary to preserve the structure and the well-being of the organization and its members.

Back to Top

Section 5 - Chain of Command

I) The ADMINISTRATIVE Chain of Command is as follows:

1) Fleet Operations Manager (the person who owns the Fleet and pays the bills)

2) Sim Commanding Officer/ Gamemaster

3) General Crew Ranks

II) Failure to observe the Chain of Command will result in corrective action according to Section 4.

III) Non-ranked sims are expected to establish a Chain of Command to deal with internal problems.

IV) Due to the multi-universe nature of Python Fleet, there is no military hierarchy above the Gamemaster.  It is requireded, however, that the Gamemaster will communicate changes, concerns, and problems within the sim to the Fleet Operations Manager, Carol Thompson at betazoid@mosquitonet.com 

Back to Top

Section 6 - New Starships and Sims

I) Activation of a new sim in Python Fleet and the assignment of the Gamemaster.

 

     1) A new sim being activated within Python Fleet must be done so with the approval of the Fleet Operations Manager.  

 

     2) Once the sim's Gamemaster is assigned, the Gamemaster's task will be to ensure that the sim's role-play board is created to the set standards of 

         Python Fleet.    A separate website is optional.

 

     3) A minimum of 6 new players must be recruited. 

 

     4) The new sim will post a link to Python fleet's website at http://www.pfrpg.org/ 

 

     5) Python Fleet will post links to the new sim's role-play board and website (if applicable).

 

     6) New sims may run in any timeline or in any universe.

II)  Existing sims: Requirements for an independent Starship, Starbase, or sim of any sci-fi genre who wishes to join Python Fleet.  

    1) Must have at least 6 members.

    2) Must have been simming regularly for at least 3 months or its Gamemaster be an experienced simmer of at least 3 months.

    3) The independent sim must accept Python Fleet rules & regulations in their entirety.

 

    4) The independent sim must accept the Python Fleet Senior Staff and structure in its existing state.

 

    5) The incoming sim will post a link to Python fleet's website at http://www.pfrpg.org/

 

    6) Python Fleet will post links to the incoming sim's role-play board and website (if applicable).

 

    7) Independent sims may run in any timeline or in any universe.

Back to Top

Section 7 - Posting Standards

 

1) Posts should be written in narrative style, that is 3rd person past tense, unless the scene is a log, a flashback, or the character is telling a story. Conversations between characters should be written as if they would appear in a novel, with proper punctuation.  All chat ID's must be stripped from Joint posts and mechanical errors fixed before posting.

 

 

2) Posts and Characters must be as realistic as possible within the universe you are simming in. If you wish personal enhancements or want to introduce a deity into the storyline, please inform your Gamemaster and get permission.

 

 

3) Posts must follow the mission or storyline. or have something to do with it, except for personal posts which may be flash-backs or dreams etc. Duty posts must be made from the standpoint of your rank and position in your department.

 

 

4) Posts must be spell checked and checked for words used out of context before they are posted.

 

 

5) Posts must be no shorter than one full paragraph.

 

 

6) Posts should deal with one incident or a series of related incidents, not a great many incidents which are not related.

 

 

7)  If you find your post becoming longer than 2 or 3 pages, break it up into parts and post them separately or as a threaded topic.  Shorter posts are easier to read.

Back to Top

Section 8 - Standards for Ratings on all Python Fleet Sims

It is required that all sims post their rating prominently on their role-play boards. Sims whose occasional post falls in a more restrictive category will post a disclaimer or alert at the top of the post. (example -  Note: Sexually explicit content)  If the sim finds itself wandering often into more restrictive content, the sim should  be rated to the higher level.

Copied from the following site: http://www.esrb.org/esrbratings_guide.asp which lists ratings for computer and video games

C = EARLY CHILDHOOD
Titles rated EC - Early Childhood have content that may be suitable for ages 3 and older. Contains no material that parents would find inappropriate.

E = EVERYONE
Titles rated E - Everyone have content that may be suitable for persons ages 6 and older. Titles in this category may contain minimal violence, some comic mischief and/or mild language.

T = TEEN
Titles rated T - Teen have content that may be suitable for persons ages 13 and older. May contain violent content, mild or strong language, and/or suggestive themes.

M = MATURE
Titles rated M - Mature have content that may be suitable for persons ages 17 and older. Titles in this category may contain mature sexual themes, more intense violence and/or strong language.

A = ADULTS ONLY
Titles rated AO - Adults Only have content suitable only for adults. Titles in this category may include graphic depictions of sex and/or violence. Adult Only products are not intended for persons under the age of 18.  

Back to Top

Section 9 - Star Fleet Code of Conduct

ARTICLE I
I am a member of Starfleet, fighting in the forces which guard the Federation and our way of life. I am prepared to give my life in their defense.

ARTICLE II
I will never surrender of my own free will. If in command, I will never surrender the members of my command while they still have the means to resist.

ARTICLE III
If I am captured I will continue to resist by all means available. I will make every effort to escape and to aid others to escape. I will accept neither parole nor special favors from the enemy.

ARTICLE IV
If I become a prisoner of war, I will keep faith with my fellow prisoners. I will give no information nor take part in any action, which might be harmful to my comrades. If I am senior, I will take command. If not, I will obey lawful orders of those appointed over me and will back them in every way.

ARTICLE V
When questioned, should I become a prisoner of war, I am required to give name, rank, service number, and date of birth. I will evade answering further questions to the utmost of my ability. I will make no oral or written statements disloyal to the Federation or its allies or harmful to their cause.

ARTICLE VI
I will never forget that I am a member of Starfleet, fighting for freedom, responsible for my actions, and dedicated to the principles which made the Federation free.

Back to Top

Section 10 - Optional Points System For The Promotion Of Python Fleet Members

Promotions may be handled on a point system. Each time you post or contribute to a story line you get points. Each week these points are totaled and added to your total and this will be posted on the list as well as on a page at the site which will be updated weekly. Below is a list of how many points are rewarded for various actions and a list of ranks and how many points are required to be promoted to those ranks. For example when a Lt. (JG) reached 600 points he/she will be promoted to Full Lt. It should be noted that a post must be of 200 words more more to qualify for for ranking points.

Note: All new players start at 0 points regardless of starting rank.

For those of you familiar with paper-based RPGs like Dungeons & Dragons, GURPs, or any of the Palladium System RPGs, you are familiar with the concept of experience points.  This point system is no different than a basic experience point system.

This system is one example out of many.  The Gamemaster is free to institute another point system or none at all, as long as promotions are handled in a fair manner among the players.

Note:  The Marines have no warrant officer ranks.  Naval Warrant Officers are promoted from NCO ranks.  The points will be reset to zero for an NCO that accepts a commission as a warrant officer.  A warrant officer may be promoted to full officer at the discretion of the CO, and the points the warrant officer has earned will carry over to his officer rank.

Revised November 9, 2007