GNSF RULES

GNSF Rules

RULES OF ENGAGEMENT

TABLE OF CONTENTS

I. GETTING STARTED

1. Enlisting
2. Communications
3. Downloads
4. Naval academy and graduation

II. GNSF STRUCTURE

1. Chain of Command
2. Task Forces
3. Rank Structure
4. Promotions
5. Ribbons and medals
6. Bonus and duty points

III. SUPPORTED GAMES

1. Courtesy
2. Reportable games
3. Approved/banned players and organisations

IV. MANAGING ACTIVITY STATUS

1. Minimum activity requirement
2. Shore leave
3. Status definitions
4. GNSF automated system
5. Automatic email reminders
6. Summary of leave procedures

V. COMBAT OPERATIONS

1. Internet play
2. Cheats and bugs
3. Weapons Free
4. Voice communications
5. Saluting
6. Reporting in
7. Dropping from game or leaving
8. Silence of the dead
9. Neutrals or friendlies

I. GETTING STARTED

1. ENLISTING

ALL new comers to the GNSF are required to review our Rules of Engagement (ROE) and standing orders (SO) completely before submitting their Sign Up Form. Once you submit your Sign Up Form, you confirm your agreement with all that is stated in these documents and pledge to abide by all rules and regulations. Once you agree to these conditions and sign up, you will become part of the GNSF and designated as a SFCA (Cadet). Should you have any questions you would like answered before joining, feel free to contact any one of our officers listed below, or within our membership roster. Please understand that our ROE and SO are subject to change as new situations arise and as changes take place within the organization. Please remember that once you become a member of the GNSF you will be expected to conduct yourself in the manner prescribed in the following paragraphs until you formally resign or are dismissed.
GNSF Members are free to belong to any other online group they choose with the EXCEPTION of group(s) that are designated as “Hostile Organizations.” Membership in any form (including joining their forum) will result in immediate dismissal from GNSF. The reason for this is simple, either the group or members of such group contain known cheaters, or those that have shown disrespect and abuse to others in the past. Please remember some groups do not have the same standards, and some have no standards at all. At GNSF we try not to place restrictions on a player, as the player's on-line time is his/her own, and no one should tell another what he/she can or can't do. We do however have some restrictions, like this one, whose sole purpose is to prevent cheaters and abusive people from becoming members just to cause grief for the good people here. While we try not to restrict membership to anyone, just as in real life, some simply do not care about others, and these types of players are just not welcome here.
The first thing you need is a nick name (Callsign) for your sign up. Please try to restrain it to 10 Alphabetic and/or Numeric characters or less and DO NOT use spaces (John Doe is NOT acceptable, John-Doe or John_doe IS). This will help later on when you add duty and assignment designators to your Callsign.While ICQ is used by some members, Ventrilo is the primary program we use to communicate, set up and play games. ICQ limits the number of digits a nick can carry.
No Callsigns that have a profanity or drug related connotation will be allowed. Anyone signing up with such a Callsign will have it removed, and must sign up again with one that is acceptable.
The GNSF does not allow two members to have the same call sign as this obviously would lead to confusion in the area of the records and scores of personnel involved. Check back at the GNSF site to see that you have been added to the GNSF Roster. At this time, you will be contacted by the Naval Academy with instructions on how to proceed, along with the requirements you will need to meet and how to get there.

2. COMMUNICATIONS

The main way GNSF players communicate with each other for organizing and starting games is via Ventrilo. ICQ is still used by some members, but it is not the primary means of communication. For ICQ, it is recommended to have and use a different ICQ UIN specifically for your membership in the GNSF (as this number will be listed on the roster).
For Ventrilo, you MUST have the client version of Ventrilo listed on the GNSF download pages, as a different version will NOT work with our server. You can either get the client software from our Downloads page, or directly from the Ventrilo website. The login information for the GNSF server is listed on our main page.
After you have graduated from basic training and are assigned to a Task Force, make sure to add your TF number at the end of your nick, (eg: TF-74, TF-75, etc). Also put the proper abbreviation of your rank in front of your ICQ nick (e.g. ENS, LTJG, LT, LCDR, CDR, CAPT). Check the Ranks page if you are unclear about the proper abbreviation for your rank.
Please do not send any mass messages to other members. This includes the false "ICQ is going pay" messages, and “Send this to everyone on your list". The rule is... NO MASS MESSAGING. This also includes mass E-mails, as most people do not want to be included on chain Email strings.
At all times, you are responsible for updating your info on your "user profile". If you change e-mail address, ICQ number, or any personal info, you must immediately update your profile and advise your Chain of Command so that email lists can be updated. You can update your profile data from the main page by selecting the EDIT MEMBER PROFILE link.

