Track 2 · Pro Path

Exports: sharing functions across resources

Events fire and forget. Exports are function calls: synchronous, they return a value, and they run on the same side that registered them. They are how every framework you have ever used wires resources together, exports.ox_inventory:GetItemCount, exports.es_extended:getSharedObject. This lesson teaches you to expose a function safely and, more importantly, to consume it from a second resource so you see the cross-resource call the topic is named for.

You'll learn: exports('name', fn) registration, exports.resource:fn() call syntax, why exports are synchronous and same-side, the global-namespace risk, and when to reach for an event instead
Time: ~18 minutes
Prereqs: Lessons 13 & 14 (events)
Outcome: You can build a money resource a second resource reads from with exports.qu_money:GetBalance(src), and explain why it is a real function call and not an event

BEFORE YOU START

Build it

Make the two resource folders

The server has one folder per resource.

Inside your server's resources folder, create both of these folders:

code

resources/qu_money
resources/qu_money_consumer

Exports: sharing functions across resources

Build it

Make the two resource folders

Create the files

Write qu_money/fxmanifest.lua

Write qu_money/server.lua

Write qu_money_consumer/fxmanifest.lua

Write qu_money_consumer/server.lua

Start and test it

Keep reading the full lesson