Pegasus Fleet Policies

Revision as of 03:09, 8 June 2015 by Emily Quinn (talk | contribs) (Restricted Characters Policy)

This page has been adopted by the PFA as an official policy.

Here, the official Pegasus Fleet Policies are listed, including the issue date and any further relevant dates (such as revision/voiding dates).

Restricted Characters Policy

Whilst Pegasus Fleet recognises and welcomes a wide array of variety in the characters that are included within, there are some races within the Star Trek universe that are simply too powerful, or would have no place In-Character on a sim within the fleet. As such, the Pegasus Fleet Admiralty enacts the following list of characters and races which are restricted from sims for use for player characters in the fleet, pending approval from the sim's CO and the Pegasus Fleet Admiralty:

  1. Shapeshifter (Changelings, Chameloids, 8472...)
  2. Androids, Augments or mobile emitter-equipped Holograms.
  3. Races from the Delta Quadrant.
  4. Races from the opposing side of recent wars or of a hostile nature to Starfleet.
  5. Characters with physical or mental powers beyond those shown by major characters on the shows/movies (Excluding other restricted or disallowed races)
  6. Characters from official sources, or their relations.

The following characters or races will be disallowed for all player characters.

  1. Borg, unless free from the collective.
  2. Q, half-Q, Q in human form, etc
  3. Any race that is prohibited from any form of contact with other races, such as the Talosians.

Pegasus Fleet recognises that at times races or characters on this list may be an important aspect of missions sims within the fleet run. As such, this list only applies to active Playing Characters, and does not restrict the use of mission-specific Non-Player Characters (NPCs). If you are unsure whether a character or a race would qualify as a restricted race, then you may consult with the next step up on your Chain of Command, who will attempt to clarify on a case-by-case basis where required. If a player wishes to use a restricted character or race, it can be used if it approved by both the sim's CO and the Pegasus Fleet Admiralty. If the CO approves of the character, the player and CO must submit a request directly to pfadmiralty[at]pegasusfleet[dot]net with at least the following:

  • Name of your ship
  • Name of the proposed character
  • Character that you wish to allow
  • Reasons for the player wanting to use this character. Please give as much detail as possible.

Once the proposal is received, the Pegasus Fleet Admiralty will discuss the proposal and may ask you questions regarding it before voting on it. Once the vote is complete, you will be notified of the decision as quickly as possible.

Issue Date: 9th July 2010
Updated: 6th May 2015

Equal Opportunities Policy

Pegasus Fleet firmly believes that people should not be subject to discrimination or harassment, and that equal opportunities are paramount to the fun gaming environment that is meant to be the goal of the Pegasus Fleet.

We therefore work fervently to prevent discrimination against any person or group of persons on the grounds of race, colour, ethnicity, nationality, sex, sexual orientation, appearance, disability, religious or political beliefs, illness, marital status, or age, save that persons under the age of 13 may not join because of COPPA (or similar as proper for their locality) regulations, and that certain sims within the fleet have been granted higher age restrictions that have been authorized as per the Sim Rating Policy.

Pegasus Fleet will view any violations of this policy with the utmost seriousness, to the point that violators will face expulsion from Pegasus Fleet unless it is believed that the severity of the offence does not warrant such action.

Issue Date:

