COO:Combat Operations Manual

From Emperor's Hammer Encyclopaedia Imperia
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.
  • 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 LC Highlander, MAJ LegionX, CPT Colo Delste, CPT TheBlackxRanger and CPT TI-40026

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

Queues & Platforms

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

COOMAN-Example-Admin.png

The Administration area where match reports can be generated

COOMAN-ExamplePvPSub.png

The PvP submission page

COOMAN-ExamplePvESub.png

The PvE submission page

Match Reports

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.
  • Match reports are restricted to report from 1 account/identity per platform. Any suspected to be dual-hating/smurfing on a platform are subject to inquiry where such will be confirmed by the COO or a COOA. Suspect submissions are to be placed on hold. After a warning, the pilot is expected to choose one account. If such is encountered again and is confirmed to be done on the same platform, the pilot’s submissions will be denied entirely for one queue cycle. Further incidents will be raised to the necessary disciplinary processes.
    • For tracking purposes: EA App (PC), Origin (PC/macOS),Steam (PC/macOS), Microsoft PC Game Pass (PC), XBOX, PlayStation Network are considered separate platforms apiece.
  • 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.
  • Matches must be submitted no later than 72 hours from their completion. Anything past this will be denied.

Platforms

The following platforms are supported for PvP and PvE queues:

  • X-Wing vs TIE Fighter
  • X-Wing Alliance
    • X-Wing Alliance Upgrade/TIE Fighter Total Conversion
  • Star Wars Battlefront (EA)
  • Star Wars Battlefront II (EA)
  • Star Wars Squadrons
  • Star Conflict
  • Empire at War Forces Of Corruption
  • Star Wars: The Old Republic


COOMAN-PvP-Example-Scoreboard.png

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

COOMAN-PvP-Example-Report.png

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

Queue Processing

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 Combat Operations within Staff Operations on the Management section of Member Account on the TIE Corps website after successful PIN and password authentication.

COOMAN-Example-CombatOps.png

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.

  • Duplicates are generally automatically flagged by the detection system. However false-negatives and false-positives may present so please scrutinise all duplication reports to ensure they are being flagged properly. Anomalies with the detection system should be reported to the Internet Officer.

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). Skipping a match report and requesting help from other COOAs and/or the COO is always considered appropriate if a report looks unclear.

COOMAN-Example-QueueReport.png

An example of a match report that qualifies for recognition

COOMAN-ExampleDupe.png

An example of a match report that is denied for being a duplicate

COOMAN-Example-DenialDupeMail.png The resulting email from the database alerting the reporter that their submission was denied (Naughty naughty, Miles!)

Combat Events

Combat Events are multiplayer events tracked by the Combat Operations Office. They are added by the COO or a COOA from the Combat Operations Office Administration page.

Inter-club combat events will also be listed but may also be listed at the third-party BattleStats website. To be countered in an inter-club combat event that the EH is participating in, you must have a BattleStats account and be a member of the EH Club (Club ID: 486) in BattleStats.

Distinguished Flying Cross

Distinguished Flying Cross

Winning Combat Operations Office approved combat events makes a pilot eligible for the Distinguished Flying Cross.

Multiple DFCs can be awarded on a single combat event if more than one EH/TC member qualifies and they are all tied for 1st place (though likely a rare condition).

Overall though these conditions must be met by default

  • You must be the best EH ranking player in the combat event.
    • If there is a tie and the other requirements are met, DFCs can be awarded to all tiers.
  • You must beat a minimum of three different players on that combat event
  • You must have a win-loss ratio of at least +3 (ex. 3 wins/0 losses, 4 wins/1 loss, etc.)
  • Any exceptions to these rules must be agreed to by at least one member of the TIE Corps Command Staff or EH Command Staff.

Ratings & Awards

The Combat Operations Office also issues awards for attaining certain levels in the Rating system for PvP/Combat Ratings and PvE/Co-Op.

Upon meeting a certain rating, the pilot is recognised with the appropriate medal for that rating by the COO. These medals can be found in the TIE Corps Pilot Manual.

