#No such export GetCoreObject in resource qbx_core
1 messages · Page 1 of 1 (latest)
is this right if not what would it be
if FRAMEWORK == "ESX" then
ESX = exports['es_extended']:getSharedObject()
DebugPrint("^2[REPORTS] Using ESX Framework^0")
elseif FRAMEWORK == "QB" then
QBCore = exports['qb-core']:GetCoreObject()
DebugPrint("^2[REPORTS] Using QBCore Framework^0")
elseif FRAMEWORK == "QBX" then
QBCore = exports['qbx_core']:GetCoreObject()
DebugPrint("^2[REPORTS] Using QBX Framework^0")
elseif FRAMEWORK == "VRP" then
local Proxy = module("vrp", "lib/Proxy")
VORP = Proxy.getInterface("vRP")
DebugPrint("^2[REPORTS] Using VRP Framework^0")
else
DebugPrint("^2[REPORTS] Using Standalone (No Framework)^0")
end
I’ve got that but it’s shooting of that error 🤔
try reading those then, it specifically tells you qbx_core doesnt use GetCoreObject()
Kind of misleading, it does use GetCoreObject, just not its own, it uses the qbcore GetCoreObject()
Sorry what? o.O
Due to the backwards compatibility? Or am i missing something?
Because last i checked, it uses the qbcore getcoreobject, not its own.
The bridge uses that yes, qbx itself doesn't use get coreobject. Bruiser is reffering to his code that is trying to call that.
elseif FRAMEWORK == "QBX" then
QBCore = exports['qbx_core']:GetCoreObject()
DebugPrint("^2[REPORTS] Using QBX Framework^0")
Which doesn't exist.
You don't need to call the whole core like qbcore to enable exports.
That's what i was referring to, Qbox doesn't use its own GetCoreObject, since it doesn't have one, so it relies on QBCores, no?
No, If your setting up a config that sets the framework. You shouldn't be relying on the bridge at that point
Oh wait, you're right, man, i should probably get some sleep.