3. DOWNLOADS

Apart from communications software and depending on the games you wish to play, you may need to download some extra files, like patches, mods, mission packs etc. You can visit the GNSF download page for details. Please note that all downloadable files created by the GNSF are GNSF property and are not to be disseminated to other virtual groups. Doing so is grounds for dismissal from the GNSF organization.

4. NAVAL ACADEMY AND GRADUATION

Your first assignment is to the NAVAL ACADEMY which requires you to fulfill a number of requirements that will be outlined in detail by the NAC (Naval Academy Commandant), Deputy Commandant (NADC), the Training Group Commander (CTG) and the supporting Tactical Officers (TO). These requirements ensure you have read and understand the ROE, and can connect online for the game you play. Once you have completed your training to the satisfaction of the Naval Academy Commandant, you will be graduated and ready for assignment to a Task Force, promoted to ENS, and awarded the National Defense Medal. You will then be assigned by the Personnel Office to a Task Force where you will be able to play, train, and qualify for specific badges and awards. Note that you do not have to decide on only one sim, as players are free to play as many as we support here, adding the specific training badges to their records.
All Sign Up Forms are processed by our NAC. Should you have any questions upon entering, please direct them to any of our TOs . Our Chain of Command is there for a reason and we ask that you use it.

II. GNSF STRUCTURE

1. CHAIN OF COMMAND (CoC)

The GNSF is structured as shown on the CoC chart. The upper Chain of Command consists of the Fleet Admiral, the Chief of Naval Operations (CNO) and the Deputy Chief of Naval Operations (DCNO.) These Officers are always available for everything that a member may need, but we ask that members follow the CoC line first when dealing with a certain issue.

2. TASK FORCES

The GNSF is structured into Task Forces (TF), with TFs being activated as our member count requires. Each active TF will have air, sea and land combat capabilities. Each TF acts as a complete battle group within the GNSF structure, allowing us to have "TF vs TF" engagements. Each Task Force has a CTF (Commander Task Force) as well as an XO (Executive Officer). Other staff can be added at the CTF's discretion. Each Task Force has its own homepage that is maintained by a member within the TF. CTFs have the ability to award certain Ribbons and Medals.

3. RANK STRUCTURE

The rank structure used in the GNSF is based on Naval ranks, as the first sims played here were 688(i) Hunter/Killer and Dangerous Waters, naval combat simulators. Regardless of the sim played (Ground combat, Sea combat or Air Combat) ALL members use the same rank structure. This removes confusion about who is where in the rank structure when more than one type is used. It also keeps everything even and on the same level for scoring and awards. For more information on the specifics of the rank structure, check out the Ranks Page. All members will show the proper courtesy towards higher ranking officers. Rank is earned in the GNSF, not given.

4. PROMOTIONS

Upon completion of the Naval Academy training, you will be promoted to the rank of Ensign (ENS) and awarded the National Defense Medal . You will then be assigned to a Task Force for your stay within the GNSF. The best way to get promoted is to PLAY, making sure that you file all Mission Reports. Mission Reports play a vital role in determining who gets promoted, as they are the way promotion points a player earns are put into the system. Another way to earn promotion points is to become a Staff Officer, helping to manage the GNSF (please note that Staff Officers still must play and report missions). Some Staff offices award a specific amount of points per day to compensate the member for play time lost due to office work. If you are interested in a Staff Position, let your CTF know about it and he will pass it along.
Promotions from the rank of Ensign (ENS) up to the rank of Commander (CDR) are done by promotion points, training courses, and Time in Grade (TIG). Promotion points are the points earned by playing and reporting the game you play or holding a Staff position. TIG is the number of days you have been at your current rank. All promotions below the rank of Captain are issued by the CTF, while ranks above Captain are done via the Promotion Review Board (PRB). For a detailed description of the requirements for each rank, see the Ranks section of the AWARDS AND RANKS page.
If you have any questions about promotions contact your CTF.