Internet Relay Chat (IRC) Policy

  1. Try not to offend people. While moderate swearing and violence is allowed, users must control themselves and remember that this is supposed to be a PG-13 environment and that others in the room may not find it acceptable.
  2. Try not to be easily offended. Often, some things that are said that can be taken in multiple ways. Without hearing it spoken by a human voice, some things can be taken negatively when in fact no such bias was intended. If you find something being said that's offensive to you, stop a moment and think about other ways it could be meant.
  3. As a courtesy to others, conversation is only allowed in English. Should users wish to speak in another language, they are advised to converse in either a private message or another room.
  4. Recruitment of players for sims or other games is strictly prohibited, with the exception that the Admiralty may post a link for the ship most in need in the room's topic.
  5. Debate on topics is usually encouraged, however if the discussions make any of the users uncomfortable or the debate gets too heated, Channel Operators will call for a halt of any such discussions.
  6. Harassment and abuse of fleet members, visitors and other parties is strictly prohibited.
  7. While in the channel, you should try to stick with using the same nick(name) or variations thereof (eg. If your nick is Tom, Tom|afk is fine) whenever possible.
  8. Using a different nick and pretending you aren't you will not be tolerated. The ops have been provided tools that allow them to see who someone is.
  9. Fleet members and Visitors alike are asked to respect Fleet Laws while visiting this channel.
  10. If in doubt, you should err on the side of caution or consult with the Operator(s) present in the channel.
  11. The authority of channel Operators is unquestionable. Any and all users shall submit to their authority instantly should they be called to do so. The channel Operators are responsible for the maintenance of good conduct in the PF IRC channels.
  12. Channel Operators may make other rules at their discretion to promote good conduct in the IRC channels.
  13. Any user found contravening these rules are liable in the first instance to the full IRC disciplinary powers of Operators (i.e. kicks, bans etc.).
  14. Should a serious breach of conduct occur, proceedings may be started before the JAG. Users may also appeal the verdict of an Operator up the Chain of Command as established in the Fleet Constitution.
  15. Operator or voiced status is at the discretion of the PFA as a whole and is not necessarily granted with or associated with any positions in the fleet.
  16. Bots and Triggers other than those approved by the Fleet will not be allowed in any of the official Fleet chat rooms

Issue Date:

Judicial Code of Practice

See Judicial Code of Practice

Issue Date:

Leave of Absence Policy

  1. If a Fleet Member thinks that they may be unable to fulfil their duties for a time, then they should ask their superior for a Leave of Absence (LOA). LOA requests must state when the Fleet Member expects to both leave and return. Superiors should not refuse a proper request for LOA. Similarly, personnel should not abuse the LOA system. The Fleet recognizes the following types of leave:
    1. Leave of Absence- This type of absence is where a Fleet Member will not be able to perform their duties. This is a short term absence only and the Fleet Member's position will be preserved. Standard LOAs do not excuse the Fleet Member from the need to file any report required of their position.{Time Frame: 1 week – 1 month}
    2. Extended Leave of Absence- This type of absence is where a Fleet Member will be away for an extended amount of time and unable to perform their duties. In cases where the absence is greater than a month's time, it is not reasonable for the Fleet Member to continue to hold their position, however, upon their return, they may petition their superior to return to their position, or if that position is no longer available, an equivalent position that they are qualified for within the Fleet. If such a position is not available, then they will be put on a waiting list and will be considered as the primary candidate for any such positions that may become available. {Time Frame: 1 – 3 months unless specific}
    3. Absence Without Leave- This is not actually a type of leave, but needs to be noted. If a Fleet Member, through absence, has not lived up to the duties expected of their position in the fleet for a period of no less than 1 month, then they may be removed from that position at the discretion of their superior.
    4. Emergency Leave Without Notice - Sometimes life sneaks up on us without notice and at these times, there may be no way that a Fleet Member can make the proper notifications. In such cases, it is likely that the Fleet Member will be removed as AWOL. If that Fleet Member returns with a valid reason for their absence before 3 months of absence have expired, then they may petition their superior to return to their position, much like with the similar provision under ELOA. If they return after 3 months have expired, such petitions must instead be made to the PFA instead.
  2. Who needs to be informed?
    1. Their Subordinates- A Crew will need to know that the Executive Officer will be running the sim for a bit, and will be handling from New crew Applications to Mission completion. CO's under a TGCO will need to know that requests should be passed on to a higher level. Admiralty should inform at least the staff members directly under them.
    2. Their Immediate Supervisors - Whether this is their TGCO, TFCO/CFCO, The PFA or the PFCO. This person needs to be notified of your LOA so that they can keep an eye on your duties and assist your Subordinates if need be.
    3. Department of Personnel Management- This person needs to know so that new applications for the ship can be re-routed, either to the ship's XO, or to another ship, and to update the LOA Logs kept by the Fleet.(COs and up only)
  3. What is considered abuse of the LOA system?
    1. Chaining multiple LOAs together in such a way as to exceed the time limits on LOAs or ELOAs. While extensions can be granted up to the limits of the appropriate type of LOA when needed, chaining them together beyond the limits is considered an abuse of the system.
    2. LOAs may not be used to evade disciplinary actions or proceedings. If the character is under the effects of a strike or other timed disciplinary measure, then at the point where the LOA is requested, or at the start of their absence in the case of an ELWON, the countdown of that measure will be put on hold until such time as they have returned from leave. If they are under the effect of such a measure, it is grounds to refuse a petition such as are found under I.2 and I.4.
    3. LOAs for only certain characters, whether Playing or Administrative (PFA, Fleet Staff) and not other characters that the Fleet Member may have. If they request LOA for one, they must request it for all of them.
  4. What is required to be in a Leave Request?
    1. The Names and Positions of all characters, whether Playing or Administrative.
    2. The beginning AND ending dates of the leave.
    3. The reason for the leave.
    4. Additionally, upon your return from leave, you should contact all the people you told about your leave and inform them that you have returned to duty.

