COO:Combat Operations Manual

From Emperor's Hammer Encyclopaedia Imperia
Revision as of 02:16, 2 September 2024 by Coldsnacks (talk | contribs)
Hansolo-shemaynotlooklikemuch.png 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 From the Office of the Combat Operations Officer Last update: Coldsnacks (09/2/2024)
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 GN Elwood The Brave, COL Highlander, COL Miles Prower, LC Gytheran & 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:

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

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
    • Elite Dangerous
  • Shooters
    • Classic Star Wars Battlefront
    • Classic Star Wars Battlefront II
    • EA Star Wars Battlefront
    • EA Star Wars Battlefront II
    • Destiny 2
    • Star Wars: Hunters
  • Strategy
    • Star Wars Empire At War: Forces Of Corruption
  • RPG
    • Star Wars: The Old Republic

Flight

X-Wing vs TIE Fighter

Acceptable Match Configurations:

  • Free For All (PvP)
    • Must be alike craft
    • No beam weapons, countermeasures or warheads
    • Must be 5 minutes in length or longer
    • Must submit with a pre-game match setup screenshot
  • 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 5 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 5 minutes in length or longer
  • Missions/Campaigns (PvP)
    • Must be 5 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

Get The Game:

Connectivity Help:

  • 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 vs TIE Fighter Example Screenshots

X-Wing Alliance

Acceptable Match Configurations:

  • Free For All (PvP)
    • Must be alike craft
    • No beam weapons, warheads or countermeasures
    • Must be 5 minutes in length or longer
  • Team Battle (PvP)
    • Must be alike craft
    • No beam weapons, warheads or countermeasures
    • Must be 5 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 5 minutes in length or longer

Get The Game:

Connectivity Help:

  • 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.

X-Wing Alliance Example Screenshots

X-Wing Alliance Upgrade/TIE Fighter Total Conversion

Acceptable Match Configurations:

  • Free For All (PvP)
    • Must be alike craft
    • No beam weapons, warheads or countermeasures
    • Must be 5 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 5 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 5 minutes in length or longer
    • No beam weapons, warheads or countermeasures

Get The Mod:

XWAU and TFTC Example Screenshots

Squadrons

Acceptable Match Configurations:

  • 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 (which means kills should be set to max.)
  • 3PO League Rules (Custom PvP)
    • A minimum of 1 kill or 200 score must be achieved by qualifying pilots

Special Custom Match Rules:

  • 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).
  • Hull Health Adjustments (3PO League Configuration)
    • Applies to both sides (Imperial and New Republic)
    • Hull Health (Capital Ships, Cruisers, Frigates): 0.8
    • Hull Health (Corvette/Raider): 0.6

Get The Game:

SWS Example Screenshots

Star Conflict

Acceptable Match Configuration:

  • No custom matches
  • Any pilot listed in the submission must be part of the EH corporation in-game. Message a CMDR, COM, or COOA for help joining the Corporation.
  • Standard Game Modes (PvP)
    • Combat Recon where a pilot has played as the Captain and survived is considered to be an objective completion.
  • Standard Game Modes (PvE)
    • There must be two or more human players to count for PvE
    • Qualifying players in PvE must have attained a minimum of 3 kills and/or objectives or more
    • Combat Recon where a pilot has played as the Captain and survived is considered to be an objective completion.

Get The Game:

Star Conflict Example Screenshots

Elite Dangerous

Acceptable Configurations:

  • PvE Modes
    • Bounty Hunting
      • Two screenshots: one for team confirmation (Wingman symbols above Hud), and one of the Administration Contact page showing amount at 150k credits or more
    • Combat Bonds and Thargoid Activity
      • Two screenshots: one for team confirmation (Wingman symbols above Hud), and one of the Combat Bonds page
    • Missions
      • Two screenshots: one for team confirmation (Wingman symbols above Hud), and one of the mission completion screen
      • Donation and courier missions are not acceptable to submit for Legions of Skirmish.
  • PvP Modes
    • FFA Deathmatch and Team Deathmatch
      • Players must submit the scoreboard screen showing a win and at least one kill or at least 200 points.
    • Capture The Flag
      • Players must submit the scoreboard screen showing a win and at least one kill, objective, or at least 200 points.

