The Yetti yetti combatlog script tackles one of the most frustrating problems in roleplay servers: players who disconnect mid-fight to avoid the consequences. When someone logs out during combat, the script spawns a lootable ped in their place, so leaving the server no longer means escaping cleanly. Suddenly, rage-quitting a losing gunfight carries a very real cost.
That standing ped represents the disconnected character right there on the street. It shows the character name and Rockstar license with a handy copy button for staff, and nearby players can rob it, cloning the offender's inventory into loot that fairly reflects the risk of a real firefight.
How the Yetti yetti combatlog script works
- Spawns a visible ped when a player disconnects during an active encounter.
- Displays the character name and R* license with a convenient one-click copy option.
- Lets other players rob the ped, duplicating the disconnected inventory as recoverable loot.
- Restores the original items back to the player once they reconnect to the server.
- Configurable timers control how long the ped remains before it despawns.
Why anti-combat-log tools matter
- Removes the incentive to rage-quit or dodge losses by force-closing the game.
- Keeps firefights fair by ensuring consequences land even after a sudden disconnect.
- Gives staff quick access to identifying details for later follow-up reports.
- Compatible with QB, Qbox, and ESX inventories for wide server support.
- Lightweight and event-driven, so it costs almost nothing while sitting idle.
Combat logging quietly erodes trust in a server's rules, and manually moderating every incident is exhausting for admins. By turning a disconnect into an in-world event with real stakes, this resource discourages the behavior automatically while adding a dramatic new loot opportunity for the players left standing.
Installation is simple and the configuration is short. Set your preferred despawn timers, confirm the framework bridge matches your inventory system, and restart the resource. From there the system runs entirely on its own, requiring no daily attention from your staff team. The logic is deliberately simple, which keeps it easy to audit and unlikely to conflict with the other combat and inventory scripts you already run. For most servers it becomes a quiet, dependable safeguard that just works in the background night after night.
Protect the integrity of your firefights with dependable enforcement, and browse more moderation tools in our admin and utility scripts or explore the full catalog of FiveM scripts for your community.