Issue Date: 15th December 2010

Recruitment Policy

Just as there are great ways to recruit that will give your sim good publicity, there are bad ways to recruit that will give your sim poor publicity. As such, the Pegasus Fleet Admiralty enacts the following list of recruitment and advertisement which are disallowed from sims in the fleet, effective on the date this policy is passed:

  1. Recruiting in places (Chat Channels, Groups, Boards, Other Games) not specifically made for advertising or recruitment purposes
  2. Spamming IM lists, Email address books, or Group/Board/Members lists for advertising or recruitment purposes
  3. Opening another Sim for the sole purpose of advertising or recruiting for your PF sim
  4. Advertising on behalf of other CO's unless a member of the Recruitment Department, or that CO's Players, TGCO, or TFCO
  5. Advertise other Simulations in a negative fashion to gain kudos for your own sim

One thing to remember is to know who it is that you are recruiting. If you are good friends with them, then it can be seen as OK to mention your sim to them. If they are consequently interested, they may ask for more information about it. Sometimes even your friends aren't interested, so make sure that they have an interest in your sim before attempting to recruit them. Or else, you might be going down a path that can get you into serious trouble.

The act of spamming is to send unwanted messages to people. Spamming a person, makes a person extremely irritated, no matter how patient or nice that person may be in RL.

Issue Date:

Selection Policy

  1. Pegasus Fleet is devoted to an environment where people are encouraged to live up to their full potential, and as part of that at times will offer positions for advancement within the Fleet. It is with those ideals in mind that we set forth to provide a fair method for the selection of properly suited and qualified applicants to fill these positions.
  2. Individual Application Process – This process is reserved for use when only one such position is available.
    1. The Availability of applications will be posted to the IFS, Fleet Forums and CO List, along with any prerequisites for that position, and who to request the application from.
    2. It will fall to the COs of the Fleet to make sure that their crews are made aware of these opportunities, where appropriate.
    3. Applications will be available for 1 week, and must be returned to the PFA Member in charge of that position (For Admiralty positions, this would be the PFCO) before 10 days after the applications were first made available.
    4. In the event there are no applicants, the process may be re-started no sooner than 15 days after the week to receive applications has ended.After the application taking process has been completed, the applications will be presented to the PFA along with the recommendation of the PFA Member who took the applications.
    5. The PFA will then consider the applicants in a similar manner to the process used for Standing Orders, with an additional voting slot titled “None of the Above” included in the vote.
    6. The majority will be considered to be the greatest number of votes rather than 50%. In the event of a tie, there will be a run-off between the two leading candidates.
    7. In the event of “None of the Above” wins the vote, the process may be re-started no sooner than 15 days after the conclusion of the PFA Vote.
  3. Open Application Process – This process is reserved for use where many possible positions are available on a continuing basis, such as Academy Instructors or Tech Team Members.
    1. The availability of positions will be posted on the appropriate department web site, along with a link to the application, if any.
    2. At times, no more than once a month, and only if there are no more than 5 staff total, the PFA Member may post an ad for more members to the CO list.
    3. It will fall to the COs of the Fleet to make sure that their crews are made aware of these opportunities, where appropriate. For example CO Instructor positions would not be shared with normal crew.
  4. In all applications, consideration should be based on the applicants merits, application and history, in accordance with the Laws of the Fleet.

