Module B6 · Build real features

How a script talks to a framework

You already know how to register a command and print a line. The missing piece is the player. A framework like ESX, QBCore, or Qbox is the thing that knows who the player is, how much cash they hold, and what job they work. Your script does not store any of that. It asks the framework. In this lesson you build one server script that asks all three the same two questions, give $100 and what is your job, and you watch each one answer in its own dialect.

You'll build: A server script that detects whether the server runs ESX, QBCore, or Qbox, gets the player object, gives them $100, and prints their job. The same action, three frameworks, one file.
Time: ~24 minutes
You need: A local server running ONE framework you can restart (es_extended, qb-core, or qbx_core), plus the natives toolbox and command/print habits from earlier modules.
You'll learn: How to get the player object in each framework -> how to read money and job -> the export style vs the event style -> why real scripts detect the framework first and then branch

BEFORE YOU START

How a script talks to a framework

The one idea: your script asks, the framework answers

Keep reading the full lesson