5. RIBBONS AND MEDALS

During game and tournament play, members will be able to earn Ribbons, Medals and Qualification Badges. Some of these may be awarded to officers by their CTF, while others will be awarded by the COC or Instructors. Check out the Awards Page for more details on all the Awards, Medals and Badges, how they can be earned, and who can award them.

6. BONUS AND DUTY POINTS

Bonus points are given along with some ribbons and medals issued for combat-related achievements, usually to the top performers during a tournament/competition or over a specific time span. Further, duty points are given for staff positions and automatically added by the system to the staff member's record. Duty Officers duly appointed by a CO also receive duty points for the time period they are acting as a DO. Also, Time in Game (TIG) bonus points can be awarded to compensate for TIG loss while on a special assignment for those without a DO status at the time of the assignment.

III. SUPPORTED GAMES

1. COURTESY

When you play any reportable game, you are a GNSF ambassador and are expected to act like a GNSF Officer at all times. While other individuals or groups may have no rules, you should still conduct yourself as if you were playing here. We do not ask anything unrealistic of our members, only that they treat others with common courtesies and play fair and honorably.

2. REPORTABLE GAMES

The GNSF currently authorizes the following games for scoring: Ghost Recon, Arma Gold, Call of Duty, Company of Heroes, Company of Heroes Online, Dangerous Waters, 688(i) Hunter/Killer, Silent Hunter IV, Falcon 4 Allied Force and DCS Black Shark. GNSF MEMBERS CAN PLAY AND LOG ANY OF THESE IN ANY PLATFORM/ARMY THEY LIKE AND IN ANY COMBINATION THEY DESIRE.
A member may play and score missions played with other members of GNSF, with players that are on the approved players list, with members of approved organizations, but also with anyone else. In a negative sense, the only games that are not reportable are those played with people or members of organizations on the banned list.

GNSF White Ops (GNSF games in the stricter sense)
These are the games that are played between GNSF members or GNSF members and individuals on the approved list or members of approved organizations (see approved players list), provided that GNSF ROE and game settings are followed. Members reporting a game of this sense get points for their total time in game, but their other statistics (kills, wins etc.) are also tracked. Reporting these games is mandatory.

GNSF Black Ops (GNSF games in the wider sense – outside GNSF ROE)
This includes White Ops games where GNSF ROE and game settings are not followed, as well as any game played with ANY person on the internet who is not listed on the approved players list or is not a member of an approved organization (unless banned), regardless of whether GNSF rules and game settings were followed. These games can also be reported and scored in exactly the same manner as White Ops games. The only difference is that in this case, other statistics like kills, wins etc. are NOT tracked. However, the amount of points a member gets is exactly the same, as scoring is purely a function of time spent playing. Obviously, reporting these games is not mandatory – it is entirely at the member’s discretion.
Each player is required to file his/her own report on the mission reporting page.
Reports must list the name (callsign) of the "outside" player(s), PLUS the organization (if applicable) that the player belongs to.

ANY game reported MUST have a screen shot or debrief available on request.
Any differences and/or conflicting issues over any game automatically void that game. In any and all cases, kills on any Cadet are not scorable by the GNSF player. It can be mentioned in the report, but not scored.
ALL EXERCISE (EX games) type games must be logged as "EXERCISE" on the report page.
All data fields will be filled out (kills, players etc.). The description field must contain narrative of the game(s) at all times. Basic mission descriptions are sufficient; detailed ones are desired. Supplying a copy of the debrief file (where required)without further information does not meet this requirement. The report shall then be considered incomplete and be removed or otherwise nullified.
ALL WHITE OPS GAMES MUST BE LOGGED WITHIN 48 HOURS AND IN THE SAME CALENDAR MONTH, REGARDLESS OF THE LENGTH AND/OR OUTCOME.
ANY MEMBER CAUGHT INTENTIONALLY LOGGING FALSE REPORTS WILL BE PERMANENTLY DISMISSED FROM THE GNSF.