Issue Date: 15th December 2010

Sim Rating Policy

  1. Pegasus Fleet recognizes that the content of some sims may not be appropriate for all ages.
  2. Because of this, all sims withint the fleet will use the Universal RPG Rating scales for language, sexual content, and violence. Each category will be independently scaled from 0 to 3.
  3. Unless approved by the Pegasus Fleet Admiralty, all sims within the fleet will be no more than 0 or 1 in any of the three categories. Higher ratings must be approved by the Pegasus Fleet Admiralty.
  4. Sims must display a banner stating the sim rating prominently on their site.
  5. Existing sims coming into the fleet will be grandfathered in that if their ship application is approved, their existing rating will be considered approved. However, they will be asked to display the appropriate Universal RPG Ratings for all three categories.
  6. It is not acceptable to remove an existing player because you wish to change your sim rating. If you have such a player, and their legal guardians agree to let them stay aboard if the change is made, the player only then can be considered grandfathered to the sim rating change, otherwise, do not apply for the rating change.
  7. Sims should consider carefully their reasons for wanting such a change; content such as violence or the writing of other more mature subject matter are acceptable reasons for such a change.
  8. A change simply to exclude younger players from your sim is NOT acceptable. The exclusion in the Equal Opportunity Policy is not meant to provide a means of discrimination.
  9. Ships in joint missions with other ships or docked at a starbase or colony where the other sims involved have a lower rating than themselves should be respectful of these lower ratings and not share message with the other sims of a nature unacceptable for those sim's ratings.
  10. Commanding Officers who wish to apply for a sim rating change should apply directly to pfadmiralty[at]pegasusfleet[dot]net with at least the following:
    • Name of your ship
    • Current sim rating
    • New sim rating desired
    • Reasons for the change. Please give as much detail as possible.
    • List of any players below the age of the new rating, include what their parents said.
  11. Once the proposal is received, the Pegasus Fleet Admiralty will discuss the proposal and may ask you questions regarding it before voting on it. Once the vote is complete, you will be notified of the decision as quickly as possible.

Issue Date: 29th May 2010
Updated: 6th May 2015

Sister Fleet Policy

  1. Sister Fleets are defined as other simming fleets or organizations that wish to ally with and have an official close working relationship with Pegasus Fleet, yet still remain an independent organization from Pegasus Fleet.
  2. Members of Sister Fleets do not fall under the scope of the 11th Fleet Constitution.
    1. A Sister Fleet is free to set their own rules and regulations for their members. The PFA shall have no authority over the operations of a Sister Fleet.
    2. The Commanding Officer or unit of a Sister Fleet, and their laws, do not have any standing or authority within Pegasus Fleet Admiralty, save that there should be mutual respect between both parties.
    3. Not withstanding the above, members of Sister Fleets will be expected to abide by all relevant Pegasus Fleet guidelines when making use of Pegasus Fleet resources (such as forums, the wiki, etc) or when enacting joint missions.
  3. Sister Fleets shall be established by means of a by-law for each sister fleet which is officially recognized as such. Said by-law shall list the name of their fleet and the URL of their website. The Sister Fleet can also define the nature of their relationship with Pegasus Fleet, including, but not limited to, exchanging links, joint missions, and use of fleet resources.
  4. The status of a Sister Fleet is an at-will agreement and may be dissolved by either party at any time.
    1. The Sister Fleet's Commander/Commanding unit may do so by informing the Pegasus Fleet CO, who will then inform the PFA to update the aforementioned by-law. This is one of the few cases where the by-laws may be altered without a PFA vote.
    2. Pegasus Fleet may dissolve a Sister Fleet arrangement through a vote to update said by-law as directed by Article VI, Section 3.

