Skip to main content

​
Common Issues

This guide helps you resolve common problems when using ACHCE Client. If you encounter an issue not covered here, please contact support or check the FAQ.
This error occurs when the client cannot establish a connection to Firebase.Possible Causes:
  • No internet connection
  • Firebase credentials not configured
  • Firebase database is offline or unreachable
  • Firewall blocking outbound connections
Solutions:
  1. Check your internet connection 
    ping 8.8.8.8
    Ensure you have an active internet connection.
  2. Verify Firebase credentials
    • Open the configuration file and check that AuthSecret and BasePath are properly set
    • Ensure the Firebase credentials are valid and not expired
    • See the Firebase Setup guide for proper configuration
  3. Check Firebase database status
    • Log into your Firebase console
    • Verify that the Realtime Database is active
    • Check database rules allow connections from your IP
  4. Firewall configuration
    • Ensure your firewall allows connections to Firebase domains
    • Add exception rules for ACHCE Client executable
Empty or incorrect Firebase credentials in Form1.cs will always cause connection failures. Never leave AuthSecret or BasePath as empty strings in production.
The TopMost protection window may interfere with game launch in some configurations.Symptoms:
  • Game window doesn’t appear
  • Cannot click on game launcher
  • Screen covered by overlay
Solutions:
  1. Restart ACHCE Client
    • Close the application completely
    • Launch ACHCE Client with administrator privileges
    • Try launching the game again
  2. Check screen resolution settings
    • ACHCE Client adjusts to primary monitor resolution
    • If using multiple monitors, ensure primary monitor is correctly configured
    • The client uses Screen.PrimaryScreen.Bounds to detect resolution (Form2.cs:25)
  3. Verify Windows compatibility mode
    • Right-click ACHCE Client executable
    • Go to Properties > Compatibility
    • Disable compatibility mode if enabled
Issues with temporary folder management can prevent proper anti-cheat functionality.Symptoms:
  • Game files not found
  • Modified game files still loading
  • Error messages about missing files
Solutions:
  1. Check disk space
    • Ensure you have sufficient disk space for temporary files
    • At least 1GB of free space recommended
  2. Verify write permissions
    • Run ACHCE Client as administrator
    • Check that user has write permissions to the temporary folder location
  3. Antivirus interference
    • Some antivirus programs may block or delete temporary folders
    • Add ACHCE Client to your antivirus exclusion list
    • Add the temporary folder location to exclusions
Temporary folders are automatically cleaned up when the application closes (Form1.cs:100-104). If you’re testing, this is expected behavior.
Player information should automatically sync to Firebase when connecting.Symptoms:
  • No player entries in Firebase database
  • Player data not updating
  • Random name not generated
Solutions:
  1. Check Firebase database rules 
    {
  "rules": {
    "PlayerIpList": {
      ".read": true,
      ".write": true
    }
  }
}
    Ensure your Firebase Realtime Database has proper read/write permissions.
  2. Verify client initialization
    • Check that the client object is properly initialized (Form1.cs:37)
    • Look for error messages in the loading screen
    • Ensure PlayAcON() method is being called
  3. Check random name generation
    • The system uses GenerateRandomNames class to create unique identifiers
    • If this fails, player data won’t be stored correctly
    • Check for errors in the random name generation process
  4. Network path validation
    • Firebase path should be: PlayerIpList/{randomName}
    • Verify the path structure in your Firebase console
The client retrieves public IP addresses for player tracking.Symptoms:
  • IP shows as null or empty
  • Cannot connect to server
  • Player tracking not working
Solutions:
  1. Check IP detection service
    • ACHCE Client uses PublicIPAddress class to retrieve public IP
    • Ensure external IP detection services are accessible
    • Test with: curl ifconfig.me to verify IP detection works
  2. Behind NAT or proxy
    • If behind corporate firewall or complex NAT, IP detection may fail
    • Contact network administrator
    • May require alternative configuration
  3. IPv6 vs IPv4
    • Ensure your network supports the IP version being detected
    • Some networks may only support IPv6, causing IPv4 detection to fail
The IP address is primarily used for logging purposes. Hardware-based identification is the primary ban enforcement mechanism.
The application may freeze during the loading sequence.Symptoms:
  • Loading screen stuck
  • Application not responding
  • Timer animation stops