Connectivity

  • X-Wing vs TIE Fighter: GameRanger (third party application) or Direct IP
    • GameRanger may need UDP port 16000 forwarded in some configurations
    • Windows Firewall will need to permit XvT, Balance of Power (BoP) (if included) and the DirectPlay Server (dplaysvr.exe) to communicate (and GameRanger if used)
    • May require DirectPlay to be installed in Windows 7/8/10/11 ("Turn Windows features on or off" function > Legacy Components > DirectPlay)
    • Direct IP may require the following ports to be forwarded: TCP 2300-2400 + 47624, UDP 2300-2400 + 6073. Please note doing so is done at your own risk.
    • Paradoxically, works best with network settings having Internet off.
  • X-Wing Alliance: GameRanger (third party application) or Direct IP
    • GameRanger may need UDP port 16000 forwarded in some configurations
    • Windows Firewall will need to permit XWA and the DirectPlay Server (dplaysvr.exe) to communicate (and GameRanger if used)
    • May require DirectPlay to be installed in Windows 7/8/10/11 ("Turn Windows features on or off" function > Legacy Components > DirectPlay)
    • Direct IP may require the following ports to be forwarded: TCP 2300-2400 + 47624, UDP 2300-2400 + 6073. Please note doing so is done at your own risk.
    • Paradoxically, works best with network settings having Internet off.
  • Battlefront (EABF1): Built in matchmaking
    • Windows Firewall exception will need to permit EABF1 to communicate.
  • Battlefront II (EABF2): Built in matchmaking
    • Windows Firewall exception will need to permit EABF2 to communicate.
  • Squadrons:Built in matchmaking
    • Windows Firewall will exception need to permit Squadrons to communicate.
    • Crossplay is enabled by default (PC + XBOX + Playstation)
  • Star Conflict: Built in matchmaking
    • Windows Firewall exception will need to permit Star Conflict to communicate.
  • Empire At War/Forces Of Corruption (EAW/FOC): Built in match browser if on Steam. Connectivity to GOG players needs GameRanger (third party application).
    • Windows Firewall exception will be needed to permit EAW/FOC to communicate.

Acceptable Match Configurations

X-Wing vs TIE Fighter

  • Free For All (PvP)
    • Must be alike craft
    • No beam weapons, warheads or countermeasures
    • Must be 10 minutes in length or longer
    • Matches eligible for recognition must have a screenshot that displays the pre-game setup
  • Team Battle (PvP)
    • Must be alike craft
    • No beam weapons, warheads or countermeasures
    • Must be 10 minutes in length or longer
  • Team Battle (PvP)
    • AI craft must be of equal or better skill than humans
    • AI craft must have equal or better craft type than humans
    • No beam weapons, warheads or countermeasures
    • Must be 10 minutes in length or longer
  • Team Battle (PvE)
    • There must be two or more human players present on one team
    • AI craft must be of equal or better skill than humans
    • AI craft must have equal or better craft type than humans
    • No beam weapons, warheads or countermeasures
    • Must be 10 minutes in length or longer
  • Missions/Campaigns (PvP)
    • Must be 10 minutes in length or longer
    • Training missions are ineligible
  • Missions/Campaigns (PvE)
    • There must be two or more human players present on one team
    • Training missions are ineligible

X-Wing Alliance

  • Free For All (PvP)
    • Must be alike craft
    • No beam weapons, warheads or countermeasures
    • Must be 10 minutes in length or longer
  • Team Battle (PvP)
    • Must be alike craft
    • No beam weapons, warheads or countermeasures
    • Must be 10 minutes in length or longer
  • Team Battle (PvE)
    • There must be two or more humans present on one team
    • AI craft must be of equal or better skill than humans
    • AI craft must have equal or better craft type than humans
    • No beam weapons, warheads or countermeasures
    • Must be 10 minutes in length or longer

