  |
 |
  |
|||
|
|
|||||
GNSF Rules
Select Catagory | |||
| |||
RULES OF ENGAGEMENT
PREFACE
This preface is meant to explain the following ROE and Standing Orders so that no confusion will occur when using or referencing these documents. The listed documents are set forth as a frame work to ensure courtesy, fairness and justice for all members of the GNSF. Being such, these documents are NOT to be looked at in the same light as a “legal” document taken verbatim, as it is intended to be used for it’s “intent”. That being said, grammar and spelling errors shall not be used as grounds to disregard the intent, nor shall any area where a specific item is not detailed exactly pertaining to the issue in question. In plain English this means that while some area’s are open for interpretation (as they always would be even if it was 1200 pages long), this interpretation shall ALWAYS be to fit the “ intent” of the rule (for example, it does not specifically say you can not blare music while in ventrilo when players are using it for game com's, but this is non the less unacceptable behavior and a show of disregard and disrespect for the other members). Please make sure that while reading and interpreting these rules and procedures you do not lose sight of the intent. At GNSF we want a set of rules and procedure’s that can be used to uphold justice and common courtesies without turning into a “it doesn’t say that in the ROE specifically” fest. We are not here to practice law or dig for loopholes, we are here to keep things fair and fun for every single member.
ENLISTING
ALL new comers to the GNSF are required to review our Rules of Engagement (ROE) and standing orders (SO) completely before submitting thier 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.
When you play against members of outside groups or organizations or other approved individuals, you are a GNSF ambassador and are expected to act like a GNSF Officer at all times. While other 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.
Playing and reporting games played against
players from other online groups or organizations or approved individuals is
now allowed following these mandatory conditions:
- The "outside" player must be a member of an authorized group
or organization, OR an approved individual (see approved player list).
- Prior to game play, you must make sure the player(s) you go up against are
approuved individuals or Members of those authorized organization(s) AND are
not listed on the banned player list . If that organization or individual is
NOT in the approved lists, that game is NOT reportable. You can then ask your
COC for the possibility of adding this new player or organization to the authorized
list. That authorization will be given or revoqued by the FADM after proper
verification.
- In your report, you must list the name (callsign) of the "outside" player(s), PLUS the organization (if applicable) that the player belongs to.
- ANY game reported MUST use the approved GNSF mods/patch for that sim. While other groups may have their own mods, we must use our set to ensure that the scoring system is fair for all members here.
- ANY game reported MUST have a screen shot or debrief available on request.
- GNSF ROE are in effect concerning scoring and reporting at all times.
- 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.
Any group that is listed as a BANNED group is there because of severe problems that stretch well into the 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, with the exception of players on the APPROVED players
list, which may not belong to any group at the time. Authorized and Banned players and groups can be found at BANNED AND APPROVED PLAYERS LIST or by selecting the link from the main page.
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. Next thing you need to do is get ICQ and/or Ventrilo (Current Ventrilo Client listed on the R&D pages), and have it installed and ready to use (if you don't already have it). All GNSF members utilize ICQ or Ventrilo to form up and organize potential games. All new members should add the following people to their ICQ contact list (if they use ICQ). These are the upper Chain of Command (COC) members in the GNSF, so give them your respect. They are accessible and available when they are on line, but once again, we ask you to utilize the chain of command when it comes to the GNSF. The COC chart is available at the Naval Academy. For Ventrilo, you simply install the current client software and sign in.
+FADM Stern GNSF
117598081
+ADM Wallbanger CNO-GNSF
23895587
ADM Paul DCNO-GNSF
140337828
All GNSF downloadable files are considered GNSF property and are not to be disseminated to other virtual groups. Doing so is grounds for dismissal from the GNSF organization.
The main way GNSF players communicate with each other for organizing and starting games is via Ventrilo (and sometimes ICQ ). The GNSF does not allow two members to have the same call sign (ICQ Nick Names) 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.
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 R&D 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.
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.
VERY IMPORTANT: WHEN USING ICQ, DO NOT TO 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.
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 TO's . Our Chain of Command is there for a reason and we ask that you use it.
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 Forces has a CTF (Commander Task Force) as well as Squad Leaders (responsible for a specific sim group). 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 .
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.
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 possition. 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.
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.
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 DONT 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.
Since Real Life MUST always come first, there will be times when a player CANT 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 cant play for a while from one that just vanishes. It is only common courtesy that you let us know if you cant 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.
Activity within the GNSF is monitored via an automated system on the site. It tracks every players reporting activity and watches for anyone that goes more than 30 days without filing a report. Since this system is completely automated, unless the COC sets a player up for leave, the system will flag a player as AWOL (Absent Without Leave) once he goes past 30 days without a reported game. If any member goes AWOL (Absence Without Leave) , the system will automatically change the player's status to AWOL and advise the COC. After 15 more days, a request will be automatically sent to JAG for process and removal of the player.
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 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 JAG directly with instructions that this is considered confidential. JAG
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 can get the time
needed without the automatic system flagging him AWOL. 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 he has left. We will NOT remind people they are in danger of being removed, as that is done solely by
the automated system.
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 system will send the following Email based on time span from the members 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 Assignment). 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 JAG within 48 hours to resolve this issue. Fifteen (15) days since the member was placed AWOL. This Email goes to JAG 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 cant exorcise the simple common courticy of contacting the COC BEFORE he is flagged AWOL, then he does
not deserve any special considerations. AWOL DEFINITION NOTE! - If you are flagged AWOL ; You WILL NOT be granted ANY form of leave You WILL NOT be granted ANY time extention on a prior leave You are AWOL (and will be flagged by the system) if ; You have not logged a mission in over 30 days (AWOL on day 31) You fail to report in (log a mission or contact the COC) before a LOA expires (last report date + 60 days) You fail to report in (log a mission or contact the COC) before a ELOA expires (last report date + 90 days) You fail to report in (log a mission or contact the COC) before a Special Assignment expires (SA Return Date) If you will be unable to play for A SHORT amount of time (excess of 1 week, 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. If you need 30 to 60 days of leave, request a Leave Of Absence (LOA) PRIOR
to being AWOL. That will permit you to extend your absence for up to 60 days starting at the date of your last reported mission. PRIOR to the end of your LOA,
you MUST contact your CO with your intention OR Report a Mission. If you do not, the system will flag you as AWOL. If you need more than 60 days, request an Extended Leave
Of Absence (ELOA) PRIOR to being AWOL. That will permit you to extend your absence for 90 days starting at the
date of your last reported mission. PRIOR to the end of your ELOA, you MUST contact your CO with your intention OR Report a Mission. If you do not, you will be flagged as AWOL. If you need more time, request a transfer to Special Assignment.
PRIOR to the end of your current LOA or ELOA. As long as you stay in contact with your
Commanding officer and keep him up to date on your needs, your leave can usually be extended to fit your circumstances. If you do not, you will be flagged AWOL. AWOL personnel will NOT be granted Leave of ANY form. All leave requests MUST be made PRIOR to being AWOL. Due to Real Life issues and/or RL military
deployment, some members may have to take leaves much longer than 90 days. For these
cases the member's CO must contact the DCNO-GNSF for "Special Assignment"
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. For a Leave of Absence (LOA), the CTF's approval is required. For an Extended Leave of Absence (ELOA), the approval of the DCNO is required. For Special Assignment, the approval of the CNO's is required. All leave requests MUST be made PRIOR
to being AWOL. 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. If the leave required is more than 60 days and
the member wishes to keep the reason confidential, he can contact the FADM and provide a brief reason. Any reasons for leave given this way will be kept
totally confidential. 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 sent to JAG 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 Once a player on leave reports a played game, the system will automatically terminate any leave condition the player has
ont the next scheduled check. The player must still contact the CTF to make sure his status is set back to active. Summary of Leave Proceedures : ABSENCE FOR LESS THAN 30 DAYS = ADVISE YOUR CO ABSENCE FOR BETWEN 30 and 60 DAYS = MUST REQUEST LOA TO YOUR CTF. LEAVE STARTS AT DATE OF THE LAST REPORTED MISSION. 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. COME BACK TO ACTIVE DUTY, BY LOGGING A MISSION REPORT WHILE STILL ON LOA OR ELOA. The GNSF in its goal to make things not only better for all members, but also to make things fair for everyone, has implemented
an automated system for processing members' activity. This will make sure ALL from ENS to FADM are treated exactly the same way, as the system can not play favorites.
The system basically executes once a day and follows the rules listed in the ROE to determine the status of every member. This will not only list overdue members as
AWOL, but also place members back to active when they terminate any leave.
Please note that there are three area's that the system DOES NOT process, "Retired", "NES", and "Special Assignment". The reasons for this are
pretty straightforward. Retired 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, and 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. NES (Non Effective Strength) 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.
Special Deployment:
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. With that in mind, ALL other members not in one of these three groups will be checked automatically by the system every day for
their status. The system currently checks for several things, which break down into sections as follows;
SECTION 1 - Members going AWOL
This section deals with members that do not log a report within the specified minimum time frame for the "Status" they hold,
as follows;
ACTIVE MEMBERS
All active members are checked to see how long it has been since their last report was logged (this number is shown in
the "Task force details" page under days since last report). Any active member that passes 30 days without logging a mission is flagged by
the system. 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.
LOA MEMBERS
All members on LOA and ELOA are checked to see how long it has been since their last report was logged (this number is shown
in the "Task force details" page under days since last report). Any active member that passes 60 days (for LOA) or 90 days (for ELOA) without logging a mission is flagged
by the system (just as above).
PROBATION MEMBERS
ALL members on Probation are checked to see how long it has been since their last report was logged (this number is shown
in the "Task force details" page under days since last report). 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 JAG with a GOOD explaination
of why they have again gone AWOL. Failure to contact JAG 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
players records, the Days since Last report WILL remain constant. Removal of Probation does not give 30 days from that point, its simply removes the Probation flag
from the system and records.
A Few words about AWOL Becoming AWOL is something that all members should try hard to avoid, as it WILL leave a permanent entry on your records.
All that is required is that EVERY member log a mission at least once every 30 days. 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 sent to JAG for removal would be based on the reasons supplied to JAG. Lastly, since AWOL can only be "undone" by the upper COC, a member requesting LOA or ELOA after being
marked AWOL will NOT see this request approved. 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. SECTION 2 - JAG Processing of
AWOL Members After 15 days of being flagged AWOL (from active) OR immediatly on being flagged AWOL (from Probation), the system will automatically Email JAG 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 there name displayed on a site. SECTION 3 - Return from Leave The system also does a check for members returning from "Leave", 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. Retirement
status is only given to a very elite group that has given the GNSF
dedicated and continuous exemplary services and/or to
Officers with many career achievements that had a direct impact on what the
GNSF is today. 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. If you have questions about setting up to
play on Internet, feel free to ask a fellow member of the GNSF. All GNSF members are required to install patches and special files
found at our R&D page. Please note
that only "Official" mods and patches are allowed for scorable game
play. 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. Each player is required to file his/her
own report on the mission reporting page.
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.
Also, if you are playing a game, please make sure you are in an appropriate channel in Ventrilo. That way, others that may wish to join will know what game you are playing, just
by what room you are in. During match-ups and multi-player games in which the outcome will be reported for scoring, no member is allowed to use cheats. Cheats are considered The use of any documented or undocumented game bugs are
forbidden. Any use of cheats is grounds for disciplinary action from the JAG Office. If a player continues to cheat during game play then please contact your CTF and 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 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. Specific details can be found within
the GAME SETTINGS section on the R&D site. 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 on the R&D site. 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 officers club channels. 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 on the R&D site. When one enters 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. ONLY official GNSF DISTRIBUTED mission packs can be logged and scored on the score cards. MISSIONS PACKS ARE AVAILABLE AT THE DRD WEB SITE
ALL GAMES MUST BE LOGGED WITHIN 48 HOURS AND IN THE SAME CALENDAR MONTH, REGARDLESS OF THE LENGTH AND/OR OUTCOME. ALL EXERCISE (EX games) type game 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 Each 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) For specific details on game specific ROE, scoring, and points values, refer to
the GAME SETTINGS section on the R&D site for the game in question. 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. You WILL lose
points for every Neutral or Friendly you kill, so be carefull. 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.
MANAGING ACTIVITY STATUS
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".
they will report it to the proper Office.
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 tails, and offering help to one still alive in the game IS cheating.
GNSF MEMBERS CAN PLAY AND LOG ANY OF THE OFFICIAL SIMs AND PLAY ANY PLATFORM THEY LIKE IN ANY COMBINATION THEY DESIRE.
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 beremoved or otherwise nullified.
also entered.