Core-Injuries — FiveM Injury System
Professional tier-based injury system for FiveM roleplay servers. Crutches, wheelchairs, arm slings, EMS tools, knockout mechanics, and full persistence — built for QBCore, QBox, ESX, and Standalone.
🎬 Showcase
Why Core-Injuries?
Most injury scripts are a toggle. Crutch on, crutch off. Core-Injuries is a full system — four injury tiers, real-time statebag sync, an EMS proximity menu, knockout physics, and persistence across restarts. Every tier has its own prop, clipset, walk speed, and duration bounds. EMS can see a player's live status and apply a custom duration in seconds. Knockout victims ragdoll, regen health, and wake up injured. Nothing needs to be configured to detect your framework — it auto-detects on start.
🏥 Injury Tiers
Minor — Crutch prop, 0.8x walk speed, sprint/jump disabled, 15 min default
Moderate — Crutch prop, 0.5x walk speed, sprint/jump disabled, 30 min default
Severe — Crutch prop, 0.3x walk speed, sprint/jump disabled, 60 min default
Wheelchair — Wheelchair prop, no movement, 120 min default
All values editable in config/injury.lua. Add custom tiers, swap props, change clipsets — no encrypted files involved.
✨ Full Feature List
Injury System
4 tiers with unique clipsets, props, and movement penalties
Seamless tier transitions — no relog required
Self-removal toggle per tier (force EMS interaction on severe/wheelchair)
Skin reload watch — props re-attach automatically on clothing change
EMS Tools
Proximity context menu (3m range) — see live tier + time remaining, apply or clear instantly
Custom duration input per tier, clamped to configurable min/max bounds
/emsinjury,/emsheal,/emsmenucommands with job permission checks
Knockout Mechanics
Melee knockout below configurable health threshold
Weapon knockout above configurable damage spike threshold
Screen blur + vignette + color grading during KO
Ragdoll with HP regen, cooldown, and auto-applies post-KO injury tier
Persistence (optional)
oxmysql — injuries survive server restarts
Auto table creation on first start
Expired row cleanup job
Audit trail:
ems_cleared,expired,self_removed,crutch_used
Framework Support
Auto-detects QBox, QBCore, ESX, Standalone — zero config needed
One-line override if auto-detect fails
Encrypted bridge layer — core logic never touches framework code directly
Performance
Total active client budget: ≤ 0.21ms/frame
Adaptive sleep — 2000ms idle, 500ms when active
All features individually toggleable — disable what you don't use
📦 Requirements
FiveM Server Artifacts — 3095+
ox_lib — v3.28.0+
ox_inventory — Latest
oxmysql — Latest (optional — persistence only)
⚙️ What's Editable vs Encrypted
config/ — all config files, fully open and unescrow'd
Core sync, bridge, enforcement logic — encrypted
You configure everything. The encrypted portion is only the internals you'd never need to touch anyway.
📥 Links
💬 Discord — discord.gg/TBb4QKHQtm
🐙 GitHub — github.com/Core-Forge-5
📺 YouTube — @CoreForgeFivem
📋 CFX Thread —
Core-Injuries— Built by CoreForge.