Skip to main content

​
General Questions

ACHCE Client is an anti-cheat system specifically designed for Halo Combat Evolved. It prevents cheating through multiple protection layers:
  • TopMost window protection - Blocks external cheat injection tools
  • Temporary folder system - Prevents unauthorized game modifications
  • Hardware-based identification - Tracks players using unique device identifiers
  • Firebase integration - Real-time player tracking and ban management
The system is designed to ensure fair gameplay while being transparent about its protection mechanisms.
ACHCE Client is designed for Windows systems running:
  • Windows 7 or later (Windows 10/11 recommended)
  • .NET Framework 4.7.2 or higher
  • Halo Combat Evolved (PC version)
The client is built specifically for Windows and requires .NET Framework. It does not support Mac, Linux, or console versions of Halo.
Installation is straightforward:
  1. Download the ACHCE Client executable
  2. Ensure .NET Framework 4.7.2+ is installed
  3. Configure Firebase credentials (for server administrators)
  4. Launch ACHCE Client before starting Halo
For detailed instructions, see the Installation Guide.
No registration required. ACHCE Client automatically identifies players using unique hardware identifiers (such as BIOS UUID). This means:
  • No username/password needed
  • No manual registration process
  • Automatic identification on first launch
  • Hardware-based tracking prevents ban evasion
Your identity is tied to your hardware, making it more secure than IP-based or account-based systems.

​
How It Works

TopMost protection keeps the ACHCE Client window always on top of other windows, covering the screen during gameplay.Purpose:
  • Prevents opening cheat injection tools
  • Blocks external programs that modify game memory
  • Makes it difficult to use external cheating software
How it works:
  • Form2 creates a full-screen overlay that matches your monitor resolution
  • The window stays on top of all other applications
  • This blocks access to injection tools like trainer programs
TopMost protection doesn’t interfere with normal gameplay - it only blocks external tools from being opened while the anti-cheat is active.
ACHCE Client creates temporary folders to prevent players from using modified game files.The problem:
  • Players could use extensions like HAC2 Release or Chimera
  • Modified game files could bypass anti-cheat measures
  • Permanent modifications persist between sessions
The solution:
  • Game files are loaded into a temporary, controlled environment
  • Files are verified before use
  • Temporary folder is deleted when you close the game
  • Next session uses fresh, verified files
This ensures every gaming session starts with clean, unmodified game files.
ACHCE Client identifies players using unique hardware identifiers rather than easily-spoofed information like IP addresses.What is used:
  • BIOS UUID (unique to your motherboard)
  • Other hardware identifiers specific to your device
  • This creates a unique “fingerprint” for each player
Why not use IP addresses?
  • IP addresses can be changed easily using VPNs
  • Multiple players may share the same IP (home networks)
  • Dynamic IPs change frequently
  • Hardware IDs are much more difficult to spoof
Hardware identification means that bans are tied to your physical device. Changing your IP address or using a VPN will not bypass a ban.
ACHCE Client uses Firebase Realtime Database for player tracking:Data stored:
  • Player IP address (for logging purposes)
  • Unique hardware identifier
  • Session information
  • Ban status (if applicable)
How it works:
  • When you connect, your information is added to Firebase
  • The system uses a randomly generated name as the database key
  • When you disconnect, your session data is automatically deleted
  • Ban records persist to prevent future access
Privacy:
  • Only essential data for anti-cheat functionality is collected
  • Session data is temporary and removed when you exit
  • No personal information beyond IP and hardware ID is stored
See Form1.cs:58-69 for implementation details.

​
Bans and Enforcement

The ban system uses hardware-based identification to prevent cheaters from returning:Detection:
  • Server administrators monitor for suspicious activity
  • Cheating behavior is logged and reviewed
  • Confirmed cheaters are added to the ban database
Enforcement:
  • Bans are tied to hardware identifiers, not IP addresses
  • Banned players cannot connect even with VPN or IP changes
  • Ban records are stored in Firebase Realtime Database
  • Checks happen automatically when connecting
Duration:
  • Temporary bans have a specified duration
  • Permanent bans require administrator review to lift
  • Ban appeals should be directed to server administrators
Yes, but the process is managed by server administrators, not the ACHCE Client software itself.Steps to appeal:
  1. Contact the server administrator or community moderators
  2. Provide your hardware identifier (if requested)
  3. Explain your situation clearly and honestly
  4. Wait for administrator review
False positives are rare but possible. If you believe you were banned in error, reach out to server administrators with a detailed explanation.
Common bannable offenses include:
  • Using cheat software - Aimbots, wallhacks, ESP, etc.
  • Game file modification - Altered game files for unfair advantage
  • Injection tools - Memory manipulation or code injection
  • Exploiting bugs - Intentionally abusing game vulnerabilities
  • Ban evasion attempts - Trying to bypass existing bans
Not bannable:
  • Playing well or having high skill
  • Using legitimate game settings
  • Having a good internet connection
  • Reporting bugs or issues
Attempting to bypass or disable ACHCE Client while playing on protected servers will result in an immediate ban.
No. This is a key feature of ACHCE Client’s design:Why VPNs don’t work:
  • Bans are tied to hardware identifiers, not IP addresses
  • Changing your IP doesn’t change your hardware fingerprint
  • The system was specifically designed to prevent VPN-based ban evasion
