Optimize ChocoHax settings for maximum protection and performance on your FiveM server
Configuration is Critical
Configuration is really important and takes time, and with a great configuration you can have great protection and no false positives.
Configuration Overview
Understanding ChocoHax configuration options and best practices
Server Settings Panel
Access via your server dashboard
Time Investment
Proper setup prevents issues later
Zero False Positives
With proper configuration
Step-by-Step Configuration Guide
1
Setup Discord LogsConfigure Discord webhooks to receive real-time notifications about server security events
Essential Webhooks
General Webhook: Overall server activity
Admin Actions: Ban/kick/warn notifications
Warnings: Detection alerts before punishment
Screenshots: Evidence of detected cheats
Configuration Tips
- • Use separate channels for different alert types
- • Enable logging in ChocoHax settings first
- • Test webhooks after setup with a test message
- • Consider backup webhook URLs for redundancy
2
Configure Protection FiltersSecurity
Set up entity, weapon, and explosion filters to prevent malicious content
Weapons Protection
Configure weapon spawning and usage detection:
- • Blacklist overpowered and unused weapons
- • Set reasonable kill limits and distance
- • Monitor discord logs for false positives
Explosions Protection
Control explosion types and spam prevention:
- • Whitelist safe explosions (vehicles, etc.)
- • Blacklist dangerous types
- • Enable anti-spam protection if needed
Entities Protection
Prevent malicious entity spawning:
- • Enable anti-spam checks
- • Whitelist common vehicles/peds
- • Monitor object spawning
- • Set up auto-cleaning
3
Test in Warn ModeTesting
Test all protection features safely before enabling full punishment
Testing Strategy
Set all punishments to
warn
Monitor Discord logs for false positives
Test during peak server hours
Ask staff and/or players to test common activities
What to Test
- • Vehicle spawning and modifications
- • Weapon usage in different scenarios
- • Player interactions and commands
- • Resource interactions (ESX/QBCore)
- • Map-specific activities and events
4
Apply Configuration ChangesRequired
Restart your server to apply configuration settings to both server and client
Restart Process:
- Save your configuration changes in the panel
- Stop your FiveM server completely
- Wait 10-15 seconds
- Start your server again
- Perform a second restart after the first restart completes
Two Restarts Required
Configuration settings need 2 restarts for settings to apply to the client side. The first restart applies server-side settings, and the second restart ensures all client-side configurations are properly loaded.
F8 Console Error?
If the F8 Client sided console errors out for missing config, please check your
/your_chosen_name/client/client.lynx if it exists, and retry the restart process.Config Fails to Save?
If the configuration fails to be saved in the panel, try manually exporting and placing the config file:
- Click the icon beside the/button
- Select Export Config to download the configuration file
- Rename the downloaded file to
config.json - Place it in your
your_chosen_namefolder
File Structure:
📁 server-data/
📁 resources/
📁 [scripts]/
📁 your_chosen_name/ ← Place config.json here
📄 fxmanifest.lua
📄 core.lua
📄 config.json ← Export and place here
📁 client/
📁 locales/
Permission Management Options
Internal Permissions
Recommended
Built-in permission system with web interface
Easy web-based management
Group-based permission system
Real-time updates
Multiple identifier support
Best for most servers. Configure in Settings → Permissions.
ACE Permissions
Advanced
FiveM native permission system via server.cfg
Native FiveM integration
Works with other resources
Requires server.cfg editing
More complex setup
Good for servers with existing ACE setups. See our ACE guide.
txAdmin/QBCore
Framework
Framework-specific permission integration
Framework integration
Familiar interface
Limited ChocoHax features
Framework dependency
Use when you need framework-specific integration.
Whitelisted Areas
False Positive Prevention
Create safe zones where certain protections are disabled to prevent false triggers
Common Use Cases
Casino Interiors: Disable certain detections in gambling areas
Race Tracks: Allow high speed without speed hack detection
Admin Areas: Safe zones for staff testing
Event Locations: Temporary zones for special events
Configuration Tips
- • Use descriptive names for easy identification
- • Set appropriate detection ranges (50-1000m)
- • Enable only necessary protection bypasses
- • Get coordinates from in-game position
- • Test areas thoroughly before going live
Pro Tip: Start with smaller areas and expand as needed. Too large whitelisted areas can reduce overall protection effectiveness.
Quick Configuration Actions
Access configuration tools and resources