No replies to this topic

[Impulse 9]

United Operations Standard Operating Procedures

Addons

The Game Server Officers will be expected to design and manage a system which achieves:

• Simple one stop updating of game content for players.
  
• Hassle-free integration of new data distribution systems.
  
• Obeying the decisions of regulars in regard to adding or removing addon content, but firmly and assertively offering his technical expertise on matters to properly educate regulars of the impact of their decisions.
  
• Carefully consider, research and test all possible technical changes in order to ensure as little stress on play as possible.
  
• All regulars shall be responsible, when capable, of assisting other regulars with technical issues. The Game Server Officerpurpose is to direct and be the single point of contact for all things regarding this topic.

Mission Making

• Mission Requirements
  
  • Missions may only contain addons as per the list of addons supported by United Operations.
    
  • All missions must contain a coherent schema of play. This involves a briefing, logical objectives and the means by which to accomplish them.
    
  • Critically malfunctioning missions may be removed at will, with a notification sent to the mission maker.
    
  • Most missions require reasonable lose conditions. Joke missions are excepted from this rule.
    
  • Mission names must be prefixed as such:
    Cooperative missions (“COOP”/”CO”): CO##_NameV1
    Team versus Team (“TVT”) missions: TVT##_NameV1
    Joke missions: LOL##_NameV1
    
  • Modifications to missions (i.e. "new versions") must have a unique file name and unique version number indicated in the mission name.
    
  • If your mission has an intro, it must be able to be toggled, and must be off by default. Loud sounds embedded in the mission are to be avoided where possible.
    
  • Mission must perform reasonably, both on clients and on the server.
    
  • All missions submitted post September 11 2010 must contain documentation or some indication of what medical system is included for play. As per SOP.
    
  • In order to fasten the change between seeder and real missions I propose a hard limit of 20 slots for every seeder mission that was NOT made by community members[insurgency/domi], the only missions that will be exempt from this are seeders made by community members like Krause's Executive Outcomes.
    The mission makers are responsible for implementing this if they edited any seeder missions outside the community.
• Mission Submission Process
  
  • Once a mission is complete and ready to be submitted, the mission maker is tasked with ensuring that the Mission Requirements are fulfilled, as per the previous section of this document. Missions which violate the Mission Requirements will necessitate a “strike” on the offending mission maker. Three strikes effects the suspension of automatic acceptance of new missions in lieu of quality control by the Mission Making Officers.
    
  • A new thread is created, as per the template provided in the mission making forum. This thread informs the community of regulars as well as the Mission Making Officers as to the introduction of new content.
    
  • The mission maker is then expected to upload the mission to the /submission directory on the test server FTP. Information regarding how to access and use the FTP is provided in the mission making forum.
    
  • It is the responsibility of the Mission Making Officers to provide an informative list of all missions currently on the server. This information is to be condensed into a singular thread, with brief, succinct summaries of the basic mission types not exceeding a few words or sentences.
    
  • United Operations Training Center (UOTC) missions will be exempt from all SOP requirements, shall be prefaced in title and file name by UOTC_ and shall not be deleted off the training servers.

Web Services Office

Duties pertaining to delegates of the Web Services Office:


1. Moderators are delegates of the web services office. Moderators are charged with the maintenance of the forums, polls and calendar entries.

1.1 - A moderator MUST as part of their general duties:

1.1.1 - Communicate any problems which they can foresee to a WSO via PM, forum post or report center.

1.1.2 - Communicate any deletion or unapproval of topics, posts, polls or calendar events to a WSO via PM, forum post or report center.

1.1.3 - Communicate any warning given or moderated person to a WSO via PM, forum post or report center.

1.1.4 - Be familiar with the forum guidelines and uphold them.

1.1.5 - Close a poll automatically based upon the polls creation time / date.

1.1.6 - Polls must not be closed early.

1.1.7 - Forum topics, posts and polls must not be edited or closed, except under forum guidelines or for organizational or technical reasons.

1.1.8 - Moderators will not talk about reported topics, posts, polls or calendar events except to other moderators or WSO's.

1.2 - A moderator may as part of their general duties:

1.2.1 - Restore or delete forum topics, forum posts, polls and calendar entries.

1.2.2 - Edit forum topics, posts, polls and calendar entries.

1.2.3 - Move or merge forum topics, posts, polls and calendar entries.

1.2.4 - Approve or unapprove forum topics, posts, polls and calendar entries.

1.3 - A moderator may as part of their additional duties:

1.3.1 - Warn or moderate individuals who violate the forum guidelines.

1.3.2 - Add or edit a users information dependent upon a user request, via a sanctioned poll or in relation to a warning / moderated item.

