Anti CombatLog
Anti CombatLog - Tired of players rage-quitting just to save their loot? This script makes sure they don’t escape the consequences.
Pré-visualização em Vídeo
Click to load video from YouTube. By watching, you agree to their privacy policy.
Anti CombatLog - Advanced FiveM Combat Logging Prevention System
Eliminate one of the most frustrating exploits on FiveM servers with this comprehensive anti-combat logging solution. Combat logging - when players disconnect during active combat or police pursuits to avoid consequences - ruins immersion and fairness. This script detects and punishes combat logging across all major scenarios including shootouts, police chases, robberies, and player confrontations.
What's Included
This isn't just a basic disconnect detector - it's a sophisticated combat state tracking system that monitors multiple trigger conditions and applies appropriate consequences. The script tracks player combat status through weapon usage, damage received, police proximity, wanted levels, and active robbery participation. When a player disconnects while flagged in any combat state, the system automatically applies configurable penalties that persist across sessions.
You get a complete anti-combat logging solution with intelligent detection algorithms, false positive prevention, administrator bypass options, comprehensive logging for server moderation, and full framework integration for job-based rules. The system works seamlessly in the background, requiring zero player interaction while maintaining server integrity.
Key Features
- Multi-Trigger Combat Detection - Tracks combat state through weapon firing, damage taken, police wanted status, law enforcement proximity, and active crime participation. No single detection method means fewer false positives.
- Smart Cooldown Timers - Configurable grace periods after combat ends. Players must wait a set duration (typically 30-60 seconds) after combat before safely disconnecting. Prevents run and quit exploits.
- Vehicle Spawn Prevention - Players who combat log lose their vehicle permanently or temporarily. Configurable to delete the vehicle, move it to impound, or flag it for police seizure.
- Inventory & Money Penalties - Automatically removes configurable percentages of cash and items from combat loggers. You choose the severity - from mild warnings (10% loss) to severe punishment (100% inventory wipe).
- Temporary Bans - Repeat offenders can be automatically banned for configurable durations (1 hour, 24 hours, 7 days, or permanent). Escalating punishment system discourages repeat violations.
- Database Logging - Every combat log incident is recorded with timestamp, player identifier, combat reason, and applied penalties. Essential for investigating player reports and identifying chronic offenders.
- Admin Bypass System - Server staff and authorized personnel can safely disconnect during combat without penalties. Permission-based exemptions prevent false punishments during server management.
- Reconnect Penalties - When combat loggers rejoin, they spawn at hospital or police station (configurable), lose combat log status items, and receive notification of their violation. No escaping consequences.
- Police Interaction Detection - Special rules for law enforcement encounters. Being chased, handcuffed, or within police proximity during wanted status triggers combat logging protection.
- Robbery & Heist Protection - Active participation in store robberies, bank heists, jewelry store jobs, or gang activities triggers extended combat status. Prevents loot and disconnect exploits.
Combat State Triggers
The script monitors multiple conditions to determine combat status. Understanding these triggers helps configure the system for your server's specific needs:
Weapon-Based Detection:
- Firing any weapon (guns, melee weapons, explosives)
- Being shot at or hit by weapons
- Aiming weapons at other players in close proximity
- Damage dealt or received within configurable time window
Law Enforcement Detection:
- Active wanted level (1 star or higher)
- Police within chase radius (configurable distance, typically 50-100 meters)
- Being handcuffed or restrained by law enforcement
- Evading active police pursuit (fleeing with wanted level)
- In police custody or being arrested
Criminal Activity Detection:
- Active robbery in progress (stores, banks, jewelry stores)
- Participating in gang territory activities
- Lockpicking vehicles or properties
- Drug selling or manufacturing activities (if integrated)
- Kidnapping or holding hostages
Player vs Player Detection:
- Damage exchange between players within time threshold
- Being in close proximity during active shooting
- Punch/melee combat between players
- Vehicle ramming or vehicular combat
Configurable Penalty System
Tailor the punishment to match your server's rules and player expectations. The script offers granular control over every consequence:
Financial Penalties:
- Remove 0-100% of player cash (bank and/or wallet)
- Flat fee deduction (e.g., $5,000 combat log fine)
- Escalating fines for repeat offenses
- Option to transfer fines to police/government funds
Inventory Consequences:
- Remove illegal items only (drugs, weapons, stolen goods)
- Remove percentage of all inventory items
- Complete inventory wipe for severe violations
- Transfer items to police evidence locker
Vehicle Handling:
- Delete vehicle permanently
- Move to impound with retrieval fees
- Transfer ownership to police/government
- Temporary vehicle access suspension
Respawn & Status:
- Force respawn at hospital (lose location advantage)
- Spawn at police station (if wanted)
- Temporary health/armor reduction on reconnect
- Cooldown period before rejoining activities
Repeat Offender Escalation:
- 1st offense: Warning + minor penalties
- 2nd offense: Moderate penalties + temporary ban (1-24 hours)
- 3rd offense: Severe penalties + extended ban (7 days)
- 4th+ offense: Maximum penalties + permanent ban option
Perfect For
- Serious Roleplay Servers - Maintains immersion by preventing players from escaping consequences through disconnecting. Essential for servers with realistic crime/punishment systems.
- PvP-Enabled Servers - Stops players from quitting during gang wars, turf battles, or player confrontations to avoid death and item loss.
- Police Roleplay Servers - Prevents suspects from disconnecting during pursuits, arrests, or jail time. Law enforcement can complete proper booking procedures.
- Economy-Focused Servers - Protects server economy by ensuring players can't exploit combat logging to avoid financial losses from robberies or fines.
- Heist & Robbery Servers - Prevents exploits where criminals disconnect after successful heists to secure loot without risk of police recovery.
Installation & Configuration
- Download & Extract - Unpack the anti-combatlog script to your server resources folder
- Database Setup - Import the provided SQL file to create combat log tracking tables (for persistent penalties and logging)
- Configure Settings - Edit config.lua to set combat timers, penalty amounts, detection triggers, and admin exemptions
- Framework Integration - Configure framework-specific settings (ESX, QBCore, QBOX) for inventory, money, and police job integration
- Set Cooldown Timers - Define how long players must wait after combat (recommended: 30-60 seconds for gunfights, 2-5 minutes for police chases)
- Configure Penalties - Set money loss percentages, inventory removal rules, vehicle handling, and ban durations
- Add Admin Permissions - Grant combat log exemptions to server staff identifiers or permission groups
- Test Thoroughly - Verify detection works across all scenarios and penalties apply correctly on reconnect
- Restart Server - Start the resource and monitor logs for first 24 hours to fine-tune detection sensitivity
Framework Compatibility
- ✅ ESX Legacy - Full integration with ESX inventory, bank accounts, and police job. Supports es_extended 1.9+ and ESX Legacy.
- ✅ QBCore - Native QB inventory integration, qb-management money handling, and qb-policejob wanted level detection.
- ✅ QBOX - Compatible with QBOX inventory systems and law enforcement integrations.
- ✅ Custom Frameworks - Modular design allows adaptation to custom inventory, banking, and police systems with minimal code changes.
Technical Specifications
- Performance Impact: Minimal - uses efficient event triggers instead of constant polling
- Database: MySQL/MariaDB/OxMySQL compatible for logging and persistent penalties
- Dependencies: Framework-specific (ESX/QBCore/QBOX), no additional resources required
- Server Resmon: <0.01ms idle, <0.05ms during combat state checks
- Detection Accuracy: >95% accuracy with default settings, adjustable for stricter or looser detection
- False Positive Prevention: Built-in grace periods and multi-trigger confirmation reduce accidental penalties
Advanced Features
Webhook Integration: Connect to Discord webhooks to log all combat log incidents in a dedicated moderation channel. Includes player name, identifier, combat reason, penalties applied, and timestamp for easy staff review.
Grace Period System: Legitimate disconnections (server crashes, internet outages) during brief combat moments can be configured with grace periods. Players who weren't actively engaged for long enough receive reduced or no penalties.
Whitelisted Jobs: Certain jobs (medics, mechanics) can be exempt from combat logging in specific scenarios. For example, medics responding to active shooting scenes won't be penalized for nearby combat detection.
Custom Notifications: Fully customizable player notifications inform users when they enter combat status, how long until they can safely disconnect, and what penalties they'll face for combat logging.
Configuration Examples
Light Roleplay Server (Lenient):
- Combat timer: 30 seconds after last shot
- Money penalty: 10% cash loss
- Inventory: Illegal items only
- Vehicle: Moved to impound ($500 fee)
- Ban: Warning only, no ban until 3rd offense
Serious Roleplay Server (Moderate):
- Combat timer: 60 seconds after combat, 3 minutes during police chase
- Money penalty: 25% cash + $2,500 fine
- Inventory: 50% of all items removed
- Vehicle: Impounded with $2,500 retrieval fee
- Ban: 1 hour on 2nd offense, 24 hours on 3rd
Hardcore PvP Server (Strict):
- Combat timer: 2 minutes after combat, 5 minutes during wanted status
- Money penalty: 75% cash + 50% bank funds
- Inventory: Complete wipe of all items
- Vehicle: Permanently deleted
- Ban: 24 hours on 1st offense, permanent on 2nd
What Makes It Stand Out
Most anti-combat logging scripts rely solely on weapon fire detection, leading to false positives when players shoot at NPCs or participate in hunting activities. This script uses multi-layered detection that requires multiple combat indicators before flagging a player. A player hunting animals won't trigger combat status, but a player shooting at another player while wanted by police absolutely will.
The escalating penalty system means first-time accidental combat logs (rare legitimate internet disconnects) result in minor consequences, while chronic exploiters face increasingly severe punishments. This balanced approach maintains fairness while effectively deterring intentional combat logging.
Additionally, the comprehensive logging system creates an audit trail that helps server staff identify patterns of abuse, investigate player reports, and make informed decisions about ban appeals. You'll know exactly when, why, and how often each player has combat logged.
Moderation Tools
Administrators get access to special commands for managing the combat log system:
/combatlog [playerID]- Check if a player is currently in combat status/clearcombat [playerID]- Manually clear combat status (for false positives or legitimate issues)/combathistory [playerID]- View player's combat log violation history/combatpardon [playerID]- Remove penalties and ban from combat log violation/combatconfig reload- Reload configuration without server restart
Support & Documentation
The script includes detailed configuration documentation explaining every setting, recommended values for different server types, and troubleshooting guides for common issues. Example configurations for light, moderate, and hardcore enforcement are included to help you get started quickly.
