Guidelines
Are essentially rules with “designed in” flexibility. Guidelines provide structure and background for activities, behaviors etc. while engaging in =1FS= team and gaming activities. Guidelines exist to assure a favorable team and gaming experience. Guidelines are always used best in concert with common sense and are the preferred method of establishing structure! Our guidelines contain both mandatory and voluntary content. 

Policies
Are fixed “rules”. Policies must not be violated. Intentional violation of a policy may lead to disciplinary action up to and including dismissal from the squad (e.g. cheating).

Processes
Are fixed “mechanical” procedures that have been designed to optimally organize team and game activities. Processes are determined based on a need for a process, usually as a response to actual in-game or in-team experience. Processes are frequently “driven” by guidelines and policies.

1. =1FS= soldiers are honor bound to display respect to other squads and soldiers. It is the code of the warrior breed.
2. Obey commanding officers.
3. Never intentionally shoot team members.
4. Play for the team not for yourself (sometimes you have to make a sacrifice).
5. You are expected to participate in official training meetings. If you cannot, reasonable notice is required.
6. When we recognize your commitment to excellent work, you can expect to be decorated and promoted.
7. Wear your =1FS= Callsign and Tag correctly and proudly.
8. Cheaters are not tolerated!
9. Our most important rule: =1FS= Operatives have fun!

2. Membership Requirements

1. You must have the full version of Delta Force - Black Hawk Down and the newest available update.   updated
2. You must have ICQ. Download it at icq.com.
3. In order to fully enjoy =1FS= membership, you should be prepared to participate 8 hours or more each month.

3. Membership in another Squad   NEW

1. Membership in a squad/clan based on another multiplayer game of NovaLogic's Delta Force series is not allowed!
2. Membership in a squad/clan based on another multiplayer game and not one of NovaLogic's Delta Force series is allowed. *

Please feel free to join any =1FS= server displayed on Novaworld. Players wishing to apply for membership in =1FS= can ask any =1FS= Operative for an opportunity to try out for the team. A =1FS= Team Leader (Detachment Commander/Executive Officer) must be present for a tryout. 

1. Your callsign is your =1FS= identification in the Delta Force gaming community. You become well-known by your =1FS= Callsign. Choose it carefully.
2. Regulations require that callsigns be no longer than 10 characters (without =1FS= tag) and must not contain any special characters such as @,$, § etc. =1FS= does not use "hexed" characters in player callsigns (only letters of the English alphabet and numbers 0-9 are allowed).
3. Make sure you really like the player callsign you choose. Your callsign should last you for the "long haul". Changing callsigns at =1FS= is generally frowned upon. One change is possible if there is significant justification to do so.

2. Battle Tag

1. Battle Tags (BT) are used during official battles (always) and scrimmages (always) only. Use of Battle Tags greatly improves on field visibility because it is based on the concept of initials or an abbreviated callsign.
2. Battle Tags are at minimum 2 letters and at maximum 3 letters and the tag =1FS= (note that there is no blank character/space between your chosen letters and the tag =1FS=).
3. Special characters are not allowed (only letters of the English alphabet and numbers 0-9 are allowed).
4. Battle Tags consists of capital and small letters (case sensitive) depending on the consistence of your Battle Tag and your original =1FS= Callsign.
5. Your chosen Battle Tag should represent you well and should make you easily identifyable to your teammates.
6. For illustration here are some examples: Darkness=1FS= to Drk=1FS=, His Own Mom=1FS= to HOM=1FS=, Azzkikr=1FS= to Azz=1FS=, Dark Angel=1FS= to DA=1FS=.

2. Expectations to Server Operator

The =1FS= Server Operator shall

1. have the server (host) up and ready no later than 15 minutes before the match is to start
2. assure all server settings are correct
3. create all game passwords (game and squad)
4. communicate passwords to team leaders/battle coordinators of each squad at least 30 minutes before the match
5. send the server's IP address to team leaders/battle coordinators of each squad
6. rigidly remain neutral to assure the server (host) in no way influences game play for either squad participating.

3. Expectations to Operatives

=1FS= Operatives shall

1. check the Battle Management forum and Schedule daily
2. sign up for the match under the thread posted in Intelligence Forum at least 1 day prior to the match
3. be online on ICQ at least 30 minutes before the match
4. know the passwords (game and squad) at least 15 minutes before the match
5. have the server's IP address and have verified the ping latency at least 15 minutes before the match
6. know what maps in which one is assigned to start and/or play and when a substitute is in for one
7. have their PC rebooted and ready at least 15 minutes before the match
8. display Battle Tags properly and correct during gameplay
9. follow the code of the warrior; display honor and show respect to team mates and the opposing squad.

4. Expectations to Battle Management Officer   updated

The =1FS= Battle Management Officer shall

1. post all scrimmages and battles (matches) in the Battle Management forum and Schedule as soon as possible, preferably 1 week prior to the match
2. post a sign up thread in the Intelligence Forum at least 2 days prior to the match
3. follow the same expectations listed under "3. Expectations to Operatives" above.

5. Expectations to Team Leader   updated

The =1FS= Team Leader shall

1. identify all starters and substitutes for the match
2. communicate the line-up for each map at least 15 minutes before the match
3. send passwords (game and squad) to each player at least 15 minutes before the match
4. assure that all participants display Battle Tags properly and correct during gameplay
5. assure that =1FS= operatives play with honor and show respect to team mates and the opposing squad
6. assure that he is the only =1FS= operative officially communicating with the opposing squad
7. follow the same expectations listed under "3. Expectations to Operatives" above.

1. An operative with little or no activity for given period of time may be deemed as inactive.

2. Identification of Inactive Operatives

1. When =1FS= Team Leaders determine an operative in the team as inactive or marginally active they may request approval of =1FS= Squad Command to remove that operative from the active team.
2. Upon approval, Team Leaders contact the operative by e-mail and include the following information:
• present facts illustrating inactivity/insufficient activity
• present all of the operative's current options
1. contribute by comitting to more activity
2. reassignment to Reserves Unit
3. Honorable Discharge upon request
• request for reply within 7 days of date of e-mail
3. If the operative does not reply within the proscribed time, the operative will receive a General Discharge from =1FS=.
4. When Team Leaders determine an operative inactive or marginally active once again, Team Leaders may reassign the operative to Reserves Unit without any preceding notification.

3. Reassignment to Reserves Unit (RU)

1. Reassignments to Reserves Unit will be made immediately whenever an operative requests reassignment to RU.
2. =1FS= Squad Command manages further actions with the operative. 

4. Reason and Deadline for Inactivity

1. After operative transfers to RU the operative has 30 days to provide reason for his inactivity by mailing an explanation to the squad commander.
2. This mail must include a future date for the operative's expected return to active duty.
3. =1FS= Squad Command approves the request and expected return date.
4. If the inactive operative has not responded with a reason and deadline after 15 days in RU he can expect a one time reminder from the squad commander.

5. Return to Active Duty / Extensions / Discharges

1. If the inactive operative is ready for active duty he will be reassigned to unit detachment at the next promotion round.
2. If the inactive operative is not yet ready for active duty he can request an extension from the squad commander.
3. Any reserve operative can leave the squad if desired by contacting the squad commander by e-mail.
4. Departing reserve operatives receive Honorable Discharges.
5. If the inactive operative does not communicate a reason/deadline within 30 days of placement in RU he will automatically receive a General Discharge without a preceding reminder.