Issue Date: 12th July 2010

Strike Policy

  1. The Pegasus Fleet Strike System is meant for Commanding Officers, OOC Fleet Staff, and Admiralty alone, and is not meant for use with Fleet Members below those levels.
    1. It is to the COs to develop and maintain their own disciplinary systems on their sims, so long as they follow the Laws of Pegasus Fleet and don't interfere with the Judicial System of the Fleet.
    2. COs should not enter Disciplinary Records for their crew into the Integrated Fleet Systems, and if they feel something should be noted therein, should instead contact the JAG on such matters, who will decide whether the action should be entered into the system or not.
    3. Only a Fleet Member's superior, as per the Chain of Command (CoC) for discipline specified in the Constitution may enter a Strike on their record.
    4. Others who wish to enter strikes on a player must request it of the Players Superior, as per the CoC for Discipline.
    5. Strikes are a function of the Executive CoC, the Judicial Branch and other Admiralty Members may not use strikes as punishment except within their own department. In the case of a Court-Martial, Strikes issued by a superior may be upheld, but additional strikes may not be issued.
    6. Strikes are entered on the Player's Record and not the Character's Record. Strikes entered will affect all characters of that player which are CO, OOC Fleet Staff and Admiralty.
    7. Before entering a Strike into IFS, The Superior should first examine the Player Records of that Player to insure that no other strikes are in effect, which could affect the rank(s) of the Player's Characters.
    8. Strikes entered in the Player's Record must include their expiration date and the reason the strike was issued.
  2. Strikes are assigned for many things, including, but not limited to missing reports, General or Specific Offences, Failure to handle an application in 7 days time, etc.
    1. Depending on the severity of the Offence, A warning should be issued for the first instance of an offence, such as not filing a report, etc. Such warnings must be entered into the IFS, just as with strikes, but warnings do not expire
    2. The first strike will not cause a demotion of any kind, but will render the holder ineligible for either promotion or selection while any strikes are in effect.
    3. Each Strike after the the first will carry with it a single incremental drop in rank. If the drop in rank would make a Fleet Member ineligible for the position they hold, they will be removed from that position.
    4. As strikes expire, any rank drops incurred will be automatically restored.
    5. CO's and OOC Fleet Staff are required to hold a position of Lt. Commander or higher. Admiralty must hold a position of Commodore or higher.
    6. Strikes will "Clear" themselves after 3 months. New strikes will not delay the removal of previous strikes, but will not expire till 3 months after the previous strike has expired.
    7. In extreme cases where the onus of a single strike is felt to be insufficient, the Superior may petition the PFA for permission to assign 2 strikes to an individual.
    8. The individual assigned a strike and the JAG must be informed of such by the superior assigning the strike.
    9. All records of the Offence surrounding the strike should be kept by the assigning Superior Officer until the strike has expired.

Issue Date: 15th December 2010 Revised: 2nd December 2012

Privacy Policy

The fleet takes the privacy of it's members quite seriously, and shall take steps in order to protect that privacy. Fleet members should be able to expect a certain measure of privacy, both of their personal data and communications. The fleet will not tolerate people accessing or sharing such information, with every few exceptions.

  1. Private communications are to be accessible, modifyable or sharable only by the sender and the recipient(s). The sender and recipient(s) are the only ones who may share these communications with others. Accessing, modifying or sharing them without the permission of these parties, whatever the means, is grounds for immediate expulsion from the fleet. This does not apply to public communications, such as posts, logs, news items or CO List messages.
  2. Personal data, including contact data is given for administrative purposes of the Fleet as well as the required communications neccessary to the nature of simming. Accessing, modifying or sharing this data with people outside the scope of needing to know, without the permission of the person whom the data is about, is grounds for immediate expulsion from the fleet.

Issue Date: 15th July 2012