Glossary

Code running on a player’s FiveM game. Client-side actions should not be trusted as proof of payment or permissions.

A resource that must start before another resource can work.

A named function exposed by a resource to another resource. Its name and direction must match the shipped code.

Code connecting a resource to a server framework such as QBCore, Qbox or ESX when supported.

The resource manifest that declares files and metadata for a FiveM resource.

A folder of FiveM scripts and assets started by the server.

Code running on the FiveM server, where sensitive state changes should be checked.

A versioned database change supplied with a resource release, when applicable.

An interaction library for selecting entities or zones in game.