3. APPROVED/BANNED PLAYERS AND ORGANISATIONS

Any group that is listed as a BANNED group is there because of severe problems that stretch well into that organization. In most cases we will simply ban the offending players without punishing any good players in the outside group. Please make sure that ANY players you play with are NOT listed on the banned player list, as while the group as a whole may not be banned, some players might. ANY player from an outside group that is not on the BANNED players list MUST show in his approved group's uniform for the game to be reportable as a GNSF White Ops game, with the exception of players on the APPROVED players list, which may not belong to any group at the time. Approved and banned players and groups can be found at BANNED AND APPROVED PLAYERS LIST or by selecting the link from the main page.

IV. MANAGING ACTIVITY STATUS

1. MINIMUM ACTIVITY REQUIREMENT

IT IS MANDATORY FOR ALL GNSF MEMBERS TO LOG A MISSION REPORT AT LEAST EVERY 30 DAYS. We are all here for ONE reason, to have fun and play the games we like to play. We are a gaming group, and as such, one of the few requirements here is TO PLAY. Any organization that has members that DON’T play will not survive as a group, as inactive people do nothing more than occupy a space on the roster. At GNSF, our players PLAY, so you know you will always be able to find someone to get a game in with.

2. SHORE LEAVE

Since Real Life MUST always come first, there will be times when a player CAN’T play for a duration of time. We understand this and all that is asked is that the player let us know. This is the only way we can tell a player that can’t play for a while from one that just vanishes. It is only common courtesy that you let us know if you can’t make the required 1 game per 30 days, and that way we can take action to allow you to remain a member until you can again play. We have several "status conditions" we can set based on your required leave time.
There are only a few requirements for leave, which each member will accept by requesting leave. These are simple, common sense rules. ALL leave requests MUST be submitted timely, have a reason AND an estimated return date. If the reason is considered "private or personal", then the applicant can specify this. In this case the reason MUST be sent to FADM directly with instructions that this is considered confidential. FADM will then keep this information totally confidential.
The most important requirement is "Check in and stay in touch". GNSF WILL NOT babysit members on leave. They are to KNOW when their leave will expire AND make contact with their CO BEFORE the leave expires. This is the ONLY way a member can make sure that he/she can get the time needed without getting into trouble. Any member that stays in touch with COC will ensure his records remain safe. As a rule, if we do not hear from a missing member, we assume they have left. We will NOT remind people they are in danger of being removed, as that is done solely by an automated system (see below).

3. STATUS DEFINITIONS

