How to use State Bags

A State Bag is a sticky note attached to a player or entity that every resource can read. You write a value once, and FiveM copies it everywhere automatically. No events, no asking around. Need to know a player's job, hunger, or radio channel? Just read their note. In 2026 this is the standard way to share data that lots of resources need but nothing breaks if it's a beat late.

You'll build: A resource that sets, gets, and reacts to State Bag changes - sharing data between resources without events.
Time: ~20 minutes
You need: A local FiveM server, one resource you can edit.
You'll learn: Player vs entity State Bags, setting and getting values, reacting to changes with handlers, and when to use State Bags vs events.

BEFORE YOU START

Build it

Create the resource

A new resource folder with the basic files.

code

resources/qu_statebag_demo/
fxmanifest.lua
server.lua
client.lua

code

fx_version 'cerulean'
game 'gta5'

server_script 'server.lua'
client_script 'client.lua'

Set a State Bag value (server)

The player's State Bag has a 'job' key.

Write a value to a player's note. We do this on the server because the server is the boss of player state:

code

-- Set a State Bag value for a player
local playerId = 1  -- replace with actual player ID
local playerState = Player(playerId).state

playerState:set('job', 'police', true)  -- true = replicate to all clients
print(('Set player %s job to police'):format(playerId))

How to use State Bags

Build it

Create the resource

Set a State Bag value (server)

Read a State Bag value (client)

React to State Bag changes

Keep reading the full lesson