Anti-Cheat Integration Checklist

Before going live, ensure your product is running the anti-cheat interfaces correctly with this checklist.

3 mins to read

The Anti-Cheat Interfaces require using SDK 1.12 or higher. The Anti-Cheat Client interfaces supports Windows, Mac, and Linux platforms, and requires a 64-bit operating system installation.

You should use these checklists to verify the integration of the Anti-Cheat interfaces and your game works properly before release.

Service Installer (Windows)

1. Fully remove any existing Easy Anti-Cheat installation by running EasyAntiCheat_EOS_Setup.exe qa-factory-reset from a command prompt.

This ensures that your test system is in the same state as the system of a player who has never played any Easy Anti-Cheat protected game before. If you have other Easy Anti-Cheat protected games installed then they will need to be repaired or reinstalled after this operation.

Success criteria:

  • The command sc query EasyAntiCheat_EOS reports that the specified service does not exist as an installed service.
  • Registry keys do not exist at the following location: HKLM\Software\Wow6432Node\EasyAntiCheat_EOS\.

2. Install the game as a player would, using e.g. the Epic Games Store, Steam, etc.

Success criteria:

  • EasyAntiCheat_EOS_Setup executes with Administrator rights, and it closes with exit status 0.
  • The command sc query EasyAntiCheat_EOS reports that the service exists and is in a STOPPED state when the game is not running.

3. Uninstall the game

Success criteria:

  • EasyAntiCheat_EOS_Setup executes to uninstall the Easy Anti-Cheat Service.
  • The command sc query EasyAntiCheat_EOS reports that the specified service does not exist as an installed service.

Game Client & Anti-Cheat Bootstrapper

1. Go to your Developer Portal > Your Product > Game Services > Anti-Cheat > Configure. Select Enable All and click Save Changes.

Success criteria:

  • Client Protection and Server Kicks remain enabled after refreshing the Anti-Cheat page.

2. Start the game without the anti-cheat bootstrapper.

Success criteria:

  • Your game may function normally, or may display a warning/error message if you prefer.
  • However, the player should not be able to join protected multiplayer game sessions with other players. Anti-cheat authentication should fail and an appropriate message should display.

3. Start the game with the anti-cheat bootstrapper.

Success criteria:

  • Your game should function normally.
  • The player should be able to join protected multiplayer game sessions with other players successfully and remain connected for more than 10 minutes.
  • The player should be able to disconnect from one protected multiplayer game session and join a different one successfully.

4. Go to your Developer Portal > Your Product > Game Services > Anti-Cheat > Configure. Select Enable Client Protection Only and click Save Changes.

Success criteria:

  • Client Protection remains enabled after refreshing the Anti-Cheat page.

5. Start the game without the anti-cheat bootstrapper and pass the additional command line argument -EOS_FORCE_ANTICHEATCLIENTNULL to the game.

Success criteria:

  • Your game should function normally.
  • The player should be able to join protected multiplayer game sessions with other players successfully and remain connected for more than 10 minutes.
  • The player should be able to disconnect from one protected multiplayer game session and join a different one successfully.

6. Start the game with the anti-cheat bootstrapper.

Success criteria:

  • Your game should function normally.
  • The player should be able to join protected multiplayer game sessions with other players successfully and remain connected for more than 10 minutes.
  • The player should be able to disconnect from one protected multiplayer game session and join a different one successfully.

7. Go to your Developer Portal > Your Product > Game Services > Anti-Cheat > Configure. Select Disable All and click Save Changes.

Success criteria:

  • Client Protection and Server Kicks remain disabled after refreshing the Anti-Cheat page.

8. Start the game with the anti-cheat bootstrapper.

Success criteria:

  • Your game should function normally.
  • (For Windows) The command sc query EasyAntiCheat_EOS reports that the service is in state STOPPED while the game is running.
  • The player should be able to join protected multiplayer game sessions with other players successfully and remain connected for more than 10 minutes.
  • The player should be able to disconnect from one protected multiplayer game session and join a different one successfully.

9. Go to your Developer Portal > Your Product > Game Services > Anti-Cheat > Configure. Select Enable All, enable Force Enable Server Kicks, and click Save Changes.

Success criteria:

  • Client Protection and Server Kicks remain enabled after refreshing the Anti-Cheat page.