Officer Articles of Conduct

Revision 06-29-2008

Definitions:

CinC - Commander in Chief
There is one Allied CinC and one Axis CinC. This is the highest level of the High Command and this person is ultimately responsible for their entire side.

Senior Command - The CinC, Chief of Staff and Deputy Chief of Staff
There is one Allied Senior Command and one Axis Senior Command. These three, one set on each side, work together to manage the rest of their HC.

HC - High Command
This defines the entire Officer structure, from the CinC to the last 10OIC.

CO - Commanding Officer
The person in charge of a Unit, i.e., a Brigade, Division, etc.

XO - Executive Officer
The person second in charge of a Unit, i.e., a Brigade, Division, etc.

OIC - Officer In Charge
The persons assigned leadership roles in a Brigade.

SIO - Senior Investigating Officer
The person leading a Disciplinary Review Process investigation.

OCS - Officer Candidate School
The training program that will prepare a player for HQ3 Command.

Mission Statement:

The WWIIOL High Command is a player run organization that serves the larger WWIIOL community through its volunteer staff’s dedication and commitment to the organization’s ultimate purpose noted below. While a fully volunteer-based society, the HC is a CRS mandated structure designed to enhance gameplay quality for the entire WWIIOL community.

WWIIOL is designed, and supported as a game that allows its players to define the course and flow of the “war.” In that light, specific game systems and functionality are delivered from CRS to the HC in ongoing support of a fully player-run command layer. The HC structure represents the marriage of game technologies and services with community dynamics to deliver a system that is unprecedented in the online gaming world. Indeed the WWIIOL HC is a fully functioning High Command structure without equal.

The ultimate purpose of the HC is to conduct military-style combat operations in the WWIIOL game theater, and all administrative functions that these operations require. The HC is not only responsible for the planning and conducting of strategic and tactical combat operations in game, but it also is responsible for policing its members, managing its member lists, conducting Research and Development choices and Deployment of combat forces and assets in game. The ultimate outcome of all this activity is a more enjoyable and intense gaming experience for all subscribers.

The CinCs, Chiefs of Staff, and Deputy Chiefs of Staff manage the WWIIOL HC. Those highest command positions are guided by the CRS Community Management Staff, which are CRS employees.

I. Rights of the Players

1: HC staff will not attempt to compel other players to follow their orders. They have authority only over players who are members of the HC. They are to guide and lead the player base using strategic and tactical tools given to them by CRS . Some of these tools are: Movement of Brigades and Divisions, Attack and Defense Objectives, RDP and Unit Deployments.

2: HC staff will work towards earning the respect of the community. The HC staff must be willing to listen to the community for their concerns and ideas. They are there to enhance the gameplay of the players and must make every effort to maintain a working relationship with the community.

3: HC staff will not engage in rudeness or other insulting exchanges in the forums or in game. Rants, flames or whines are not allowed while you represent the HC, and public complaints about the game or CRS is incompatible with membership. HC Staff shall utilize the Chain of Command in reporting complaints on the game or CRS. HC staff shall be positive in public, and not post in a way that would lower the morale of their community.

II. Joining the HC and Responsibilities of the HC

4: Membership in the HC is voluntary and is open to players who wish to take part in the role-playing aspect of the High Command. The Command is a role-playing element within the community. Those who volunteer to take part in this role-playing will take on a role for the position they hold. Qualifications are maturity, experience with the game, the ability to organize, an active game account, completion of the OCS program and the ability to put aside your personal time for the enjoyment of your fellow players. Membership in HC does not come automatically with a subscription. Participation in the High Commands is granted or revoked at the discretion of the Senior HC Staff.

5: HC staffs are ambassadors of CRS. The rest of the gaming public will be looking for your example and assistance. You will provide it, treating all members of the community with the utmost respect and cordiality.

6: HC Officers must follow the official Chain of Command and carry out the instructions of Senior Officers, to the best of their ability. If unable to carry out orders or duties, the Officer will delegate the task to subordinate Officers in the Chain of Command. High Commanders must deliver for their players. If you are unable to deliver and provide your players adequate leadership and or representation, then you must step down, making way for others behind you who can.

7: HQ3 COs and XOs may belong to a squad and keep their squad duties, as long as they can carry out their HC duties as well. Commanding Officers of HQ3 level will not place their squad’s interests before their HC duties. They must be able to manage both. Some HQ3 have multiple squads, and players who are not in squads attached to them. They all must be equally taken care of.

7.1: As such, HC Officers above HQ3 Commander must temporarily drop squad responsibilities in order to be eligible for promotion, and for the duration of service in HC. Senior Officers cannot represent both the interests of HC and a squad at the same time. Squad structures and command lines do not supersede HC organization and protocol.

8: In order to be eligible for membership in the HC, Officers must demonstrate ability and commitment through a training program that will prepare them for HQ3 Command. This training program is mandatory and is a pre-requisite for entry into the bottom rung of the HC, as a Colonel, and deputy to a HQ3 Commander. The training staff of the HC conducts OCS training.

