Combat Operations Manual

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 FA Miles Prower
• 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 VA Silwar Naiilo, LC Taygetta, LC EvilGrin and CPT TI-40026

Both types of officers are expected to have completed the Combat Operations Exam (COE) before placement.

Queues & Platforms

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 were combat is against AI opponents

Match reports must meet the following minimum standards globally:

• Match reports must be for matches that resulted in victory
• Match reports must include all applicable TC pilots on the winning team
• Match reports must include accurate scoring information for each TC pilot on the winning team.
  • Qualifying pilots must have achieved at least 1 kill or objective.
  • If there has been no kills but an objective has been achieved, a 0 or 1 entry in kills is acceptable.
• Match reports must include a post-game scoreboard screenshot that displays player names and kills/scores.
  • Some platforms or custom matches will require an additional screenshot as indicated below.

The following platforms are supported for PvP and PvE queues:

• X-Wing vs TIE Fighter: Matches eligible for recognition must have a screenshot that displays the pre-game setup
• X-Wing Alliance: Matches eligible for recognition must have a screenshot that displays the pre-game setup
• Star Wars Battlefront (EA):
• Star Wars Battlefront II (EA):
• Star Wars Squadrons: 'Custom matches' must also have a screenshot that displays the pre-game setup and must have settings that are either standard or part of an accepted setup (i.e 3PO League).
• Star Conflict: