In order to use the club job script on your server, you must set the framework settings
Integrating Club into ESX
Let's go inside the wais-club folder and open the Config.lua file with an editor.
Change the Config.Framework variable in the first lines of the Config file as below.
Config.Framework = { ["Framework"] ="esx", -- esx, qbcore or qbx ["ResourceName"] = "es_extended ", -- es_extended or qb-core or your resource name. If you using qbx you should write qb-core
["NewCore"] = true, -- If you use the new core, set this to true ( esx or qb ). If you are using the old one, make it false and edit the event below according to yourself.
["SharedEvent"] ="esx:getSharedObject" -- Event name for old cores.}
Integrating Club into QBCore
Config.Framework = { ["Framework"] ="qbcore", -- esx, qbcore or qbx ["ResourceName"] = "qb-core", -- es_extended or qb-core or your resource name. If you using qbx you should write qb-core
["NewCore"] = true, -- If you use the new core, set this to true ( esx or qb ). If you are using the old one, make it false and edit the event below according to yourself.
["SharedEvent"] ="qb-core:getSharedObject" -- Event name for old cores.}
Integrating Club into Qbx
Config.Framework = { ["Framework"] ="qbx", -- esx, qbcore or qbx ["ResourceName"] = "qb-core", -- es_extended or qb-core or your resource name. If you using qbx you should write qb-core
["NewCore"] = true, -- If you use the new core, set this to true ( esx or qb ). If you are using the old one, make it false and edit the event below according to yourself.
["SharedEvent"] ="" -- Event name for old cores.}
If the name of the core script is different, replace the value of the [“ResourceName”] variable with the script name