RAC-Core setup and user guide.
Customer-facing help for server owners and staff: try the demo, connect a FiveM server, learn the main workflows, and fix common setup issues.
The shortest path to a connected server
Try the demo first if you want to see the panel before installing anything. When you are ready, follow the install steps in order.
Help for real product usage
The guide avoids internal release notes and focuses on what customers need to install, operate, and troubleshoot RAC-Core.
- Demo and sample-data behavior
- FiveM resource install steps
- Framework-specific feature notes
- Support, moderation, monitor, tablet, and resource workflows
A practical guide for server owners and staff.
RAC-Core gives your team a web panel and in-game tablet for support, moderation, live operations, analytics, and server health.
What RAC-Core ships
The product is centered on staff workflows that happen during live server operations.
Before you install
A few quick checks keep the first connection smooth.
- Access to server.cfg and your FiveM resources folder
- A RAC-Core server created in the panel
- Your framework resource loaded before RAC-Core
- screenshot-basic installed if you want screenshots or monitor frames
- ESX status support if you want hunger and thirst writes
Try the panel with safe sample data.
The demo is intended to feel like the live product. It uses session-scoped dummy data, so you can create tickets, reply, freeze sample players, restart sample resources, inspect analytics, and reset without touching a real server.
Close to the real panel
Overview, support, players, live monitor, resources, analytics, and audit views use the same workspace language as the full product.
Session state only
Demo actions change only your browser session. Reset returns the sample server, tickets, players, resources, and audit stream to their original state.
Self-hosted demo
If you host RAC-Core yourself, the demo requires DEMO_MODE=true and a reachable backend API base. The hosted demo should work without a real server.
Four steps to connect FiveM.
Start with the default install. Tune framework settings after the panel heartbeat is working.
Step 1 - Download and place the resource
Put the latest RAC-Core resource in your FiveM resources folder and keep the folder name as rac-core.
resources/
rac-core/
fxmanifest.lua
client/
server/
ui/Step 2 - Start required dependencies first
Start your framework and shared utility resources before RAC-Core. Install screenshot-basic if you want support screenshots or Premium live monitor frames.
ensure oxmysql
ensure screenshot-basic
ensure qb-core
ensure qbx_core
ensure es_extended
ensure rac-coreStep 3 - Add your panel credentials
Create or open your server in the RAC-Core panel, then copy the server ID and server token into server.cfg.
set rac_server_id "YOUR_SERVER_ID"
set rac_server_token "YOUR_SERVER_TOKEN"Step 4 - Restart and verify
Restart the resource, then confirm the startup banner, version check, and panel heartbeat.
restart rac-core
# or
ensure rac-coreThe settings most server owners need.
Credentials belong in server.cfg as convars. Framework behavior lives in rac-core/server/config.lua.
# server.cfg - required credentials
set rac_server_id "YOUR_SERVER_ID"
set rac_server_token "YOUR_SERVER_TOKEN"
# rac-core/server/config.lua - common options
Config.Framework = "AUTO" -- AUTO, STANDALONE, ESX, QBCORE, QBOX
Config.EnforceModeration = true
Config.Ui.AllowPlayersSupportAccess = true
Config.VersionCheck.Channel = "stable"Notes that matter
- Do not paste server tokens into screenshots, public tickets, or public repositories.
- Hosted resource packages are built for the hosted RAC-Core API. Self-hosted packages must be built or configured for your public domain.
- QBCore and QBOX use metadata-aware character handling.
- ESX surname handling can be adapted to your character package.
What each framework supports.
This table shows which features are framework-backed and which are part of the general RAC-Core operations layer.
| Framework | Supported data | Notes |
|---|---|---|
| Standalone | Moderation, support workflows, analytics, tablet, audit, device link, and queued actions that do not require framework economy data. | Use this when you want RAC-Core as an operations layer without ESX/QBCore/QBOX economy writes. |
| ESX | Job, grade, cash, bank, health, armour, hunger, thirst, offline queue, support, and analytics. | Hunger and thirst need esx_status or compatible handlers. Surname writes can be adapted in Config.FrameworkAdapters.ESX. |
| QBCore | Job, grade-only updates, cash, bank, charinfo last name, health, armour, hunger, thirst, and offline queue. | Uses qb-core exports and metadata-aware handling for character and status writes. |
| QBOX | Job, grade-only updates, cash, bank, charinfo last name, health, armour, hunger, thirst, and offline queue. | Detected through qbx_core and uses the qbx export path directly. |
Standalone
Moderation, support workflows, analytics, tablet, audit, device link, and queued actions that do not require framework economy data.
Use this when you want RAC-Core as an operations layer without ESX/QBCore/QBOX economy writes.
ESX
Job, grade, cash, bank, health, armour, hunger, thirst, offline queue, support, and analytics.
Hunger and thirst need esx_status or compatible handlers. Surname writes can be adapted in Config.FrameworkAdapters.ESX.
QBCore
Job, grade-only updates, cash, bank, charinfo last name, health, armour, hunger, thirst, and offline queue.
Uses qb-core exports and metadata-aware handling for character and status writes.
QBOX
Job, grade-only updates, cash, bank, charinfo last name, health, armour, hunger, thirst, and offline queue.
Detected through qbx_core and uses the qbx export path directly.
Use the product during live staff work.
Most teams spend their time in support, player profiles, live operations, moderation, and the audit trail.
Support workflows (Pro+)
Help and report threads, assignment, replies, status changes, and screenshots in one place.
Live monitor (Premium)
A 16-slot operator view with telemetry and screenshots for active player oversight.
Security and RBAC
Staff roles, per-user permissions, VPN/proxy visibility, join controls, and sticky risk tracking.
World controls (Premium)
Sensitive world actions such as clearing entities require Premium and the matching permission.
Offline queue
Character and action changes can remain queued until the resource sees the player and acknowledges delivery.
Audit trail
Staff actions and important system events are recorded for later review.
A focused surface for staff already in session.
The tablet is a compact version of the daily workflow, tuned for quick in-game actions rather than long desktop review.
In-game commands
`/support` - Open the support chooser for help or reports.
`/help` - Open the help request flow.
`/report` - Open the report flow.
`/racpanel` - Open the RAC-Core in-game panel.
`/ractablet` - Open the tablet control surface.
Actor-bound actions
goto, bring, and spectate are intentionally in-game because they need a staff actor in the server session.
Give staff the access they need, not everything.
Role presets and per-user overrides let owners separate read access, support access, resource controls, moderation, and high-risk actions.
Security controls
VPN/proxy visibility, allowlists, banned identifiers, join controls, chat flood protection, and weighted risk scoring.
RBAC model
Role templates work as presets, then user overrides let server owners tune access for individual staff members.
Understand server health and player behavior.
RAC-Core turns player density, crash locations, disconnect reasons, entity trends, and per-player activity into operational signals.
Player activity
Player count trends, live density, and per-player activity timelines.
Crash and disconnect views
Crash hotspots, disconnect breakdowns, and visual density overlays.
Economy and jobs
Economy flow sampling and job movement trends over time.
Control resources without guessing.
Resource management is a Premium workflow. Listing and control are separately permissioned so owners can allow visibility without allowing restarts or stops.
Control
Start, stop, restart, and refresh resources from the panel when your role allows it.
Monitoring
Track state, average and max ms, restart counts, and resource event logs.
Policy
Critical resources can be protected so staff cannot stop or restart sensitive services accidentally.
Confirm the basics before handing it to staff.
Most first-run problems come from setup, dependency, or permission mismatches.
The FiveM console prints the RAC-Core startup banner and version check.
The panel shows the server as online and the heartbeat card updates.
At least one player join appears in the panel.
Free monitors up to 64 online players. Pro and Premium support unlimited player monitoring.
Support and help/report pages are available on Pro or Premium.
Live monitor, screenshots, resource management, custom commands, live map, and world controls are available on Premium.
Queued actions remain pending until the resource polls and acknowledges them.
What to check first when something does not work.
Start with these checks before changing framework settings or reinstalling the resource.
Connection and framework issues
- No players in the panel: confirm the API base, server ID, server token, and startup banner.
- Server stays offline: confirm the resource is started and the backend URL in the package matches your deployment.
- Framework values missing: keep Config.Framework = "AUTO" unless you need to force detection.
Screenshots, queue, and web issues
- No screenshots: confirm screenshot-basic is installed, started before RAC-Core, and not blocked by plan access.
- Queued actions remain pending: inspect the panel heartbeat and server console for poll or ack failures.
- ESX hunger or thirst missing: verify esx_status or compatible handlers are installed.
- Demo does not load: self-hosted installs need DEMO_MODE=true and a web API base that reaches the backend.