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

The PvP submission page

The PvE submission page

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.
• Match reports may be for 1v1, 2v2, 3v3, 4v4, 5v5 or FFA
  • FFA match reports should only have the winner on the winning team, losers on the losing team
• Information for the losing team should only be reported when the losing team contained at least one EH member.
  • Kills for non-EH members do not need to reported, except where EH members competed against other EH members on balanced teams (2v2/3v3/4v4/5v5) and non-EH members also participated.
• Match reports that may not fit in the submission form or need special attention should be e-mailed to the COO.

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
  • A minimum of 1 kill or 200 score must be achieved by qualifying pilots
  • 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
  • Combat Recon where a pilot has played as the Captain and survived is considered to be an objective completion.

A Star Wars Squadrons PvP match flown by FA Miles Prower, eligible for PvP recognition

FA Miles Prower's example match in the PvP submission form, properly formatted

Queue processing is performed by the COO or a COOA.

• The exception is that if the COO or a COOA is in the match report, another member of the office must process the match (i.e if Miles Prower (COO) and Silwar Naiilo (COOA) were reported in the match, the match report would not be visible to them, but could be processed by another COOA such as EvilGrin or Taygetta)

Queue processing is accessible to the COO or a COOA by accessing the Combat Operations Office Administration pages from the Administration section on the TIE Corps website after successful PIN and password authentication. Upon selection of the queue intended for processing, they will be presented with each match report.

The match report will consist of:

• Combat Event ID (if applicable/reported)
• Submitting pilot's name and rank
• Game platform
• Submission date
• Winning team members reported by submitter
• Losing team members reported by submitter
• Kill numbers reported by submitter and calculated team totals
• Each winning pilot with fields for kills, assists, objectives and efficiency (a Star Conflict item)

If the match report meets the standards (both global and platform-based) that indicate the match qualifies for recognition, the processor selects the 'Approve' bubble and proceeds in the queue.

If the match report does not meet the standard for recognition, the processor selects the 'Deny' bubble and either selects an appropriate automatic response from the dropdown menu (i.e Duplicate found by the automatic duplicate detection system) or enters the reason for denial into the 'Reason for denying' text box.

If the match report requires further clarification to make a decision, the processor selects the 'Skip' bubble (which is set by default for all reports).

An example of a match report that qualifies for recognition