Solutions:
  1. Wait for Firebase connection
    • Initial connection may take 10-30 seconds
    • Timer1 waits for IP address detection before proceeding (Form1.cs:71-83)
    • Be patient on first launch
  2. Check system resources
    • Ensure sufficient RAM available
    • Close unnecessary applications
    • Check Task Manager for resource usage
  3. Disable startup timers temporarily
    • If problem persists, there may be an issue with timer initialization
    • Check timer2 tick event handler (Form1.cs:85-98)
  4. Run as administrator
    • Some operations may require elevated privileges
    • Right-click and select “Run as Administrator”
ACHCE Client requires .NET Framework 4.7.2 or higher.Symptoms:
  • Application won’t start
  • Error about missing .NET Framework
  • “The application requires .NET Framework 4.7.2”
Solutions:
  1. Install .NET Framework 4.7.2
  2. Verify installation 
    reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Version
    Check that version 4.7.2 or higher is installed
  3. Check App.config
    • Verify that App.config specifies correct runtime version (App.config:4)
    • Should reference v4.0 with .NETFramework,Version=v4.7.2
Required NuGet packages must be installed for the client to function.Symptoms:
  • “Could not load file or assembly ‘FireSharp’”
  • “Could not load file or assembly ‘Newtonsoft.Json’”
  • Application crashes on startup
Solutions:
  1. Restore NuGet packages 
    nuget restore
  2. Required packages (packages.config):
    • FireSharp 2.0.4
    • Newtonsoft.Json 6.0.4
    • Microsoft.Bcl.Async 1.0.168
    • Microsoft.Net.Http 2.2.28
  3. Manual installation 
    Install-Package FireSharp -Version 2.0.4
Install-Package Newtonsoft.Json -Version 6.0.4
Always use the exact versions specified in packages.config to avoid compatibility issues.
Form2 may not display correctly on multi-monitor setups.Symptoms:
  • Window appears on wrong monitor
  • Window size incorrect
  • Overlay not covering entire screen
Solutions:
  1. Set primary monitor
    • Windows Settings > System > Display
    • Select your gaming monitor as primary display
    • ACHCE Client uses primary screen bounds (Form2.cs:25)
  2. Check display scaling
    • Ensure display scaling is set to 100%
    • High DPI settings may cause size calculation issues
    • Form2 calculates size based on Screen.PrimaryScreen.Bounds
  3. Restart with single monitor
    • Temporarily disconnect secondary monitors
    • Launch ACHCE Client
    • If successful, issue is related to multi-monitor configuration
Player data should be automatically removed from Firebase when exiting.Symptoms:
  • Player entries remain in Firebase after closing
  • “Data deleted successfully” message doesn’t appear
  • Database clutter with old entries
Solutions:
  1. Ensure proper application closure
    • Use the exit button (pictureBox2_Click in Form2.cs:34-37)
    • Don’t force close with Task Manager
    • The FormClosed event handles cleanup (Form1.cs:100-104)
  2. Check Firebase permissions
    • Verify delete permissions in Firebase database rules
    • User must have write access to delete entries
  3. Handle crashes gracefully
    • If application crashes, FormClosed event won’t fire
    • Consider implementing a timeout mechanism in Firebase
    • Use Firebase database rules to auto-delete old entries
You can set up Firebase rules to automatically delete entries older than a certain time period to prevent database bloat.

​
Still Having Issues?

If you’ve tried the solutions above and are still experiencing problems:

Check FAQ

Review frequently asked questions about ACHCE Client

Review Configuration

Double-check your Firebase and client configuration

​
Debug Mode

For advanced troubleshooting, you can enable debug messages:
1

Uncomment debug messages

In Form1.cs, uncomment the MessageBox.Show statements:
  • Line 67: “data inserted successfully”
  • Line 103: “data deleted successfully”
2

Rebuild application

Recompile the project with debug messages enabled
3

Monitor Firebase console

Keep Firebase console open to watch real-time database changes
4

Check Windows Event Viewer

Look for application errors in Event Viewer > Windows Logs > Application
Remember to remove debug MessageBox statements before deploying to production, as they can interfere with the user experience.

​
Diagnostic Information

When reporting issues, include the following information:
  • Windows version
  • .NET Framework version
  • ACHCE Client version
  • Firebase configuration status (without credentials)
  • Error messages or screenshots
  • Steps to reproduce the issue
  • Whether running with administrator privileges

Build docs developers (and LLMs) love

Get started for freeTalk to us