THE ORB
Starting the studio

A framework event does not exist

One script called out to another and nothing answered. There is often no error at all — the feature just never happens.

groupsA feature silently does nothingcodeNeeds a developer

Do this first

Check both scripts are running and are versions meant for each other.

bug_reportPaste your whole console instead

What it means

Code triggered an event nothing listens for. FiveM does not error on this: the trigger silently does nothing, and the symptom is a feature that never runs rather than a red line. When a message does appear it is usually the framework itself complaining.

What causes it

Ordered by how often it is the answer.

  1. 1

    The event was renamed between framework versions

    esx:getSharedObject was removed in ESX Legacy. QBCore:Server:OnPlayerLoaded vs QBCore:Client:OnPlayerLoaded are different events for different sides.

  2. 2

    The listening resource is not started

    The handler exists but is not registered because its resource is down.

  3. 3

    RegisterNetEvent was never called

    A net event needs both RegisterNetEvent and a handler. AddEventHandler alone does not accept a trigger from the network.

  4. 4

    Client/server confusion

    TriggerEvent is local to that side. TriggerServerEvent and TriggerClientEvent cross the boundary. Using the local one for a remote handler fires into a void.

  5. 5

    A typo

    The event name is a string, so nothing checks it.

How to tell which one is yours

Add a print inside the handler. If it never runs, the trigger is not reaching it. Then grep for the exact event name across every resource:

grep -rn "esx:playerLoaded" resources/

If the only match is the trigger, nothing listens.

Where to look

Both sides: the trigger and the intended handler.

How to fix it

-- server
RegisterNetEvent('myres:buy')
AddEventHandler('myres:buy', function(item)
    local src = source
end)

-- client
TriggerServerEvent('myres:buy', item)

Still stuck on your own code?

This page is what this error usually means. Paste your console into Server Fixer and it will rank everything in it and tell you what to do first, and if you would rather not touch it, ORBIE can repair the script and hand the resource back ready to drop in.

bug_reportOpen Server Fixer

Errors that travel with this one