Incident log runbook
When something breaks, the worst response is panic edits on the live server. This runbook turns chaos into a routine. You capture the evidence, reproduce it, classify it, fix or escalate, and write it down so the same fire does not start twice. It pairs your txAdmin logs with your Discord reports into one workflow.
The runbook
Capture before you change anything
Grab the exact console error. Note the timestamp. Note the player or resource involved. Note what they were doing.
A screenshot of the report plus the matching console line is enough. Do not start editing yet.
Reproduce it
Try to trigger it yourself on a test server, or at a quiet time. A bug you can reproduce is a bug you can fix. A bug you cannot reproduce gets a watch entry, not a guess-fix.
Classify the severity
Sort it into one of three buckets: critical (server down, money or items exploitable), major (a core feature broken), or minor (cosmetic, rare). Critical jumps the queue. Minor goes on the list.
Fix or escalate, then deploy safely
If the resource is yours, fix it on your PC, test it, and deploy with the Git loop. If it is a paid resource, open a support ticket with your captured evidence. Never patch directly on the live server.
Record the incident
Log one line per incident: date, symptom, cause, fix, and the resource or commit involved. A commit is the unique ID Git gives each saved change (see the Git lesson), so "commit a1b2c3d" lets a future you jump straight to the exact code that fixed it.
Over time this log becomes the fastest debugging tool you own.
2026-06-12 | shop dupe on rapid-click | client trusted for grant | added server cooldown + qty check | commit a1b2c3d
Keep reading the full lesson
Sign in to start, then unlock every step of this lesson and the full FiveM School with a membership.
- How it works
- If something went wrong
- What you can do now
- Try it yourself
The remainder of Incident log runbook is available to FiveM School members.