S6 Department – Game Server Management

From 7th Cavalry Wiki
Jump to navigation Jump to search
This is the Document Release Information
Article Number: SOP-S6-008
Scope: S6 Department – Game Server Management
Version: Version 1.1
Effective Date: 08JAN27
Last Modified Date: 10OCT26
Approving Authority: IMO
Point of Contact: S6 1IC


Purpose and Scope

This standard operating procedure establishes policies regulating how the Regiment uses and operates game servers. It sets expectations for their intended purpose, who has authority to modify their intended purpose and overall policies pertaining specifically to game server management.

Private & Public Servers

At the time of server purchase, the involved stakeholders will decide the purpose of the server. Whether it will be private or public. A private server is locked with a password and is only available to members. It is meant to be used for section practices, field training exercises, private operations and in certain cases, special events involving other communities. A public server is fully accessible to members of the public and is meant for general gameplay, recruiting efforts and public operations.

A public server may only be locked in the case outlined in section 3.1, where it is being used for a special event, and this will only require the authorization of the Battalion Commanding Officer. Otherwise, a public server cannot be locked without the Regimental Commanding Officer's authorization.

Authority

The Battalion Commanding Officer has exclusive authority over the configuration of their Battalion's game servers. This authority passes to the Executive Officer only while the Battalion Commanding Officer is on leave. In several cases, the authority does not extend to the Battalion Commanding Officer and instead falls to S6 Headquarters, the Information Management Officer, or the Regimental Commanding Officer.

The intended purpose of a server is typically decided when the server is purchased. For DEVCOM, this may be dynamic, but the same authority applies. The Battalion Staff/DEVCOM Staff, S6, and General Staff make the decision. The Regimental Commanding Officer holds final authority over a server's intended purpose. Once the purpose is set, a request to change it must be sent through an official ticket to S6, the Information Management Officer, the Chief of Staff, and the Regimental Commanding Officer. Please see section 5 for further information on requesting changes.

Battalion Commanding Officer (Executive Officer during leave) may authorize:

  • Mission and scenario rotation.
  • Game settings within the server's approved purpose.
  • Changes to the mod or add-on list that stay within the server's approved purpose and hosting limits.
  • Whitelists, passwords, and role access for their own Battalion's private server.
  • Restart schedules and event scheduling.
  • Locking of public servers for specific special events, not for section practices or for field training exercises.

IMO or S6 Headquarters may authorize:

  • Hosting-provider settings, server software updates, and backups.
  • Administrator credentials, root or panel access, and security configuration.
  • Emergency changes to stop an outage, exploit, or security threat.
  • Changes that could affect another server or the Regiment's shared infrastructure.

The Regimental Commanding Officer alone may authorize:

  • A change to a server's intended purpose. Including a change between private and public.
  • The purchase of new servers.
  • Closing/cancelling of servers.

Who May and May Not Authorize Changes

S6 will act on a change request only when it comes from one of the following:

  • The Battalion Commanding Officer of the Battalion that is responsible for said server.
  • The Executive Officer, only while the Battalion Commanding Officer is on leave.
  • For game-breaking technical matters and security issues when directed by the IMO, S6 1IC or 2IC.
  • The Regimental Commanding Officer.

The following people cannot authorize a change:

  • Battalion Executive Officer or Battalion Sergeant Major, unless the Battalion Commanding Officer has given approval in writing.
  • The XO while the Battalion Commanding Officer is not on leave.
  • S3 staff.
  • Company and Platoon leadership, NCOs, and individual members.
  • S6 personnel acting on their own initiative. S6 implements approved changes, it does not approve them. Except for cases listed in 4.1 and at the direction of S6 HQ or the IMO.
  • Commanding Officer of other Battalions, for servers they are not responsible for.
  • S6 will not act on a verbal request, a request in a public channel, or a request where the sender's authority cannot be confirmed. S6 will ask the sender to resubmit through the process in section 5.

Change Procedure

When requesting changes to the configuration of a server, it must be done through an S6 ticket in the applicable game server support category. Requests will require written approval from the associated approval authority. The chain of command should typically be consulted prior to submission of a ticket. For example, if S3 is requesting a map rotation change, then they should first consult the game's Battalion Staff prior to submission.

Exceptions

The above policies will be imposed unless an exception has been granted in writing by either the Regimental Commanding Officer or the Information Management Officer. The exception given must include detailed information on which portion of this policy is being circumvented and to what extent. Either by a ticket or a forum private message.

Retrieved from "https://wiki.7cav.us/index.php?title=S6_Department_–_Game_Server_Management&oldid=18025"