2. Editors are delegates of the web services office. Editors are charged with the maintenance of news articles and official documents within the forums.

2.1 - An editor MUST as part of their general duties:

2.1.1 - Communicate with different departments regarding news articles to be placed on the system via PM, forum post or report center.

2.1.2 - Adhere to the forum guidelines with regard to the news article system, news and announcements and important information sections of the forum.

2.1.3 - Editors will not talk about reported news article comments except to other moderators or WSO's.

2.1.4 - Communicate any warning given or moderated person to a WSO via PM, forum post or report center.

2.2 - An editor may as part of their general duties:

2.2.1 - Add, edit, move, merge, unapprove, approve, delete, undelete news items or folders within the news article system, excluding the SOP and Charter documents.

2.2.2 - Add, edit, move, merge, unapprove, approve, delete, undelete comments within the news article system.

2.2.3 - Add, edit, move, merge, unapprove, approve, delete, undelete forum entries within the news and announcement section of the forum.

2.2.4 - Add, edit, move, merge, unapprove, approve, delete, undelete forum entries within the important information section of the forum.

2.2.5 - Add, edit, move, merge or delete newly sanctioned SOP changes into there appropriate page.

2.2.6 - Add, edit, move, merge or delete newly sanctioned Charter changes into there appropriate page.

2.3 - An editor may as part of their additional duties:

2.3.1 - Warn or moderate individuals who violate the forum guidelines, with regard to the news articles, news and announcements and important information sections of the forum.