Active
A member is considered active when he/she logs at least one report every thirty (30) days. Number of days since a member’s last report is shown on the Task Force details page. Date of last report is also shown on a member’s personnel record page.
Leave of Absence (LOA)
This leave is granted by the CTF, upon the Officer’s request, and covers an absence of 30 to 60 days following the date of the last reported mission.
Extended Leave of Absence (ELOA)
This leave is granted by the DCNO, upon the Officer’s request to the CTF, and covers an absence of 60 to 90 days following the date of their last reported mission.
Absence without leave (AWOL)
A member is considered absent without leave if he/she
• Was in active status but has not logged a mission in over 30 days (=AWOL on day 31)
• Has failed to report in (log a mission or granted time extension) before their LOA, ELOA or Special Deployment period expires (=AWOL on the day following the expiration of their LOA/ELOA/Special Deployment status).
AWOL personnel will NOT be granted Leave of ANY form or any time extension on their prior leave. All such requests MUST be made PRIOR to going AWOL.
Probation
Any member returning from AWOL status is placed on Probation. Any member on Probation that passes 30 days without logging a mission is flagged by the system and Marked AWOL. Unlike going AWOL from an active status, members on Probation going AWOL will have 48 hours to contact the COC with a GOOD explanation of why they have again gone AWOL. Failure to contact the COC AND provide a good excuse will result in the member being removed from the system.
ALL members on Probation are also checked to see how long it has been since they were placed on Probation. If the member has been active for a 90 day period, the system will automatically remove the probation and place the member back active. Note that while the status WILL change from Probation to Active in the player’s records, the Days since Last report WILL remain constant. Removal of Probation does not give 30 days from that point; it simply removes the Probation flag from the system and records.
Special Deployment (SD)
This area is for members that require ELOA greater than 90 days based on RL issues, usually "RL Military deployment". It is for players that must take a leave but still wish to remain members of GNSF. Any member requesting and being approved for ELOA greater than 90 days will be placed here. When a member returns he must be placed back to active in a TF MANUALLY by the COC, as each leaves time frame will be unique to the member, with actual return dates being "fuzzy" and not fixed.
For these cases the member's CO must contact the DCNO for "Special Deployment" permission, and Cc the upper COC on the request (CNO and FADM) PRIOR to that Officer being AWOL. The request must include the reason AND an expected date of return. Special Deployment status is granted by the CNO.
Non-Effective Strength (NES)
This status condition is for special circumstances that prevent a player from being able to play and log games regularly to meet the minimum play requirement. A player will then be assigned this status, which informs the automatic checking system to bypass him, thus never flagging him AWOL. This status is used only in very extreme cases and can ONLY be set by the CNO and FADM, and ONLY if the reasons are found to be severe and justifiable for the status.
Retired (Ret.)
This area contains the names of GNSF Flag members that have EARNED a "retired" status, as they can no longer afford the time to be an active member. This area is used exclusively for players that have contributed greatly to the GNSF over a long period of time, through continuous and exemplary services and/or many career achievements that had a direct impact on what the GNSF is today. Entry into this state is done by the upper COC after a unanimous vote. Very few players will be eligible for this status, as it is solely based on what a person has given to GNSF, and the reasons they can no longer be an active member. Request for "Retirement" status must be addressed to the GNSF upper COC who will render a decision. The normal for even being considered for retirement is at least 5 years of service, while contributing heavily to the GNSF organization. All GNSF Retired Officers can still play and log games with the GNSF community when RL permits, as they have EARNED the right. They can also be reinstated back to active status at their request

4. GNSF AUTOMATED SYSTEM

The GNSF Automated System is used for automatically monitoring many things on the GNSF site. One thing it monitors is player activity based on the players LAST REPORTED GAME. This allows the system to Email members to help them stay in good standing, and not become inactive. The automated system ensures everyone, from ENS to FADM is treated the same way, as it can not play favourites. It not only lists overdue members as AWOL, but also place members back to active when they terminate any leave.
The system basically executes once a day and follows the rules listed in the ROE to determine the status of every member. ALL members not on Special Deployment, Non-Effective Strength or Retired status are checked for their status. The system currently checks for several things, which break down into sections as follows;
Flagging AWOL members
This section deals with members that do not log a report within the specified minimum time frame for the status they hold, as specified above in the “status definitions” section.
Every time a member in this section is FLAGGED by the system, the following is done automatically;
• The member’s status is changed from "active" to "AWOL"
• An entry is added to the member’s persrec (promotion history) showing "Status changed to AWOL". This becomes part of the player’s permanent record.
• An Email is sent to the player, his CO and the COC indicating the status change, and directing the player to contact his CO within 48 hours.
At this point, the player now has 15 days to contact and resolve this issue with his CO before the system processes the player further, as listed in section 2 - JAG processing.
Becoming AWOL is something that all members should try hard to avoid, as it WILL leave a permanent entry on your records. The main thing to keep in mind is that once a member goes AWOL, it CAN NOT be changed by the system or by reporting a game, ONLY the upper COC can return the player to active. This makes sure that EVERY member is treated exactly the same, and ALL would have the permanent entry in their records. The other thing to note is the return to active from AWOL is "at the discretion of the upper COC" AND done by placing the member on PROBATION. A player that goes AWOL from Probation would be considered "problematic", and when determining if he should be returned to active or simply removed would be based on the reasons supplied for their successive absence. Any member having trouble only has to contact his/her CO BEFORE becoming AWOL to have the matter dealt with. In the overall scheme of things, we feel this is more than fair, as having someone send a 30 second Email is really not a lot to ask.
Processing of AWOL Members
After 15 days of being flagged AWOL (from active) OR immediately on being flagged AWOL (from Probation), the system will automatically Email the upper CoC for processing of the member for removal. It now comes down to having the member's data removed from the system. At this point, the player is basically considered GONE, and to be returned to active status would NOT be considered the "norm", but a special case. Reaching this point means you have gone AWOL, been Emailed by the system, then ignored it for time allowed. Getting to this point should be avoided as once it gets this far chances are your records will be wiped clean, and once done it can NOT be reversed. Once a player has passed this point, signing up again and starting over is the only option for anyone wishing to still be a member. Please note that any player that does this more than once will more than likely be prohibited from rejoining GNSF. We are here for serious players that want to be here and play, not just have their name displayed on a site.
Return from Leave
The system also does a check for members returning from LOA and ELOA, and sets the player's status back to active once he logs a report. This way, to become active, a "deliberate action" by the player is required, ie logging a mission. The system will then change the status to active, place an entry in the persrec (Status returned to active), and Email the player, CO and COC of the status change.
Since the system is automatic, a member must be SURE they are done with leave BEFORE logging a game. Once a single game is logged, the player is now set to active and must again follow the logging requirements just like every other active player.

