Table of Contents

Integrations and ecosystem

ACTk plays well with popular Unity tooling. Use the integrations below to extend anti-cheat coverage without rewriting your own editor and runtime utilities.

Conditional symbols

Some add-ons expect the ACTK_IS_HERE compilation symbol. Enable it in the Conditional Compilation Symbols section of the settings window when you integrate third-party packages that look for ACTk.

Visual scripting

PlayMaker

ACTk ships a Integration/PlayMaker.unitypackage archive with custom actions:

  • Access ObscuredPrefs and ObscuredFilePrefs without writing code.
  • Control detectors (except the Obscured Cheating Detector) directly from state machines.
  • Example flows live under Scripts/PlayMaker/Examples.
Note

PlayMaker does not allow custom variable types, so obscured primitives require manual integration. Refer to the community guide or download the integration example if you need them.

Get PlayMaker from the Asset Store.

Behavior Designer

Import Integration/BehaviorDesigner.unitypackage to unlock:

  • Shared variables and tasks for Obscured types.
  • Detector actions and conditions that slot into behaviour trees.
  • Examples under Scripts/BehaviorDesigner/Examples demonstrate common patterns.

Get Behavior Designer from the Asset Store.

DOTS & hybrid projects

  • Sample scenes live under CodeStage/AntiCheatToolkit/Examples/DOTS ECS Examples with a dedicated UI module (Scripts/UI).
  • Systems such as PlayerBootstrapSystem, CheatResponseSystem, and AntiCheatHost show how to bridge ACTk with Entities.
  • Authoring components expose Obscured data in the inspector while DOTS systems manipulate encrypted values safely.

Combine the DOTS sample with the Obscured types chapter for a production-ready starting point.

Additional plugins

These community solutions complement ACTk in production:

Share your integration to have it featured in future updates.