Welcome to the UO Wiki

Donating members and regulars will be automatically logged in; if you are not logged in please log-in here and refresh the page.
In the event logging in does not resolve the problem please contact Verox to report the bug.

United Operations Standard Operating Procedures

From UO Community Wiki
Jump to: navigation, search

The Standard Operating Procedures are the rules and guidelines for using official services provided by United Operations. Breaches of the Standard Operating Procedures can result in punishments ranging from verbal warnings to total, permanent, bans from the community. It is a requirement for all members of the United Operations community to read and understand these rules before using any service provided by United Operations; ignorance of the Standard Operating Procedures is not a valid defence in the event of a breach.

You can find links to specific services' SOPs at the end of this article.

Community SOPs

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:

Impersonation

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;
Users will warned and if not corrected then banned from services for a period of no less than 1 day.
Any user caught doing the above during any event shall be banned from all services for a period of no less than 2 Days.

TeamSpeak

General Rules

1 - Officers are granted powers to create, delete, and edit bans.
2 - Officers are granted powers to create, delete, and edit channels.
3 - Regulars are granted powers to ban, kick, and move disruptive community members for up to 2 hours.
4 - Community Members are required to match their Teamspeak Name to their Forum Account Name or Ingame Name.
5 - Community Members may include additional text after their name to indicate game status or requests. (ex. LFG/Waiting/Streaming)
6 - Community Members are restricted from recording outside of Game Channels.
7 - Community Members are restricted from distributing copyrighted works via Teamspeak.

Game Channels

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.

Office Channels

1 - Officers are required to maintain a Teamspeak Office Channel.
2 - Officers may create Delegate Channels within their Office Channel.

Personal Channels

1 - Community Members may purchase one Personal Channel via Store Page.
2 - Channel Owners may have one Private (Passworded) Subchannel within their Purchased Channel.
3 - Personal Channels are subject to all Community Rules, in addition to Channel Owner Defined Rules.
4 - Personal Channels are required to include any addition Channel Rules, plainly, at the start Description field.
5 - Personal Channels are required to include the Channel Owner's name in the Description or Topic for identification.

Flavor Icons

1 - Flavor Icons are any Server Group, or TeamSpeak Icon used for expression, interest, group affiliation and or military affiliation.
2 - Community Members may have up to one Flavor Icon at any time.
3 - Community Members may purchase existing Flavor Icons via the Store Page, or Submit their own for Purchase by others.
4 - Regulars may have Flavor Icon (New or Existing) granted to them at any time.
5 - Server Groups for Offices, Delegates, or Membership Status do not account against a Community Member's Flavor Icon Limit

Service SOPs