5. AUTOMATIC EMAIL REMINDERS

The system sends the following emails based on time span from the member’s last logged game.
• Four (4) day prior to being placed AWOL (from active, LOA and ELOA). This is a warning Email. You now have 4 days to report a mission or request a Leave.
• Thirty (30) day prior to being placed AWOL (from Special Deployment). This is a warning Email. You now have 30 days to report a mission or contact the COC.
• The day the member is placed AWOL (all but Probation). You must now contact the COC within 15 days to resolve this issue.
• The day the member is placed AWOL (from Probation). You must now contact the COC within 48 hours to resolve this issue.
• Fifteen (15) days since the member was placed AWOL. This Email goes to the COC to start removal proceedings.
With the way the system operates, it gives more than sufficient warning to members to avoid AWOL. If these are ignored by the member then we assume he has left GNSF and no longer wishes to be a member. With these reminders, there is no reason a member needs to go AWOL, and this is why we will NOT grant or extend leaves for AWOL members. If a member can’t exercise the simple common courtesy of contacting the COC BEFORE he/she is flagged AWOL, then he/she does not deserve any special considerations.
If you will be unable to play for A SHORT amount of time (excess of 2 weeks, less than 30 days), please send that information to your CTF in the form of a "out of office" notification Email. This way, he will know you are gone for a specific period of time.
We will do all we can to provide the leave time a player requires, but we will NOT keep a members records just for the sake of having their name listed. We want to make sure no player is penalized due to RL issues, but having an extended leave because you don't feel like playing anymore will NOT happen. While we respect a person's right to privacy, some explanation must be supplied for leave requests.
Please note that as part of an online group we must take people at their word. If at any time a person has been found to have lied in regards to a leave request (ie said he was on Military assignment, but found playing in another group), that member shall be processed for removal from the GNSF. All we have as members of an online group is our word, and without that, we are nothing.
When a member is done with his leave, returning to active duty is done by;
1) Playing and reporting a game, AND
2) Notifying Your Commanding Officer that you are back from leave.
Once a player on leave reports a played game, the system will automatically terminate any leave condition the player has on the next scheduled check. If the player’s status is not automatically set back to active in the next 48 hours after the report was submitted, the player must contact the CTF to make sure his status is set back to active.

6. SUMMARY OF LEAVE PROCEDURES

• ABSENCE FOR LESS THAN 30 DAYS = ADVISE YOUR CO
• ABSENCE FOR BETWEN 30 and 60 DAYS = MUST REQUEST LOA TO YOUR CTF.
• ABSENCE FOR BETWEN 60 and 90 DAYS = MUST REQUEST ELOA TO YOUR CTF. CTF WILL SEND REQUEST TO COC
• ABSENCE FOR MORE THAN 90 DAYS = MUST REQUEST SPECIAL DEPLOYMENT STATUS TO YOUR CTF. CTF WILL SEND REQUEST TO COC.
• IF AT ANY TIME DURING ANY LEAVE MORE TIME IS NEEDED, REQUEST AN EXTENSION TO THE CTF. CTF WILL SEND REQUEST TO CNO.
• ALL LEAVES START AT THE DATE OF THE LAST REPORTED MISSION
• RETURN TO ACTIVE DUTY FROM LOA AND ELOA BY LOGGING A MISSION REPORT WHILE ON LEAVE
• RETURN TO ACTIVE DUTY FROM AWOL/SD/NES/RETIRED, BY LOGGING A MISSION REPORT AND SUBMITTING A REQUEST TO THE COC. IF AWOL WHILE ON PROBATION, ACCEPTANCE OF YOUR RETURN IS FAR FROM GUARANTEED.

