General Orders & Directives

From HFWiki
Jump to: navigation, search
This page has been adopted by the FC as an official policy.

The following is the Eighth Fleet General Orders and Directives, ratified by the Horizon Fleet Commanding Officers and Fleet Council on 19 May 2009 as a guideline for Horizon Fleet membership. It was reaffirmed by a vote off the Commanding Officers and Fleet Council on 17 April 2010.

Contents

Introduction

The General Orders and Fleet Directives shall be the governing by-law of the Fleet. They are the policies by which more specific regulations, procedures, and rules are defined. Horizon Fleet General Orders and Directives are a series of guidelines used to instruct members of Horizon Fleet on the proper etiquette and policy in situations that require consultation for a resolution.

General Orders

General Order 1

As the right of each Horizon Fleet member to be treated with respect and dignity in accordance with the Horizon Fleet Mission Statement is considered sacred, no Horizon Fleet member may engage in acts of discrimination or harassment for any reason. This General Order takes precedence over any and all other considerations, and carries with it the highest moral obligation.

General Order 2

All characters must be the original work of their creator, and may not bear resemblance to canon characters such as Picard, Data, or Sisko. It is up to the Director of Personnel & Awards or an individual CO to make the final judgment as to whether a character is acceptable or not. Characters, whether PC or NPC, are the property of their creators, and therefore may not be misused, abused, or killed without express permission. Use of the same character on a second ship within the fleet is not permitted. The following races are not allowed to be created by players:

  1. Non-Humanoid (Big rock creatures, Tribbles, clouds of psychedelic disco gas, etc.)
  2. Q, half Q, Q in human form, etc.
  3. Breen
  4. Androids
  5. Borg ("freed" Borg (e.g. 7 of 9) are allowed at a CO's discretion, Borg still in the collective are not)
  6. Jem Hadar or Vorta
  7. Founders/Changelings or any other Shapeshifters (this includes Chameloids)
  8. Xindi and all variations thereof
  9. Suliban
  10. Delta Quadrant indigenous races (Kazon, Hirogen, Talaxian, etc.)
  11. Species 8472 (Humanoid or otherwise)

General Order 3

You are allowed a total of five (5) characters in Horizon Fleet. No more than one can be a Commanding Officer, and all must abide by posting regulations set out in General Order 3 of this document. Additionally, each player is allowed only one character per simm (not counting NPCs), and each character must be unique. In addition to the 5 posting characters, a player may have up to two non-posting characters for ancillary fleet positions, such as Fleet Council or Fleet Support Staff.

General Order 4

A Commanding Officer may require a crewmember to enroll and pass the Horizon Fleet Cadet Academy, regardless of simming experience, if the Commanding Officer deems it necessary. If a crew member is assigned to the Academy, he or she may not hold a rank higher than Lieutenant, Junior Grade, until such time he or she has satisfactorily passed the Cadet Academy. It is the Commanding Officer's Responsibility to notify the Academy Director via email that a new Cadet has been submitted to the course.

Cadet Academy is not to be used as a punishment; it should only be used for players who are inexperienced and require assistance in being brought up to speed. A crewmember should be sent to Cadet Academy within the first month they have been accepted onto the simm; if a CO wishes to submit a crewmember to Cadet Academy after the first month, sufficient reason must be given and accepted by the Academy Director before submission.

General Order 5

Commanding Officers reserve the right to grant promotions, which are based primarily on in character posting ability, but can also be granted for exceptional out of character assistance to the simm. It is up to the CO to determine criteria for promotions.

Executive Officers may not outrank their ship Commanding Officer. The maximum rank an Executive Officer can reach is Commander. However, if the Commanding Officer is ranked Commodore or higher and is a Task Force Commanding Officer, the highest rank the Executive Officer can be promoted to is Captain. In extenuating circumstances, the Fleet Council may choose to accept the petition of a Commanding Officer to allow for exceptional service.

Department Heads can only reach the rank of Commander. Their rank may be equal to, but not exceed, the rank of the Executive Officer. Other members of the department may only reach the rank of Lieutenant Commander. Marine ranks are capped at the rank of Lieutenant Colonel. Commanding Officers who wish to promote their Marine above the rank of Lieutenant Colonel are required to contact their Task Force Commanding Officer.

Fleet Directives

Fleet Directive 1

By default, Horizon Fleet Simms will maintain an age rating of 13+. Commanding Officers may petition the Fleet Council for a higher rating. If granted, the higher rating must be clearly noted on the ship's website and in the ship notes section of IFS. Regardless of rating, all Simms should maintain a high moral standing, and post should be tasteful. If in doubt, one should err on the side of caution. Other options are 15+ and 18+.

Fleet Directive 2

As much as possible in a science fiction simm, please keep posts realistic. Your shuttle is not able to destroy a planet, and a ship out of torpedoes isn't about to launch an assault on a heavily fortified enemy position.

Fleet Directive 3

Generally speaking, players must post once every two weeks with each character they play to remain active. This posting requirement can be changed by individual COs for their ships, provided such a change is made known to all players on the ship and is available on the website. Commanding Officers are responsible for developing posting policies for their simm should they wish to deviate from the Fleet minimum as described above. Posting policies are to be clearly listed on the simm website, and communicated to each player upon joining. In the event the policy is changed, the Commanding Officer must notify the crew and change the policy on the website.

Fleet Directive 4

Commanding Officers will submit their required monthly reports by the first calendar day of the month for the previous month in which the report applies. As an example, reports for the month of January are due February 1st. Fleet Council members will submit their required monthly reports by the fifth calendar day of the following month for which the report applies. (i.e.: January reports are due February 5th).Reports may be submitted as early as 5 days before the end of the current month. Standing Committees will submit their required reports the last calendar day of the month for which the report applies. The report will be submitted to a designated Fleet Council Member.

Fleet Directive 5

Commanding Officers requiring a Leave of Absence are required to notify, by email, their Task Group Commanding Officer, Task Force Commanding Officer, and Department of Personnel & Awards Director whenever they are in need of a leave of absence. If the Comanding Officer is enrolled in CO Academy, the Academy Director should also be notified. Commanding Officers should include the date they are leaving and returning and any instructions for the Department of Personnel & Awards Director in case their ship receives any pending applications while they are away. Commanding Officers are also required to send an official email when they return from their leave of absence. Should a CO fail to properly request LOA (unless exceptional circumstances occur and are accepted by the TFCO) and be given a strike, the strike will stand.

Staff Members requiring a Leave of Absence are required to notify, by email, their direct superior, and the Department of Personnel & Awards Director whenever they are in need of a leave of absence. Fleet Council members should notify the rest of the Fleet Council. Staff or Fleet Council members should include the date they are leaving and returning. The Staff Member's direct superior and/or Fleet Council will determine a member to serve in an Acting capacity during the LOA when appropriate. An official email is required when the Staff or Fleet Council Member returns from their leave of absence. Should a Staff or Fleet Council member fail to properly request LOA (unless exceptional circumstances occur and are accepted by the direct superior and/or Fleet Council) and be given a strike, the strike will stand.

Fleet Directive 6

A Commanding Officer or member of Fleet Support Staff may be removed from his or her position by the Judge Advocate-General if it is determined the Commanding Officer or member of Fleet Support Staff member inexplicably disappeared or the Fleet Council finds 'No Confidence' in the Commanding Officer or member of Fleet Support Staff member in question. "No communication" is established when a formal request for communication and information is sent to all known email addresses of the Commanding Officer or member of Fleet Support Staff by the JAG office followed by no communication, in or out of character, from the Commanding Officer or member of Fleet Support Staff through any of their characters for a period of no less than two (2) weeks.

In addition, a Commanding Officer who fails CO Academy will be automatically removed from command.

In instances where a Fleet Council Member finds No Confidence in the Commanding Officer or Fleet Support Staff Member, a formal complaint must be submitted to the Office of the Judge Advocate-General. A call for a vote of No Confidence is developed and conducted by the Office of the Judge Advocate-General. Also, the vote must be passed by a majority of the Fleet Council members. When both of the above conditions are met, the Office of the Judge Advocate-General will remove the Commanding Officer or member of Fleet Support Staff.

Fleet Directive 6A

A Fleet Council member may be removed from his or her position by the Judge Advocate-General if it is determined the Fleet Council member inexplicably disappeared or the Fleet Council finds 'No Confidence' in the Fleet Council member in question. "No communication" is established when a formal request for communication and information is sent to all known email addresses of the Council Member by the JAG office followed by no communication, in or out of character, from the Council Member through any of their characters for a period of no less than two (2) weeks.

In instances where a Fleet Council Member finds No Confidence in another Fleet Council Member, a formal complaint must be submitted to the Office of the Judge Advocate-General. A call for a vote of No Confidence is developed and conducted by the Office of the Judge Advocate-General. Also, the vote must be passed by a majority of the Fleet Council members. When both of the above conditions are met, the Office of the Judge Advocate-General will remove the Council Member.

Fleet Directive 6B

The Judge-Advocate General may be removed from his or her position by the Personnel & Awards Director if it is determined the Judge Advocate-General inexplicably disappeared or the Fleet Council finds "No Confidence' in the Judge Advocate-General as outlined in the Horizon Fleet Constitution. "No communication" is established when a formal request for communication and information is sent to all known email addresses of the Judge Advocate-General by the Personnel & Awards Director followed by no communication, in or out of character, from the Judge Advocate-General through any of their characters for a period of no less than two (2) weeks.

In instances where a Fleet Council Member finds No Confidence in the JAG Director, a formal complaint must be submitted to the Horizon Fleet Personnel & Awards Director. A call for a vote of No Confidence is developed and conducted by the Personnel & Awards Director. Also, the vote must be passed by a majority of the Fleet Council members. When both of the above conditions are met, the Personnel & Awards Director will remove the JAG Director.

Fleet Directive 7

No Fleet Member may use IFS to enter, alter, obtain or access data without authorization from the Fleet Council. Theft (or the unauthorized removal) of email addresses, ages, or any information held on the system relating to a Fleet Member in person (i.e. their real name, real age etc.) is an offense contrary to the Fleet Law and the mandatory punishment is removal from the Fleet (except in exceptional circumstances proven to the Judge Advocate-General).

Fleet Directive 8

Horizon Fleet reserves the right to remove any player who can be considered a menace to the peaceful order of the Fleet. Upon discovering that a player is engaging in acts or behavior that can be considered a menace to other Fleet members and/or to the order of the Fleet, the Fleet Council will give the player a warning that their behavior, actions, etc are inappropriate. Should it continue, the player may be removed by vote of the Fleet Council. A simple majority will result in the player being removed from the Fleet with a note in their Service Record and an automatic 90 day ban. In extreme circumstances, a permanent ban may be considered but requires a unanimous vote by the Fleet Council.