Get The Game:

Elite:Dangerous Example Screenshots

Shooters

Classic Battlefront/Battlefront II

Acceptable Configurations:

  • PvP Modes
    • Players must submit the scoreboard screen showing a win and at least one kill or objective point.
    • Their team must have won, shown by their team having more points at the top of the screen.
    • If a custom match is played, you must also include a screenshot of modified settings. The "Game Info" section from the server selector is sufficient.

Get The Game:

Classic Battlefront Example Screenshots

EA Battlefront

Acceptable Configurations:

  • 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.

Get The Game:

EA Battlefront Example Screenshots

EA Battlefront II

Acceptable Configurations:

  • Standard Multiplayer Game Modes (PvP - Ground or Space)
    • 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.
    • Reports must show the Scoreboard displaying all players and the reporters must be on the side marked 'Victory'
  • Standard Co-Op Game Modes (PvE - Ground or Space)
    • There must be at least two human players or more to count as PvE.
    • In matches where 2 or more EH pilots participated in the same game, 1 person is to report the match by submitting a screenshot of the "victory pose" screen, as well as their own 'Personal' tab. The submitter should accurately record their eliminations in the "Kills" field, and report 0 for all other players.

Get The Game:

EA Battlefront 2 Example Screenshots

Destiny 2

Acceptable Configurations:

  • PvE Modes
    • Players must submit the "Match Results" screen showing at least one other human player, with credit for at least one kill.
  • PvP Modes
    • Players must submit the "Match Results" screen showing at least one kill or objective point. They must be on the winning team, or a winning player in a free-for-all.
    • Custom matches must use the default settings.

Get The Game:

Destiny 2 Example Screenshots

Star Wars: Hunters

Acceptable Configurations:

  • PvP Mode
    • Players must submit the scoreboard showing a score of at least 150 points
    • They must be on the winning team
    • Kills are to be accurately recorded in the submission

Get The Game:

Star Wars: Hunters Example Screenshots

Helldivers 2

Acceptable Configurations:

  • PvE Mode
    • Only games where the Primary mission objective was completed are eligible for submission
    • Players are to submit the screen that shows "Mission Completed" with the XP and Requisition Totals
    • The submitter is to enter the amount of XP earned in the "Kills" box. Other team members can be marked with a 0, or the XP amount earned.


Get The Game:



Role Playing Games (RPGs)

Acceptable Configurations:

Star Wars: The Old Republic

  • Flashpoints / Uprisings
    • Two screenshots must be taken: one during 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.

Get The Game:

Star Wars: The Old Republic Example Screenshots

Strategy

Star Wars Empire At War: Forces Of Corruption

Acceptable Configurations:

  • No vanilla Empire At War matches (blue styled UI)
    • Forces of Corruption UI is yellow for scorecard and match setup.
  • The Thrawn's Revenge mod may be used. This has a black UI instead of the standard yellow.
  • 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)
  • 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.
  • The setup screen must be submitted by a non-host as the "advanced options" window blocks the AI list.

Get The Game:

  • No Crossplay between Steam and GOG versions
  • Steam
  • GOG

Connectivity Help:

  • Steam version has a built in match browser
  • Windows Firewall exception will be needed to permit EAW/FOC to communicate.

Empire at War: Forces of Corruption Example Screenshots

COO/COOA Processing

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.

COOMAN-Example-QueueReport.png

An example of a match report that qualifies for recognition

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.

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.

Retrieved from "https://wiki.emperorshammer.org/wiki/index.php?title=COO:Combat_Operations_Manual&oldid=101372"