Library — DistroSource

Everything digital. One source.

9 resources

Checklist · Beginner · 10 min
Weekly FiveM server health check checklist
The fifteen-minute weekly check that catches problems before players do.
- Servers decay quietly: a resource starts erroring, backups stop, staff drift. Fifteen minutes a week catches it.
- ☐ Crash log read; new errors noted with the resource name
- ☐ Console warnings for slow resources reviewed
Items 10
Guide · Beginner · 8 min
Reading the FiveM server console
How to read the console and logs to find what broke, before asking anyone.
- Most FiveM problems announce themselves in the console. This guide shows what the common messages mean, how to find the resource responsible, and what to try before posting in a support channel.
- Start-up messages
- Runtime errors
Playbook · Intermediate · 4h
Migrate a FiveM server to a new host: playbook
Move a live server to a new host with minimal downtime and nothing lost.
- The server running on the new host with the same data, resources and players.
- Step 1: Provision and mirror
- Step 2: Test with staff
Steps 5Deliverables 3
Cheat sheet · Beginner · 5 min
FiveM server admin cheat sheet
Commands, files and habits for running a server. 4 sections, 15 entries.
- Files
- Console
- Permissions
Entries 15
Checklist · Beginner · 10 min
FiveM server launch checklist
What must be true before the server opens to the public.
- Opening day problems are almost always on this list.
- ☐ Clean boot with no console errors
- ☐ Framework and dependencies at documented versions
Items 10
Guide · Beginner · 8 min
FiveM frameworks compared for a new server
What ESX, QBCore and Qbox each assume, and how to choose for the server you actually want.
- The framework decides which resources you can use, how your economy behaves and who can help you when it breaks. This guide compares the three common choices on the questions that matter for a new roleplay server.
- What a framework provides
- ESX
Playbook · Beginner · 2h
Server operations and moderation: playbook
Run the server day to day: rules, staff, incident handling and updates that do not break weekends.
- A server that stays up and a community that stays civil.
- Step 1: Publish five rules
- Step 2: Structure staff and permissions
Steps 5Deliverables 3
Playbook · Intermediate · 2h 30m
Resource configuration and conflicts: playbook
Install and configure scripts so they do not fight each other, with a method for finding the one that breaks things.
- Resources added without breaking existing ones, and conflicts found in minutes.
- Step 1: Install on staging first
- Step 2: Read the config before starting
Steps 5Deliverables 3
Playbook · Intermediate · 5h
Stand up a FiveM roleplay server: playbook
Build a stable FiveM server from a clean install to a private test with a framework, essential resources and backups.
- A server that ten testers can join and play on for an evening without a crash.
- Step 1: Install the artifacts and the base
- Step 2: Choose and configure the framework
Steps 6Deliverables 3

Search