V. COMBAT OPERATIONS

For specific details on game specific rules and outcome conditions, refer to the GAME SETTINGS section for the game in question. Some common themes are addressed below.

1. INTERNET PLAY

When requesting a game with other member(s), add the sim you want to play to your request so the person will know which Sim you want to play.
If you have questions about setting up to play on Internet, feel free to ask a fellow member of the GNSF. The host of the game is normally decided by one simple factor, who has the best and fastest computer or connection for the job. In the end the senior ranking officer in the game will make the final call.

2. CHEATS AND BUGS

During GNSF White Ops, no member is allowed to use cheats. Cheats are considered any "in game setting or feature" specifically listed as a cheat (example, 3D in 688, respawn in GR) or "added mod or patch" that is not listed as "official".
The use of any documented or undocumented game bugs is forbidden at all times and operations.
Any use of cheats is grounds for disciplinary action. If a player continues to cheat during game play then please contact your CTF and they will report it to the proper Office.

3. WEAPONS FREE

Some games will have a weapons hold, where no firing of any weapon is allowed during this time (Dangerous Waters and Janes 688). For these games, no weapons can be fired until Weapons Free (WF) is reached.

4. VOICE COMMUNICATIONS

To reduce the amount of confusion during a game, all players should move to a unique Ventrilo channel for game play comms. If playing team Adversarial games, each side should have a separate and unique channel. All communications during game play should be done in an appropriate channel in Ventrilo, so others know what type of game you are playing (and may wish to join). NO game play comms should be done in the lobby or Officer’s club channels

5. SALUTING

When you enter a Game Waiting Room, you will Salute those already in the room, with the highest ranking person in the room returning the salute. Only the highest Ranking person in the room will Salute someone joining, unless a MOH recipient enters the room, then ALL will salute. If a game is currently in progress when someone enters (waiting area), NO PLAYER salutes until the game is complete and ALL players are back in the waiting area

6. REPORTING IN

When players start the game and transition from the waiting area into game play, they shall call IN to let all other players know they have made it in. For specific details on reporting in, refer to the GAME SETTINGS section.

7. DROPPING FROM GAME OR LEAVING

If a player drops from the game in the middle of game play, then game play will continue for the remaining players IF the game supports this (host drop on some games WILL kill the game for all). Players that remain in a game and can continue will report the game as normal, indicating which player(s) dropped. For Specific details on drops, refer to the GAME SETTINGS section.

8. SILENCE OF THE DEAD

After being killed or otherwise destroyed you are required to call "DEAD" in the chat window or on Ventrilo, notifying everyone of your demise. You may
stay and watch the rest of the battle, but you are NOT allowed to discuss anything that you see in the game with the others, dead or not, until the game officially ends. Dead men tell no tales, and offering help to one still alive in the game IS cheating.

9. NEUTRALS or FRIENDLIES

NEUTRALS are defined as targets that you must not kill, like in RL: unarmed vessels, civilians etc (unless specified in the mission's objectives).
FRIENDLIES are defined as your allied team mates (either AI or Human)
NEUTRAL or FRIENDLY kills are NOT allowed, and if you make any, you MUST enter a LOSS as the game outcome. Your legitimate kills however will still be added to your kill record. Biologicals (shrimps, whales, pigs, cows etc) are NOT considered Neutral or Friendly. If you kill them, have a BBQ! (then deal with Greenpeace... ).
TRAPS are defined as any device that is intended to kill you (SAM Sites, Captor mines etc) . They are a weapon whose purpose is to kill you. You can destroy these at any time.
The CTF will monitor the logs, and if one is found with a neutral or friendly kill, the CTF will make sure the game is entered as a loss and the Neutral kill(s) also entered.