9: HC Officers are limited to serving in one in-game branch with their chosen country. HC Officers are allowed to take on other responsibilities in CinC Staff positions for out of game organizations with approval of the Senior Command. HC Officers should only take on these additional responsibilities if they are able to perform all of their roles. HC Officers’ primary responsibility is to their office and the players. Officers should not take on any other role if they are unable to accomplish their primary responsibility.

10: To be eligible for a Commander position within a unit, one must be a member of that unit for no less than 30 days. This time period starts when the player first officially becomes a member of the unit. In the event a unit is vacant, the Branch Commander may approve a player to take the command of the unit if the player shows that they would be able to fill that position and provide positive leadership for that unit. This is in place to allow a relationship between the unit and the future Commander to be built and allow respect from the unit to be earned by a future Commander. It also allows time to insure the future Commander and the unit are right for each other.

III. Promotions Within the High Command

11: Promotion is based on merit and time spent in the HC. An Officer can be promoted a maximum of 2 ranks in a single promotional event, but this is rare and only done when exceptional need or ability is demonstrated. Promotions are done with the approval of two levels up. If a HC Commander is being promoted to HQ3 CO, the Commander must be approved at the HQ2 and HQ1 level. Once a Commander is approved two levels up, a notification of the promotion must be sent up the Chain of Command to notify all Officers above and to insure all permissions are updated in a timely manner.

IV. Actions and Guidelines While in the High Command

12: Commanders will present a united view in the eyes of their troops. Disagreements with official HC policy is to be handled in private, in the restricted forums reserved for such discussion. Prior to a decision being made, discussion is welcome. After the decision is made, all Officers will give a united image in public. To publicly disagree with HC policy is reason for termination.

13: HC Staff will treat each other professionally, as fellow Officers, with all the respect that this implies. Remember that your subordinate could end up being your superior. Infighting and disagreements are to be expected, but are never to be conducted in public. Personality clashes that become disruptive will be dealt with in the harshest terms possible, namely, summary dismissal of both parties.

14: Leave of absence. It is understood that real life must come first. In the event an Officer must be away tending to real life issues, then it is the Officer’s responsibility, as soon as reasonably possible, to inform their Chain of Command and the Commander directly up the Chain of Command. For a leave of absence lasting more than two weeks, the Chain of Command should consider a replacement, unless special circumstances warrant an extension given only by the Chain of Command. After one month of not being in game, the Commander will be automatically removed from their position. When they return they may take an open position at the lowest level and work their way back up the ladder. The HC is responsible for providing leadership to their team. Absent Commanders do no good for anyone and raise the work of others. No approval will be allowed for more than 30 days out of the game. Notice of leave of absences that are approved shall be sent up the Chain of Command for notice, all the way to the CinC.

14.1: The Commander in Chief may not be absent from the game for more than 72 hours without notice to their Chief of Staff and the Community Management Team. In the event that more time is needed, it will be granted up to two weeks away from the game, if previous communication is made.

14.2: Commanders need active subscriptions in order for them to be able to lead in the field. If a Commander is unsubscribed from the game for more than 4 days, they forfeit their position. The role of Commanders is on the field leading their troops. Without a subscription they are unable to fulfill the need of their role. In the event that a relief on this is needed, the Commander is responsible for communicating that need to the Commander in Chief, who will discuss options with the Commander, and if needed, communicate with the Community Management Team for options to help the Commander.

14.3: Officers on leave of absence may play the other side with the approval of the Commander in Chief. The time away shall not exceed two days due to the fact that Officers are community members who have stepped up to lead the community. An Officer may only request this leave of absence to play the other side once per campaign. When playing the other side they are unable to fulfill the obligations that they volunteered to do.

14.4: Officers not on a 2-day leave, caught playing on the opposing side, will be dismissed from command.

14.5: Senior Commanders, both Allied and Axis, are expected to have open lines of communication with each other to enhance the game play for all players under the leadership of the High Commands.

14.6: Commanders may work with Commanders on the other side to enhance the game. Planning events like captures and rescues, convoys, etc are allowed long as it is in a professional way and that it does not impact the operation of their team on the field.

15: Commanders have a direct communication system with CRS representatives through their CinC. Issues with the game should be communicated up the Chain of Command where the CinC will communicate those issues with the Community Management Team. Their response will be communicated back down the Chain of Command by the CinC. Complaining down stream is destructive, bad and is looked down on.

16: The .hc channel is for command purposes only. Disrespectful communication or other communication not in the best interest of the team is forbidden. Lower command communication should take place on the respective in game command channels. The use of the High Command Message of the Day (.hcmotd) is restricted to Branch CO and above. This command should be used to give guidance to the HC Commanders to the objectives and goals of the CinC.

17: Fallback and Hold-At-All-Cost dot commands will be the responsibility of the Officer that is in command of the city on the ground and they will make all judgment calls on what action is needed. All other Officers are expected to respect their wishes and grant the action they request.

18: The use of .axis / .allied commands are to be used to promote the units of the command. Each use must have in them the unit requesting help, who the mission is by and what channel they are on, if not on the default mission channel. The uses of emergency or urgency terms (911, ALL, NOW, IMMEDIATELY, PRIORITY etc) are forbidden. Misuse of this tool will result in a written warning from their Chain of Command on the first violation. The second violation is removal from the HC toolset for 3 days. If another violation happens, removal from the HC will happen.