3. Web Service Officers (WSO's) are tasked with ensuring the forums and website are operational.

3.1 - A web service officer MUST as part of their duties:

3.1.1 - Communicate with other WSO's.

3.1.2 - Communicate with delegates of the office mentioned above.

3.2 - A web service officer may as part of their duties:

3.2.1 - Switch into any role described above.

3.2.2 - Dismiss delegates of their position via PM or forum post.

3.2.3 - Create, edit or delete new delegate titles or SOP's via this SOP document.

3.2.4 - Provide training materials to newly appointed delegates.

3.2.5 - Provide logs or information when requested about the activities of moderators and WSO's, except where the logs would violate the privacy and security of individuals, moderators or WSO's.

Server

• Missions will be selected by a public game admin, only an Officer or appointed delegate with game server powers may override the publicly appointed game admin. New logged in admins should attempt to provide enough time for the current mission to reach a logical pause point and broadcast that the mission will be called in due time, not abruptly end the mission where possible.
  
• A leader ("commanding officer"/"CO") will volunteer in each mission to organize the players into a coherent tactical force. The CO's plan must be respected.
  
• The mission may be terminated ("called") by the volunteered CO of the mission.
  
• Players will be expected to follow the command hierarchy within the mission, to obey orders, and to perform their "job" to the best of their ability. Players disobeying direct orders will be removed from the game.
  
• The times preceding and following mission play may involve chatter or discussion about the previous or next mission. Once the mission loads, keep chatter to a minimum.
  
• Keep the side chat channel clear of chatter; use only to notify the community of players in violation of the charter rules and SOPs. Communication should be restricted to ACRE TeamSpeak on ACRE servers and group, direct and command chat channels on ACE servers for purposes of gameplay.
  
• You must be present in the game server channel on TeamSpeak if you are in game.
  
• Restrictions on where and when certain missions, in exception of the mission making rules, may be played do apply.
  
• If an open ended mission is being played (IE: Domination, Insurgency, TFOR Ect.....) and a REGULAR member of UO comes in and request a mission change, the logged or voted in admin will conduct a vote of all players in the Game channel AND waiting room channel in TS. If the motion for mission change passes the admin WILL change the mission or give up admin to another player. Players in the current mission will have 15 MIN to finish their current objective.
  
• As per August 4th, 2011 game Moderators must have at least 100 hours logged on the server to qualify for and to remain in appointment

TeamSpeak

• Only regulars are allowed to create and delete their own channels. All other channels will be deleted.
  
• All regulars may move non-regulars. Misbehaving regulars may be temporarily banned/kicked by other regulars for up to 15 minutes when an officer is not present or able to assist.
  
• Officers have ultimate power to create, delete and edit permanent channels, to issue permanent bans and to revoke or modify other regulars TeamSpeak powers.
  
• The game channels are to be free of casual chatter while games are running.
  
• Non-game private channels have no rules to govern the behavior of regulars.
  
• Rules on "Flavor icons": a "flavor icon" is defined as a TeamSpeak icon which is assigned for means of personal expression. Up to one "flavor icon" may be assigned to regulars, upon request of an officer. Flavor icons are available to all regulars and no specific requirements may exist for receiving them. UO groups of regulars playing other games other than Armed Assault may also identify themselves with an icon for purposes of organization and identification; these icons are considered "flavor icons" and may not exceed 1 icon at any time. Both flavor icons and group icons may not grant special powers in excess of the charter and are merely cosmetic and organizational aids.
  
• Unnecessary speaking, noise and distractions while a mission is being slotted in and/or while a briefing is taking place is prohibited.
  
• Recording in the game channels(Primary, ALT, any test or other official UO server) on TS is forbidden when not IN-GAME or recording gameplay or training.
  
• As per June 13th, 2011 all officers are TeamSpeak administrators.
  
• As per August 4th, 2011 game Moderators must have at least 100 hours logged on the server to qualify for and to remain in appointment.
  
• No copyrighted materials may be uploaded to the TeamSpeak File Browser system.
  
• In-game name and Teamspeak name must be similar enough to be immediately identifiable as the same user.
  
• Regulars may have only one non-nested Teamspeak Channel of their own within the Barracks subgroup, an additional private personal sub channel may therein be created.

Public Relations

The PR team will utilize suggestions, contributions and material from all over UO to promote community growth and expand UO's interest. Anything labeled "Official" should be sent through the PR office so it can be checked for quality and to ensure UO's interest are being promoted. Examples of this are promotions videos, posters, post on other sites/forums and any other propaganda. Any material to be listed as "Official" will be placed in the propaganda thread in the PR HQ section of the forums so we can have records of everything. The Public Relations Office will be responsible for ensuring events are scheduled either by the PR office or by another Regular. PROs are responsible for maintaining an active event schedule.

• All media, posters, images that will be used in official PR operations are the property of the UO community. It can be reused/posted at will to help promote UO. This means if you are making an item for UO, the PR office will use it as we see fit to promote UO across as much of the ARMA world as possible.
  
• There will be no restriction on anyone making propaganda for UO. Everyone is welcomed and encouraged to help the PR team. Public relations is a team effort and we need the whole community to help us grow. The PR office will not restrict anyone from creating anything but we must ensure that UO is being portrayed in the best way possible and that the community's interest are being met. If we feel someone or something is not promoting UO in the right way or someone is taking the wrong approach the PR will work with that member, nothing should be labeled official until it is reviewed by the PR office.
  
• The Public Relations office is the main source for community events, although ALL Regulars are welcome to conduct their own events in accordance with the charter.
  
• Any issues you have or if you need any help with anything please contact us at our forums or by official email publicrelations@unitedoperations.net

Justice

• Those in violation of the SOPs and charter rules will be warned and may be kicked by regulars. The Game Server Officer and Web Services Officer may issue a ban within their respective domains in order to neutralize a misbehaving player until further adjudication is possible.
  
• More permanent measures may be taken through the form of a poll to semi-permanently or permanently ban offenders. This is accomplished by petitioning a Forum Officer to create an anonymous poll and providing a rationale for the ban. The Forum Officer then posts the poll, along with the rationale and opens it for the vote of the community of regulars. Forum Officers are also responsible for clearly posting any SOPs or rules which govern the operations at hand.
  
• If a simple majority prevails in the vote, the offender is banned for one (1) month, if a 2/3 majority prevails the offender is banned for three (3) months, if a 3/4 or greater majority prevails then the player is banned for one (1) year.
  
• A banned player may appeal to be unbanned after a period of seven (7) days for one (1) month bans, thirty (30) days for a three (3) month ban and ninety (90) days for one (1) year bans.

Revisions:

1. June 13, 2011: Revised by Krause as per http://forums.united...rter-2011-06-13
2. August 6, 2011: Revised by Krause as per http://forums.united...ion-2011-08-04/
3. October 15, 2011: #8 TS SOP reworded by Krause
4. November 2, 2011: #6 TS SOP rewritten by Krause re: flavor icons
5. November 13, 2011: #3 Forum SOP, revised by Sceaduwe due to a forum software change
6. November 25, 2011: Replaced all mentions of "addon officer" with "gameserver officer", revised server SOP #1 to correlate to include new delegate responsibilities and established practices by Krause
7. December 21: Added UOTC section to mission SOPs by Krause
8. January 12, 2012: Forum SOPS as per http://forums.united...ums-2012-01-12/ by Krause
9. January 19, 2012: TS sop added restricting uploading copyright materials
10. January 23, 2012: Web Service Office SOP's rewritten by Marvin, Impulse and Sceaduwe.
11. February 19, 2012: TS SOPs as per http://forums.united...tion-2012-2-16/ by Krause
12. March 17, 2012: TS SOPs as per http://forums.united...ak-re-ts-icons/ by Krause/Impulse9