TFD Gaming Charters

ADMIRALTY S.O.P. & WARDROOM OPERATIONS 'OPS' DEPARTMENT INTELLIGENCE & SECURITY DEPARTMENT DIPLOMACY and RECRUITING LOGISTICS RESEARCH DEPARTMENT

STAR TREK ONLINE
Charter & S.O.P.
(Changes to the STO Charter & S.O.P. are coming to align it with the "NEW" TFD COMMUNITY CHARTER, as Revised 19 May 2013)

Groomed & corrected by Lance R. Violator (4 JUN 13)

Welcome to TFD. The rules and regulations in this policy are to be followed by all members of all ranks. Please read through and understand these following rules designed to protect you and all members of the community.

Greeting

TFD Gaming is a community based on the simple rules of having fun. We focus on making the community enjoyable and easy to interact with other 'gamers' of a similar play style and mindset. We are spread across many games to meet the needs of all of our members. Our strengths are in our ability to communicate through multiple media outlets and in-game to meet the demands of such a large organization.

I. Obtaining and Maintaining Membership

A. Tactical Operations Fleet Community (TFD) is an 18+ mature gaming community. All members must meet the age requirement when joining the community
B. All members need to be registered on the website. When they register on the website

1. The name used on the website must be similar to the name the member will use in voice program
2. If you have questions, about your name being similar enough, ask any game leader or your recruiter
C. The prospective member must inform the community the names of all characters in the game. When members create new characters, they must inform the community of the new character's name. This is done by registering the character on the TFD website. Members who do not register their characters will be removed from the fleet roster during the routine roster maintenance
D. Members within the community cannot hold more than one office or responsibility at a time. If members hold a position they cannot be given another office unless they resign from the other office.
E. TFD Members that are also members of other organizations/guilds cannot hold a position of authority in TFD if they are to retain officer status in the other organization. This rule will only apply if we are involved with that specific game.
F. TFD members wishing to work as an officer need to be a member of the TFD community for 90 days before applying for an Officer position (unless approved by unanimous decision of the community/game leadership).
G. Inactive accounts will be deleted during roster maintenance and members may re-apply to the guild if they left under amicable circumstances. Final decisions on re-applying to the guild belong to the game leadership (see below).
H. TFD will require that you are active member of the community.

1. Two types of activity, game and community activity.

a. Community; log onto mumble and the website at least once every 90 days
b. If any account is inactive for > 90 days, member shall be removed from roster
c. If you decide to become a member of TFD, again, you will follow new member procedures.
2. Game activity, for regular members, you are required to log in and remain active at least once every 90 days.

a. If you cannot maintain your activity, please inform a game leader. That is not a reason to put in for a Leave
of Absence (LOA).
b. Officers must be login to perform their jobs at least every 14 days, or they will be found derelict in their duties.

1). If you hold a rank and become inactive your rank will revert to TFD member, and will have another inactivity cycle before removed from the community. You may reapply to the game leader personally in this situation
2). If you decide to not rejoin the specific game back with TFD, but join another guild or organization, but want to continue to use mumble as a method of communication, this will be allowed, however your Mumble tag will change to reflect your new status.
I. All members must disclose if they have been members of the TFD community in the past. If this information is withheld, the individual will be subject to disciplinary action and dismissal
J. If a recruit is a member of a TFD alliance, TFD security will investigate why there is a change in membership, and will hold the right to ask former affiliates on conditions and reason of departure
K. If someone is on a TFD ban list then they will not be allowed back into the community
L. A ban list will be kept at a community level, and it will have the reasons of the ban, date, when the ban was done, all known names, and other notes as seen as important.

Note: This list will be shared with all TFD allies, and any other entities that which to have access to the list.

M. The ban list will only be managed by community leaders, security, and game leaders. An individual shall be placed on said ban list only by a consensus of all community and game leaders.
N. All new members to TFD in STO will remain as STO cadets for a 60 day probationary period.

II. STO Ranks and Promotion

A. The Star Trek Online community is always seeking talented individuals who are willing to donate their time to assist in helping in the administration of the fleet’s functions. As such in order to be considered for a game or community job, the individual must meet the community prerequisites for promotion (see above section)
B. If the officer or leader cannot do the job they have undertaken they may be removed by their game leader at the leader’s discretion.
C. Star Trek Online will have a leader (Fleet Admiral), four assistant game leaders (Admiral), four departments; each of which have their own commanding officer, at least one senior departmental officer (Captain), and one/two junior departmental officer (Commander). The departments can increase in size depending on need for the department’s need. A commanding officer must consult with the main game leader personally to add extra officer slots

III. Tactical Operations Fleet Delta Code of Conduct