18.1: Statements of encouragement are allowed by the Branch Commander or higher. If no officers of these levels are present in game then the Senior Officer in Charge currently with .allied or .axis privileges may issue .axis / .allied messages of encouragement. The usage of .axis / .allied may also be used to give advance warning to the player base of intended moves of Bde/Div and of the withdrawal of AO's. I.E. ".Axis: xxx Bde/Div is being moved from xxx town to xxx town. Please adjust your missions accordingly." ".Allied The attack AO on xxx town is being withdrawn. Please RTB at this time and contact your CoC for new objectives." Any /allied or /axis announcement (or similar that gives the same effect) given by an HC Officer must not be repeated within any 5 minute period by that HC Officer.

19: All Officers will be held accountable for their actions, in game and out. Management of all Officers is ultimately the responsibility of the Commanding in Chief, through the Chain of Command. Violations of the Articles of Conduct will be handled per the Disciplinary Review Process.

19.1: Disciplinary Review Process (DRP)

A: All minor conflict or misbehavior of an officer should be handled at the lowest level possible that insures resolution. Incidents of a severe nature or those requiring disciplinary action will be sent up the Chain of Command in the form of a written report/grievance with as much supporting evidence as possible. The evidence should include any screenshots, chat logs, recordings of TS chat, copies of private messages and email that relate to the incident or incidents. Only the senior command officers of the parties involved will be notified of the incident. No evidence or disciplinary action against the violating officer will be announced or shared publicly.

B: Senior Staff (CINC, COS and DCOS) will review the evidence, contact the reporting officer and the accused officer for their explanation of events if needed, and will then discuss any actions that may need to be taken. Actions may include: No action, verbal warnings, written warnings, suspension or removal from the HC.

C: The CinC will make the final decision on any disciplinary action taken, is responsible for carrying out the action and recording the actions taken in the officer's personnel file. Once an investigation is completed and a decision has been reached, it is final, binding and shall not change. There is no appeal process.

D: At any time during or after the investigation the Community Managers may make inquiries of the parties involved.

20: Commanding Officers are responsible for the enforcement of the Articles of Conduct for those directly under them. Fair, impartial and thorough investigation is required of a disciplinary review Senior Investigating Officer. Failure to do so is a violation of this Article.

20.1: As an Officer of the High Command you are entirely responsible for maintaining the confidentiality of your password and account. Furthermore, you are entirely responsible for any and all activities that occurs under your account. Your Officer persona is empowered with various High Command Tools that have been given to you with the trust of the High Command and Cornered Rat Software that, as you know, can have a great deal of impact on the game environment. As an Officer, it is your responsibility not to allow anyone access to or use of your Officer account. Unauthorized use of your account, that results in a breach of the AOC or the TOS, may terminate your participation in the High Commands of WWIIOL.

21: Term limits will be imposed in two categories; the CinC and those refusing promotion. CinCs are limited to a two month static term that will begin on the 26th of every other month. This promotes healthy forward movement of all Officers below that position. Those refusing promotion may only refuse twice. A third rejection of promotion will result in immediate retirement of that Officer.

21.1: In the event that no Officer is available to promote into the position opened by the termination of the third term Officer, the Senior Command can approve him to stay for another, or subsequent term(s).

V. Commander in Chief Requirements

22: The Commander in Chief must maintain a visible image within the community and be active within the community. This includes a presence in game and on the forums. The Commander in Chief should reach out to the community and work to earn their respect.

23: The Commander in Chief must run at least one CinC level operation per month. He may utilize the Chain of Command to organize it, but the operational plans must be joint operation style and available through the securest way possible to the lowest grunt on the field so they know of the operation.

24: (removed)

25: Commanders must do what is right for their team as a whole at all times.

Final Statement:

The Articles of Conduct are to protect both the players and the command organizations. Changes to these Articles must be approved by the Commander in Chief of both commands and the Community Management Team before they go into effect. Both commands follow the same Articles of Conduct. The commands are role-playing and have a Chain of Command. Each level has different roles that they must fulfill in order to maintain their role. It is not mandatory or given that a player must be a Commander. They volunteer to become a Commander to better their team through working with the Chain of Command to organize their team.



Revision History:
05-27-2008
Article 21:
From:
CinCs are limited to a four-month term. In the event of campaign reset two weeks prior, the CinC term expires at the start of the next campaign. If the campaign is not completed by the four month point, the CinC continues their term until the end of the campaign.
To:
CinCs are limited to a two month static term that will begin on the 26th of every other month.

Article 24 permanently removed.


11-10-2007
Article 18: Removed sentence "Statements of encouragement are allowed by the Branch Commander or higher."
Added Article 18.1


08-09-2007
Added 19: B1
Suspended Article 24:
24: The Commander in Chief is responsible for submitting RDP choices and Deployments on time. Failure to do so more than twice without good reason can result in dismissal of the Commander in Chief.


06-29-2008
Revised 19.1 DRP