Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!
Categories See All →
United Operations Standard Operating Procedures
Web Server Office
Marvin, Impulse 9
Game Server Office
Public Relations Office
Azzwort, Impulse 9
Mission Maker Office
General Provided Services SOPs
(Covers all Services Provided by UO: Teamspeak, Forums, GameServers, etc.)
United Operations is an open gaming community and with its growth we have seen the influx of outside Communities, Clans, and Gaming Personalities join us. On the game servers, on TS and on the Forums these Users are welcomed and encouraged to show their pride and wear their Tags, however, with the influx of outside presences some users have openly and disrespectfully mocked these users and communities by changing their names to impersonate or imply that they are members of groups falsely.
Because of this disruptive and disrespectful behavior the following SOP is being enacted:
- Any user caught impersonating or claiming to be an User or Personality that is not their own;
- Any user caught impersonating or claiming to be in a Clan/Community/Group they are of;
- Any user caught wearing the tags (or variation of said tags) of a Clan/Community/Username they are not a member of;
Any user caught doing the above during any event shall be banned from all services for a period of no less than 2 Days.
1 - Officers have overriding power to create, delete, and edit channels, in addition to issuing and revoking bans.
2 - Do not share/distribute copyrighted works with the teamspeak file system.
3 - Regulars may move, kick, and or ban misbehaving users for a period up to 2 hours when an officer is not present or is unable to assist.
1 - When games are in progress avoid unnecessary communication
2 - When games are in setup/briefing, hold your questions until it is your turn
2.1 - Order of communication for ArmA Series - (Highest Leadership to Lowest Leadership; ex. CO > PL > SL > TL )
2.2 - The Mission Commander will present a plan to the leaders directly beneath their roles.
2.3 - Secondary Leadership will brief by group from highest to lowest. (ex. 1st Company > 1Coy 1PL > 1Coy 2PL > and 2nd Company > 2Coy 1PL > etc)
3 - Keep all non game related communication to a minimum.
1 - Officers will maintain a set of channels for use by themselves and their Delegates as appropriate.
2 - Office Channels will maintain a list of all active Officers per department along with Delegates of the Office.
1 - Registered Members may receive one Personal Channel by way of the Store Page.
2 - Channel Owners are required to list their name in the channel name and or topic for identification.
3 - Channel Owners are free to manage their channel within community SOP and Charter guides.
4 - Channel Owners may have one private subchannel within their channel.
1 - Flavor Icons are any Teamspeak Icon used for expression, interest, group affiliation, and or military affiliation.
2 - Regulars may have up to one Flavor Icon (Existing or New) at any time.
3 - Registered Members may receive Flavor Icons by way of the Store Page, not to exceed 1 at any time.Revisions:
Pinned United Operations Charter
1.0 Mission Statement:
United Operations is a community dedicated to the active promotion of teamwork, cooperation and simulation in gaming. As a community we use the following to serve as our direction and function.
1.1 - Maturity, Friendship, Professionalism, Respect, Cooperation, Teamwork and Courtesy are the core virtues in our community.
1.2 - No Member of the community shall be granted privileges, powers, protections, exemptions or otherwise receive special treatments which exceed those held or are available in common.
1.3 - All Regulars have a common influence on the direction and administration of the community.
1.4 - Tactical and Simulation gaming, and the application of these concepts is the intent of this community.
1.5 - We are a free and open community - Monetized participation is not required. Those whom donate do so of their own choosing.
1.6 - Freedom of speech - No Member will be penalized for expressing their opinions so long as done in a Mature, Professional, and Respectful manner.
1.7 - Regulars being the core of the community embody and support by way of discussion, and promotion of the Charter and the SOPs of the community.
1.8 - No Member shall willfully act or conspire to supplant the rule of the Charter nor SOPs of this community
Operations are the standard method of community involvement in the decision making process and can be enacted across all aspects of the community.
2.1 - Standard Operations - All Operations are considered a Standard Operation, unless otherwise modified.
2.1.1 - Regulars are granted one (1) vote in Operations, additional titles gain no additional voting allotment/value.
2.1.2 - Operations last for seven (7) days, and require a two-third (2/3) majority to pass.
2.1.3 - Operation are presented as an anonymous request, excluding Regular/Officer Proposals.
2.1.4 - Votes shall be counted in an Automated/Anonymous method.
2.1.5 - Failed Operations may not be resubmitted until two (2) weeks from it's scheduled conclusion.
2.2 - Personnel Removal Operation
2.2.1 - Personnel Removal Operations are Standard Operations that last for two (2) weeks and require a two-third (2/3) majority.
Operations to add or amended rules must pass with a three-fourths (3/4) majority vote lasting two (2) weeks. We submit to the following rules in order to benefit the community at large:
3.1 - Cheating and hacking shall result in immediate and permanent removal from our community.
3.2 - The chain of command shall be respected during games.
3.3 - Players shall not intentionally team kill or otherwise disrupt game play.
3.4 - Player shall not engage in Forum/TeamSpeak spamming or otherwise disruptive behavior.
3.5 - Players shall respect each other and act accordingly.
3.6 - The rules of this community, the provisions so outlined in this document and the Standard Operating Procedures shall inform player conduct expectations.
3.7 - The rules of this community shall be applied equally across all mediums and services including, the Forums, TeamSpeak, and Game Servers.
3.8 - All operations of government must be publicly displayed. Any Regular may request and shall be entitled to any and all information regarding administrative operations.
3.9 - Sobriety will be required by individuals in leadership positions: both within the game and within the community’s offices.
4.1 - Non-regulars
4.1.1 - Non-regulars have no representation in operations of government, although they are free to express their opinions and are a valued part of the community.
4.1.2 - Non-regulars are gifted with but not guaranteed due process, protection of the Charter or Standard Operating Procedures. Non-regulars are guests who may be removed by the summary justice of other Regulars and overseeing Officers of respective areas if there are blatant violations of the Charter rules, Standard Operating Procedures or other clearly demonstrable reason. Blatant offenders may be summarily banned or otherwise disciplined without guaranteed instrument of redress. Summary instances of justice may be contested and overturned by a standard operation. These operations function as defined in section 2.0 of the charter.
4.1.3 - Non-regulars are guaranteed no privileges or rights which are awarded to Regulars, either in the Charter or in Standard Operating Procedures. Where privileges or rights are afforded, they are at the discretion of the Regular or official authority.
4.2 - Regulars
4.2.1 - Regulars represent the core of the community. Regulars are players who wish to take part in the organization and administration of the community:
188.8.131.52 - New Regulars are inducted by a Standard Operation.
184.108.40.206 - Rejected inductees will be notified and be given a reason for their rejection based on community consensus.
4.2.2 - There are two (2) methods to initiate a vote for Regular status
220.127.116.11 - Self Selection: Any registered forum user may ask to be inducted as a Regular.
18.104.22.168 - Appointment: Any Regular can appoint a player to be voted on as a Regular.
4.2.3 - All applicants must be registered and active members of the Forums for a minimum of forty-five (45) days prior to application.
4.2.4 - All applicants are expected to participate reasonable in Teamspeak activities prior to application.
4.2.5 - Regular Removals are inducted by a Personnel Removal Operation"
4.2.6 - Any Regular may resign their position as a Regular by post in the UO Forum.
4.2.7 - Regulars who have not logged into their forum account within ninety (90) days will be removed as Regulars.
4.3 - Officers
4.3.1 - Officers are expert volunteers oriented to perform a defined task within a category of expertise:
4.3.2 - Regulars may volunteer to become Officers.
4.3.3 - Operations for the induction of new Officers must be decided by a majority vote lasting two (2) weeks.
4.3.4 - Officer Removals are inducted by a Personnel Removal Operation
4.3.5 - Officers may not have any privileges or powers exceeding their tasks.
4.3.6 - Categories of expertise are as follows:
22.214.171.124 - Officer of Web Services: These Officers are tasked with ensuring the forums and website are operational.
126.96.36.199 - Officer of the Game Server: These Officers are tasked with ensuring the healthy operation of the game servers, including remote access and administration, as well as maintenance and expansion scouting.These Officers are tasked with ensuring that players have an effective and simple means by which to update their games and play here at United Operations.
188.8.131.52 - Officer of Mission Making: These Officers are tasked with managing the missions currently on the game and test servers, verifying problem missions and removing them through a transparent process, and educating the community on the addition of new missions to the servers.
184.108.40.206 - Officer of Public Relations: These Officers are tasked with monitoring, improving and developing inter-community relationships, promoting and expanding the community base, and for promoting events.
220.127.116.11 - Officer of the Training Center: These Officers are tasked with the implementation of official training courses within the community, the development of courses that coincide with the standard of play at UO, raising the overall standard of play, producing training plans, and the hiring/dismissal of instructors within the department.
4.3.7 - All elected Officers shall be granted the powers to administer the TeamSpeak server.
4.3.8 - Officers may delegate their pre-existing duties and powers, as defined by the Charter, to other Regulars. Each office must maintain a clearly worded definition of delegated powers and a complete list of those who are tasked with them. Definitions and lists must be publicly viewable on the Forum. Delegates may be voted out of their positions by a general operation (simple majority poll with one (1) week duration). Delegates voted out of a position cannot be granted delegated powers again under that office unless voted upon by the community of Regulars.
4.3.9 - Any Officer may resign their position as an Officer by post in the UO Forum.
5.0 Standard Operating Procedures:
The Standard Operating Procedures (SOPs)serve as a guide for the conduct of operations within each category of expertise delineated under the Officer section of this document. The SOPs may contain relevant procedures, expectations, and documentation. The following apply to community action and interaction with the SOPs:
5.1 - It is the primary responsibility of the Officer(s) overseeing each area of expertise to maintain and update the SOPs of their particular section as needed or required.
5.2 - Operations to add, remove or amend line-item SOPs are considered standard operations and are treated as such.
6.0 Revision and forum discussion information:
The following SOPs will govern the planning, coordination and hosting of events at United Operations. The Public Relations Office will be the central oversight and administration office for all events hosted at United Operations. The PRO will ensure members utilize a standard formats for event planning and ensure the highest quality is giving to players on event day.
1 Event Nomination/Proposal
1.1 All Proposed events need Regular Nomination with GM/Officer Support.
1.2 The Regular Nominator is responsible for the planning and Organization of an event.
1.2.a Non Regulars whom have Regular Nominator support may assist in event Planning and Organization.
1.2.b The Regular Nominator is responsible for all coordination between GM's and PRO
1.3 GM/Officer Support personnel must be established before the event, minimum 2.
1.3.a GM/Officers in a support role must give notice if unable to attend within 72 Hours before the Event.
1.3.b Replacement GM/Officers need to have at least 72 Hours notice for emergency replacement.
2 Custom Content
2.1 Any Event with new or custom content not existing at time of nomination will be scheduled no sooner than 2 months in advance.
2.2 Custom Content is considered to be scripts/addons/landmass/units.
2.3 Any Event with Custom Content needs to be prepared and in a working/tested state no later than 1 Month after proposal.
2.4 Custom Missions designed for events with nor prior working/tested version, are considered Custom Content.
3 Event Request Process
3.1 Events must be requested as per Event Request Form and submitted within the PRO Requests Subforum.
3.2 Events will be approved or denied within their own respective threads.
3.2.a Events that are Denied may will include reasoning in these threads.
3.2.b Events submitted will be decided on within one week of posting.
3.3 Events Proposed by PRO's do not need a request thread, but will be tracked internally with same requirements.
4 Event Schedule/RollCall
4.1 Event times will include two parts. Roll Call and Start Time
4.2 Roll Call time is expected to take between 30 minutes and 1 Hour.
4.3 Start Time is when the event is to begin, at it's latest point.
4.4 Members/Regulars whom are not in attendance in the RollCall Time are considered absent.
5 Event Slotting
5.1 Event Slotting will be managed by Host/GM and PRO as defined by the Event Roster.
5.2 Event Roster will be made public at the time of the event for organization.
5.3 Event Day corrections to an Event Roster will be decided by the Regular Host and PRO.
5.4 Signups for the Event Roster are managed by Event Request Form
6 Event oversight
6.1 PRO Office will have final oversight on planning and preparation of all events for quality control.
6.2 Any changes to mission intent/proposed intent will negate the event unless approved by PRO Office.
6.3 Any changes to Event Roster within 72 hours of the event will require PRO Office approval.
6.4 Any changes to modpack/addons/dependencies will require GSO/GM testing to be approved.
7 GM/Officer Event Oversight
7.1 Event Organizers will be required to secure a minimum of Two GM/Officers to be present for the full duration of any event.
7.2 Missions must be available and tested two weeks before the event is scheduled.
7.3 Event Missions will not be changed with out the approval of the MMO and PRO offices.
8 Event Cancellation
8.1 PRO office holds the right to cancel, move, change and restrict events from happening as they see fit.
8.2 Forced Cancellation may be declared for reasons defined above.
8.3 PRO Office may also cancel an event if they cite that an event is improperly planned/managed/tested.
8.4 PRO office reserves the right to deny Regular Sponsorship of events based these guidelines in past or current events.
9 Event Management Scope
9.1 All proposed events will be managed as per this document, with the following exclusions.
UOAF Events & Training
All banners, media and announcement posts must be ready to go at the time of the request, PRO will approve all event media and post as we see fit. PRO will help regulars promote approved events across all mediums, ie. Facebook, Twitter, Youtube and the forums.
Event Request Form:
Reg Sponsor (if non-reg submitter):
Sign-up Event? Y/N
Sign-up form: (post the sign-up form you intend to use for the event here. Sign-up form is subject to review.)
Mission(s) required for the Event: (The name or names of missions that will be played in the event, list ALL)
Is this mission complete? Y/N (by answering yes to this question you are signifying that the mission for the event is in the state that it will be in on event day)
Custom content? Y/N
If yes list custom content required here: (List of any custom mods required for this event and where to get them)
Event description: (the description that will be on the front page post for this event)
Banner: (The banner that will be displayed on the front page post for this event)[/indent]
I've noticed some slippage in the sig discipline. So this is a reminder as to the SoP's regarding Sig's that were enacted in the community.
As per community polls, these are the Sig picture rules and guidelines:
The intent of these rules and guidelines is to maintain an appropriate and non-disruptive means of expressing individuality in one's sig picture that enhances the UO community and encourages creative expression.
1. Forum Signature pictures shall have a maximum dimension of 500X150 pixels.
2. Forum Signature pictures shall have a maximum file size of 300KB.
3. Forum Signature pictures shall be in the following formats only:
JPG, BMP, PNG, GIF, and animated versions thereof.
4. Content must abide by Charter and SoP regulations.
1. Maintain vertical discipline, when integrating text into your signature. People browse the forums on a lot of devices, including phones, your spam of vertical text is not appreciated.
2. When posting in a thread, uncheck the signature option whenever possible. Your signature should not be present in a thread more than once.
3. Keep content relevant and appropriate to the community. Minors and ethnic tastes of all kinds use these forums, offensive content will be removed and warnings issued.
Signature Content Limits
Signature Image Size Limits Final Round
Signature Pixel Size Limits Final Round