X-Wing Alliance Upgrade/TIE Fighter Total Conversion

  • Free For All (PvP)
    • Must be alike craft
    • No beam weapons, warheads or countermeasures
    • Must be 10 minutes in length or longer
  • Team Battle (PvP)
    • Must be alike craft
    • No beam weapons, warheads or countermeasures
    • AI craft must be of equal or better skill than humans
    • AI craft must have equal or better craft type than humans
    • No beam weapons, warheads or countermeasures
    • Must be 10 minutes in length or longer
  • Team Battle (PvE)
    • There must be at least two human players or more to count as PvE.
    • AI craft must be of equal or better skill than humans
    • AI craft must have equal or better craft type than humans
    • The point total of the opposing team should be at least equal to the player team and the opposing team needs to include at least one starfighter group.
    • Must be 10 minutes in length or longer
    • No beam weapons, warheads or countermeasures

EA Battlefront 1

  • Standard Multiplayer Game Modes (PvP - Ground or Space)
  • Standard Co-Op Game Modes (PvE - Ground or Space)
    • There must be at least two human players or more to count as PvE.

EA Battlefront 2

  • Standard Multiplayer Game Modes (PvP - Ground or Space)
  • Standard Co-Op Game Modes (PvE - Ground or Space)
    • There must be at least two human players or more to count as PvE.
    • For Ewok Hunt: For an Ewok victory, no Stormtroopers can survive and you must have an elimination as an Ewok for qualify for an LoC.

Squadrons

  • Standard Dogfight (PvP)
    • A minimum of 1 kill or 200 score must be achieved by qualifying pilots
  • Standard Ranked Fleet Battles (PvP)
    • A minimum of 1 kill or 200 score must be achieved by qualifying pilots
  • Standard Fleet Battles vs AI (PvE)
    • There must be at least two human players or more to count as PvE.
    • A minimum of 1 kill or 200 score must be achieved by qualifying pilots
  • Custom Matches
    • A minimum of 1 kill or 200 score must be achieved by qualifying pilots.
    • Must be 10 minutes in length or longer
  • 3PO League Rules (Custom PvP)
    • 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).
    • Applies to both sides (Imperial and New Republic)
    • Hull Health (Capital Ships, Cruisers, Frigates): 0.8
    • Hull Health (Corvette/Raider): 0.6
    • Must be 10 minutes in length or longer

Star Conflict

  • Standard Game Modes (PvP and PvE)
    • No custom matches
    • There must be two or more human players to count for PvE
    • Combat Recon where a pilot has played as the Captain and survived is considered to be an objective completion.

Empire At War:Forces Of Corruption

  • No vanilla Empire At War matches (blue styled UI)
  • Forces of Corruption UI is yellow for scorecard and match setup.
  • Space Battles or Ground Battles accepted
  • Any faction may be used
  • PvE requires two humans or more present for LoS. AI settings are as followed: Equivalent number of AI to players or more if playing at Medium AI. Equivalent-1 or more AI if playing at Hard. (i.e 3 human players may face 3+ Medium AI or 2+ Hard AI). As of 12 September 2022, any matches not meeting these standards will be declined.
  • Advanced Settings for PvE: No Heroes, No Superweapons, Starting Credits 2000
  • Advanced Settings for PvP: No Heroes, Superweapons are allowed, free starting units required for fog of war, starting credits 2000
  • Screenshots required: Setup showing how the game was set up and a screenshot of the results showing the clear winner(s)
  • Match time no shorter than 5 minutes.

Star Wars: The Old Republic

  • Flashpoints / Uprisings
    • Two screenshots must be taken: at the beginning of a flashpoint or operation, as well as at the end. The first screenshot must include the players in the flashpoint, the flashpoint being run, and the time that it is being completed. The second must include the pop-up reward window stating the completed mission, and include the group members from the first screenshot (either in the group or in chat) and the time.
  • Operations
    • Two screenshots must be taken: at the beginning of an operation, as well as at the end. The first screenshot must include the players in the operation, and the operation being run. The second must include the lockout after the final boss..
  • Warzones (any mode), Galactic Starfighter, and Arenas
    • A screenshot must be submitted showing that the match was a victory. The pilot must have at least one kill or objective point.


Where To Get The Games

X-Wing vs TIE Fighter

X-Wing Alliance

EA Battlefront 1 (No Crossplay)

EA Battlefront 2 (No Crossplay)

Squadrons (Crossplay)

Star Conflict

Star Wars: Empire At War (No Crossplay between GOG and Steam Versions)

Star Wars: The Old Republic