Module 02 · Lesson 08

Client, server, shared: three folders, one resource

Open almost any serious FiveM resource and you see the same three folders: client/, server/, and shared/. They are not decoration. Each one runs in a different place, and putting a line in the wrong folder is how beginners leak secrets, crash the client, or wonder why a value is nil. This lesson builds the split for real and then teaches the rule for deciding where every line you write belongs.

You'll build: A three-folder resource where a shared config table is read by both the client and the server, proven across the network with one command.
Time: ~20 minutes
You need: A local FiveM practice setup you can restart, a text editor, and the ability to read both txAdmin Live Console and F8 output.
You'll learn: The client / server / shared split, the decision rule for what goes where, why shared runs on both sides, glob imports, and what must never live in shared

BEFORE YOU START

Build it

Make the resource folder

The server has one folder for this lesson.

Inside your server's resources folder, create this folder:

code

resources/qu_client_server_shared

Client, server, shared: three folders, one resource

Build it

Make the resource folder

Create the three folders and their files

Write fxmanifest.lua

Write the shared config

Write the server code

Write the client code

Start and test it

Keep reading the full lesson