Welcome to ACTk

Thank you for choosing the Anti-Cheat Toolkit (ACTk) for Unity. This manual walks you through the toolkit's capabilities, recommended workflows, and practical tips that help you ship a resilient player experience.

Note

If you need scripting reference details, jump straight to the API documentation. This manual focuses on usage patterns, configuration, and decision-making guidance.

How to use this manual

The user manual is organized into modular topics so you can quickly jump to the material you need:

• Getting started – install the package, configure global settings, and review the quick-start checklist.
• Obscured data types – fight memory editors, serialize data safely, and understand DOTS Hybrid workflows.
• Secure storage – protect save files and preferences, manage device locking, and use the Prefs Editor effectively.
• Detectors – configure cheat detectors, tune thresholds, and react to cheating attempts in code or the editor.
• Code integrity & platform tooling – validate build integrity, harden your delivery pipeline, and leverage platform-specific helpers.
• Integrations & ecosystem – review official add-ons and third-party solutions that extend ACTk.
• Troubleshooting – diagnose common pitfalls and keep your project stable.
• Migration – update existing projects safely when upgrading from older ACTk releases.
• Compatibility – review supported platforms, export compliance, and build tool notes.
• Support & resources – stay in touch, get help, and keep your team informed.

Each topic includes best practice checklists and cross-links so you can design a protection strategy that fits your game.

Quick reference

• Homepage
• Community Discord
• Video tutorials
• Forum thread

Disclaimer

Anti-cheat solutions can never be 100% unbreakable—skilled and motivated attackers can eventually bypass any client-side protection. The goal of ACTk is to stop the majority of cheaters, raise the cost of an attack, and provide you with telemetry you can act on.

Anti-cheat tooling should be part of a layered security strategy. Combine ACTk with authoritative server logic, code obfuscation, and your own monitoring. Keep ACTk updated—new releases ship fixes for newly discovered attack vectors and compatibility changes.

When you plan feature work, prefer IL2CPP builds where possible and make a habit of testing with the sample scenes in the package. Hands-on testing is still the best way to validate your protection setup.

Acknowledgments

Huge thanks to Daniele Giardini (Demigiant) for the awesome ACTk logos, intensive help, and priceless feedback.