Why reinstalling Windows doesn’t work:
  • Hardware identifiers persist across OS reinstalls
  • BIOS UUID and device identifiers remain the same
  • Only changing physical hardware components may affect your fingerprint
Hardware changes:
  • Replacing your motherboard may change your hardware ID
  • This is expensive and not a practical ban evasion method
  • Administrators can still identify patterns of behavior
The only legitimate way to resolve a ban is through the appeal process with server administrators.

​
Technical Questions

Yes, ACHCE Client’s source code is available for review. This transparency allows:
  • Community audit of anti-cheat methods
  • Server administrators to understand how protection works
  • Developers to contribute improvements
  • Users to verify no malicious code is present
You can review the source code and understand exactly what the client does.
Minimal impact. ACHCE Client is designed to be lightweight:
  • Runs in the background with minimal CPU usage
  • No game file scanning during gameplay
  • Firebase connections are async and non-blocking
  • TopMost window overlay has negligible performance cost
Most players experience no noticeable performance difference. If you do experience issues, see the Troubleshooting Guide.
Yes, ACHCE Client requires an active internet connection for:
  • Connecting to Firebase Realtime Database
  • Retrieving player ban status
  • Logging session information
  • Detecting public IP address
What happens without internet?
  • Client will display “there was problem in the internet” error (Form1.cs:41)
  • Cannot verify ban status
  • Cannot connect to protected servers
A stable internet connection is required for both the anti-cheat verification and online gameplay.
Yes. ACHCE Client follows security best practices:Data protection:
  • Firebase connections use HTTPS encryption
  • AuthSecret credentials protect database access
  • Only essential data is collected
  • Session data is automatically deleted on exit
Privacy considerations:
  • IP addresses are logged but not shared publicly
  • Hardware identifiers are hashed and not reversible
  • No personal information (name, email, etc.) is collected
  • Data is only used for anti-cheat purposes
Server administrator responsibility:
  • Admins must protect Firebase credentials
  • Database access should be restricted
  • Follow security guidelines in Firebase Setup
ACHCE Client uses the following NuGet packages:
  • FireSharp 2.0.4 - Firebase Realtime Database client
  • Newtonsoft.Json 6.0.4 - JSON serialization
  • Microsoft.Bcl.Async 1.0.168 - Async programming support
  • Microsoft.Net.Http 2.2.28 - HTTP client functionality
These are automatically installed when building from source. Pre-built executables include all dependencies.For more information, see packages.config in the source code.
ACHCE Client requires .NET Framework 4.7.2 or higher.Installation:
  1. Check if you have it: Windows Settings > Apps > .NET Framework
  2. If missing, download from Microsoft’s site
  3. Install and restart your computer
Why this version?
  • Provides modern async/await support
  • Better security features
  • Improved performance
  • Wide compatibility with Windows 10/11
.NET Framework 4.7.2 is included by default in Windows 10 version 1803 and later.

​
Server Administration

Server administrators need to:
  1. Create a Firebase project
    • Set up Firebase Realtime Database
    • Configure authentication and security rules
    • Get AuthSecret and BasePath
  2. Configure ACHCE Client
    • Update Form1.cs with Firebase credentials
    • Build the client executable
    • Distribute to players
  3. Manage the ban database
    • Monitor Firebase for player sessions
    • Add banned players to the database
    • Remove bans when appealed and approved
For detailed setup instructions, see the Firebase Setup Guide.
Yes, as an open-source project, you can customize:
  • UI appearance and branding
  • Loading messages and text
  • Additional anti-cheat checks
  • Integration with your existing systems
Recommended customizations:
  • Add your server/community name to the UI
  • Customize colors to match your branding
  • Add links to your community Discord or website
Not recommended:
  • Removing core anti-cheat functionality
  • Weakening protection mechanisms
  • Sharing Firebase credentials in the code
Make sure to test thoroughly after any modifications.
Server administrators can monitor activity through Firebase:Real-time monitoring:
  • View active players in PlayerIpList/ path
  • See connection times and IP addresses
  • Track player sessions
Historical data:
  • Ban records persist in the database
  • Session logs can be exported
  • Analyze patterns of suspicious behavior
Tools:
  • Firebase Console provides a web interface
  • Firebase SDK allows programmatic access
  • Export data for external analysis
Set up Firebase alerts to notify you of specific events, such as banned players attempting to connect.
Regular updates are important for maintaining effective anti-cheat protection:Update frequency:
  • Check for updates monthly at minimum
  • Update immediately when new cheats are discovered
  • Follow community discussions about new threats
What to update:
  • Core ACHCE Client code
  • Firebase security rules
  • Ban database entries
  • Documentation for players
The anti-cheat system should evolve with the community’s needs and emerging threats. Stay engaged with the development community to stay informed about updates.

​
Still Have Questions?

Troubleshooting

Find solutions to common technical issues

Configuration Guide

Learn how to configure Firebase and client settings

Core Concepts

Understand how ACHCE Client works in depth

Installation

Step-by-step installation instructions
If your question isn’t answered here, check the GitHub repository or reach out to the community for support.

Build docs developers (and LLMs) love

Get started for freeTalk to us