Combat Operations Manual Prototype MP02

She may not look like much, but she's got it where it counts This article is currently under construction. Work is underway to improve or create this article, updates may need to be shared via the articles discussion page. Once construction is complete please remove this template.

Combat Operations Manual

The Combat Operations Officer is in charge of all multiplayer activities throughout the TIE Corps and is responsible for organising multiplayer events both within the TIE Corps and with other outside organisations and clubs. The Combat Operations Officer's primary duties are coordination of multiplayer pilots, expanding multiplayer activities and approving multiplayer-oriented awards.

From the TIE Corps Command Staff page

Combat Operations Office

The Combat Operations Office is the organisation that overall handles multiplayer activities throughout the TIE Corps. Its officers consists of the following:

• Combat Operations Officer (COO): The Combat Operations Officer is the principal officer that is responsible for managing the Combat Operations Office, publishing reports about office activities and ensuring that assigned tasks from the EH Command Staff and TIE Corps Command Staff are completed.
  • The current Combat Operations Officer is RA Colo Delste
• Combat Operations Office Assistants (COOA): A Combat Operations Assistant primarily assists the COO in processing multiplayer matches that are present in the queue. They may also be assigned secondary projects and some may specialise as subject matter experts in particular platforms or operations.
  • Current Combat Operations Office Assistants are GN Elwood The Brave, COL Highlander, COL Miles Prower & FA Silwar Naiilo

Both types of officers are expected to have completed the COE/2 exam before placement.

Queues

The Combat Operations Office manages two queues which have several supported platforms:

• Player vs Player (PvP): Intended for supported platforms where combat is against other human players or a mixture of human opponents and AI
• Player vs Environment (PvE aka Co-Op): Intended for supported platforms where combat is against AI opponents

The Administration area where match reports can be generated

The PvP submission page

The PvE submission page

General Criteria

• Reporting is only for matches that result in victory
• Reports must have accurate pilot and score information for the winning side.
• Proof is given in the form of a legible post-game scoreboard screenshot that displays player names and score information
  • Specific platform type games may require a specific or additional screenshots
• For platforms that do not have specific requirements, qualifying pilots must have achieved 1 kill or objective
  • For winning matches that have no kills but an objective scored, a 0 or 1 entry is acceptable
• Match reports are for 1v1, 2v2, 3v3, 4v4, 5v5 or Free For All (FFA)
  • Free For All should only have the winner on the winning team
  • Information on the losing team should only be reported when the losing team contains at least one EH member
  • Kills for non-EH members do not need to be reported except where EH members competed against EH members on balanced teams and non-EH members participated.
• Matches must be submitted no later than 72 hours from completion

Platforms

Platform List

• Flight
  • X-Wing vs TIE Fighter
  • X-Wing Alliance
  • X-Wing Alliance Upgrade/TIE Fighter Total Conversion
  • Star War Squadrons
  • Star Conflict
• Shooters
  • Classic Star Wars Battlefront
  • Classic Star Wars Battlefront II
  • EA Star Wars Battlefront
  • EA Star Wars Battlefront II
  • Destiny 2
• Strategy
  • Star Wars Empire At War: Forces Of Corruption
• RPG
  • Star Wars: The Old Republic