How leafysmoke/rframework works
RFramework is a FiveM roleplay framework. Its documented player workflow begins when a player joins, loads and manages player data, and presents current stats in a HUD. Developers can also use framework APIs for jobs, money, spawning, and client-server callbacks. The tree identifies server, client, shared, and QB-compatibility code, but no source excerpts were provided; edges therefore show only relationships documented in the README, not inferred calls between implementation modules.
Main entry points: player.lua Player management · functions.lua Framework API · main.lua Client API · events.lua Server callbacks
Components 18
Player lifecycle
- Player management
[RFramework]/rf-core/server/player.lua - Character handling
[RFramework]/rf-core/server/character.lua - Character collection
[RFramework]/rf-core/server/characters.lua - Client player state
[RFramework]/rf-core/cllient/character.lua - Stats HUD
[RFramework]/rf-core/cllient
Gameplay services
- Job system
[RFramework]/rf-core/server/jobs.lua - Money and bank
[RFramework]/rf-core/server/money.lua - Inventory
[RFramework]/rf-core/server/inventory.lua - Vehicles
[RFramework]/rf-core/server/vehicles.lua - Groups
[RFramework]/rf-core/server/groups.lua
Framework interfaces
- Framework API
[RFramework]/rf-core/server/functions.lua - Client API
[RFramework]/rf-core/cllient/main.lua - Server callbacks
[RFramework]/rf-core/server/events.lua - QB compatibility
[RFramework]/rf-core/bridge/qb - Shared utilities
[RFramework]/rf-core/shared/utils.lua
Persistence
- MySQL service
- Player records
[RFramework]/rf-core/sql.sql
Other components
- FiveM player
Connections 10
- FiveM player → Player management: joins; loads data
README.md - Player management → Stats HUD: manages stats shown
README.md - Player management → Player records: persists data
README.md - MySQL service → Player records: stores records
README.md - Framework API → Player management: gets player
README.md - Framework API → Money and bank: adds or removes money
README.md - Framework API → Job system: sets job
README.md - Client API → Server callbacks: requests callback
README.md - Server callbacks → Client API: returns result
README.md - Client API → Client player state: gets player data
README.md