NullSect
Systems nominal

Scripts / tools · v0.1.0

Combat Log

When a player quits, a "?" stays where they stood: walk up and see who left and why.

  • Qbox
  • QBCore
  • ESX

Features

  1. 01

    Marker where they quit

    A "?" at the exact spot for exits, crashes, timeouts and kicks, removed after a set time.

  2. 02

    Who and why

    Name, character, ids and how they left in plain words, read from FiveM's drop code.

  3. 03

    Copy for a report

    Press E to copy every shown field to the clipboard.

  4. 04

    Server-authoritative

    Clients cannot create, move or remove markers; no thread runs while there are none.

Requirements

Frameworks
Qbox, QBCore, ESX
Requires
Nothing extra
Works with
ox_lib
Version
0.1.0

Recent changes

Read the docs →

0.1.0

  • A "?" marker stays where a player quit (exit, crash, timeout, kick) for Config.Combatlog.duration seconds (default 3 minutes).
  • Walking up to it opens an info card: name, character, server id, citizen id, Discord id, reason and time (license / Steam optional, every field switchable in Config.Fields).
  • "Left by" row: quit (F8 quit / menu), crash, connection lost, kicked or reconnected, from the playerDropped drop code (text fallback on older server builds). The raw reason keeps its first line only.
  • E copies every shown field to the clipboard.
  • Players who quit from the character screen leave no marker; markers respect routing buckets.
  • Admin commands: /combatlogtest (test marker at your position), /combatlogclear.
  • EN / TR locales, no database.

Related

Cart

Your cart is empty.