A. Log on to Mumble when in game, if possible.
B. Log on to the website suggested every few days for updates or general guild/game knowledge, at minimum (required) once every 90 days.
C. All personnel will file a Leave of Absence (LOA) in the appropriate forum after notifying the Game leaders via a PM on the Guild website. Failure to do so will result in disciplinary action. An LOA will be filed for those individuals and officers who will not be able to perform their duties for a period of 2-4 weeks. Any period over 4 weeks will only be considered by the Game Leader on a case by case basis for emergencies only.
D. All Department Officers are required to be active in Game and Mumble. Those individuals who are not active in Game and/or Mumble and do not have an LOA submitted for the absence for a period of 2 weeks (14 days) will be found to be derelict in their duties and will be considered for immediate dismissal from their Department. The dismissal from the department will result in a reduction of rank to TFD Member.
E. Officers will follow all standing orders given by the game leadership.
F. Obey orders from a department leader, assistant game leader, or game leader. Do not attempt to supplant those officers in any way. Disregarding this order will be considered for immediate dismissal from your department (for officers), or from the game community (for members).
G. If you can, please attend all guild and game meetings. Notify your commanding officer directly if you’re not able to attend these meetings.
H. In the course of duty, if there is sufficient evidence to accuse a fleet member or officer of violations of the Code of Conduct or they chose to ignore you, please bring up the incident with the nearest Game officer except in cases of emergency.
I. Any issue that arises from normal game play or from Mumble chat must follow a strict chain of command. The issue will follow this chain, junior officer, senior officer, department head, assistant game leader, and then lastly game leader. If an issue arises and an individual supplants the chain of command in any way, disciplinary action will follow determined by the game leadership.
J. Allies are people that will either officially or unofficially sign on with TFD but remain their separate entity. They will be allowed to run their own fleet in the manner they see fit with one condition. They are to abide by the TFD Code of Conduct and Rules for Voice Server. If they do not abide by these rules, they may be subject to divestment from TFD.

NOTE: Failure to follow the Community and Fleet regulations will result in the following:


1. Verbal Warning
2. Demotion of one grade
3. Member/Officer placed on probation with duration determined by game leader
4. Dismissal from TFD

NOTE: Emergencies would include members and/or officers violating the Mumble Conduct Policy despite attempts by other officers to control the situation. In emergency situations, contact the highest ranking guild officer on Mumble, if that is not an option; contact a Mumble administrator (other game leader or community leader) to restore order.

NOTE: Depending on the offense committed or the severity of the offense, the Game leader reserves the right to choose whichever punishment is best suited for the situation. The Game leader reserves the right to add or change punishments depending on the nature, repetition of the offense, and overall character of the individual in question.



IV. Rules for Voice Server



A. All members are to be respectful at all times while on the Mumble program. Racial/Sexual slurs will not be tolerated, religious and political discussions are not to be held in an open room (e.g.: lobby's, etc), all parties discussing a sensitive nature will move to a private channel and all people entering the room will be immediately notified of the nature of the conversation. Disciplinary action will follow if these rules are broken.
B. All members need to be registered and use Mumble
1. Mumble is a cornerstone of our community communication. If a new member wishes to join TFD they will have to join mumble.
2. A mic is not a requirement but a recommendation to all members since it will allow for easier interaction with all members, especially in operations and other group activities.

a. Language barriers are not an issue. Even if you cannot speak English clearly you are still welcome to our community.
b. Bashing of one game to another will not be tolerated
3. You are not to go in a new channel and start a conversation if the channel is clearly marked as a run, or group event. If you must join that channel you may do so and listen but you are not to interrupt the run. If you need to speak make sure it is at a point that will not interfere with the run or group event.
4. Freedom of Speech: Words spoken in an open forum conversation will be free of slurs including but not limited to religious, slanderous, racial, political and social status.
5. If something is discussed in a room that bothers you, please ask that the offensive conversation stop or to take the conversation to a different room. Space is not an issue on Mumble, so conversations can be taken to other locations.
6. Language should be kept to respectful voices, no screaming or yelling at another member will be tolerated.
7. Do not operate Mumble whilst impaired (drunk for example). If you conduct yourself in an unbecoming manner seen as offensive to others, disciplinary action can take place depending on the circumstances of said infraction.
8. Violations of voice server policy will be handled promptly by game and/or community command staff on a case by case basis.
9. All individuals joined in and affiliated with the TFD community will follow a Mumble naming protocol. Their naming “tag” will consist of a community or game identifier followed by a tag modifier showing their rank in the community or game, and handle.

a. Naming tag examples will include, TFD, STO, TOR, WOT, EVE, GW2
b. A tag modifier example would include Member, Ally, Captain, and President.
c. Handles will not be allowed to be racist, defamatory, derogatory, illicit, or controversial.
d. Any member found in violation of this mandate will be subject to disciplinary action and may have their handle changed y game/community leadership.




V. Enforcing Tactical Operations Fleet Delta Policy

A. The policies of TFD shall be enforced following the community and game chain of command.

1. If an issue occurs, breaking community and game rules bring it directly to the nearest security officer or command structure officer.
2. Game leadership/security will investigate the alleged infraction.
3. Members, game leaders, and security officers are not to record conversations in mumble without the party’s consent.
4. If game leadership cannot make a decision upon the evidence and situation provided, only then will the situation be referred to community leadership for solution.
5. In order to remove a member, a quorum of game and or community leadership (depending on who is reviewing the infraction) must be present to vote, and a majority of game or community leadership must agree to remove the accused.

a. If a member is dismissed for reasons of inactivity, they will have the ability to rejoin the game community with approval from security, community, and game leadership together.
b. If the member is removed for other reasons, they must communicate with community and game leadership. They must have unanimous support from security, community, and game leadership.

6. The accused may be removed from a game and not the community at large.
7. The accused may also appeal the decision to game or community leadership regarding removal or banning from a game or the community. A quorum of game or community leaders must meet and vote to appeal the decision with a 2/3 majority required to win the appeal. The accused may also select an advocate to speak on their behalf in appeals.

NOTE: This policy may be changed for severe infractions of individuals deliberately disregarding the TFD code of conduct or rules for voice server.

NOTE: Game and community leadership reserves the right to change, add, or remove punishments for severe or repeated infractions of the TFD code of conduct or rules for voice server.