Skip to content

Society Banking Setup

ARS VVS Guns V2 uses society accounts to deposit money from weapon sales. When a player purchases a weapon, the payment goes directly to the shop’s society bank account.

This guide explains how to set up the society account depending on which banking system your server uses.


The script automatically detects your banking system in this priority order:

  1. okokBanking - Auto-detected (highest priority)
  2. ars_banking - Auto-detected
  3. qb-banking - Used when Config.SocietyInBank = true
  4. qb-management - Used when Config.SocietyInBank = false

If okokBanking or ars_banking is running on your server, the script uses it automatically regardless of Config.SocietyInBank.


Many QBCore servers run into issues because QBCore changed how society accounts work:

QBCore VersionSociety SystemConfig Setting
Old QBCoreqb-management handles society accountsConfig.SocietyInBank = false
New QBCoreqb-banking handles society accountsConfig.SocietyInBank = true

If you are unsure which version you have:

  1. Check if you have qb-banking in your resources folder
  2. Check if your qb-management has society-related exports (GetAccount, AddMoney, RemoveMoney)
  3. If qb-banking exists as a separate resource, you likely have the newer QBCore setup

This is the default society system in older QBCore builds where society accounts are managed through qb-management.

Setup:

  1. Open ars_vvsguns_v2/config.lua and set:

    Config.SocietyInBank = false
  2. Ensure qb-management is running in your server.cfg

  3. The boss menu location must be added to qb-management (already covered in QBCore Installation Step 3)

Exports used:

exports['qb-management']:GetAccount(job)
exports['qb-management']:AddMoney(job, amount)
exports['qb-management']:RemoveMoney(job, amount)

No additional database tables or configuration needed beyond the standard qb-management setup.


Newer QBCore builds moved society accounts to qb-banking. This is a separate resource that handles banking with society support.

Setup:

  1. Open ars_vvsguns_v2/config.lua and set:

    Config.SocietyInBank = true
  2. Ensure qb-banking is running in your server.cfg

  3. The society account for vvsgundealer must exist in qb-banking’s database

Exports used:

exports['qb-banking']:GetAccountBalance(job)
exports['qb-banking']:AddMoney(job, amount)
exports['qb-banking']:RemoveMoney(job, amount)

If money is not depositing: Check that the job name vvsgundealer matches exactly in your qb-banking society accounts table.


okokBanking is a popular third-party banking system that supports society accounts. It is auto-detected when the resource is running.

Setup:

  1. Install okokBanking following its own installation guide

  2. Open okokBanking/config.lua (or okokBankingV2/config.lua) and add the vvsgundealer job to Config.Societies:

    Config.Societies = {
    ["police"] = {4},
    ["ambulance"] = {3, 4, 5},
    ["vvsgundealer"] = {3}, -- Grade 3 (Owner) has full access
    }

    The number {3} means grade 3 (Owner) has full access to the society bank account. Add other grades if needed:

    ["vvsgundealer"] = {2, 3}, -- Grades 2 (Manager) and 3 (Owner) have access
  3. In okokBanking config, verify the society resource is set correctly:

    Config.SocietyResource = "okokBanking"
  4. Run the okokBanking SQL queries for the okokbanking_societies table (included in okokBanking’s installation SQL)

  5. No changes needed in ars_vvsguns_v2/config.lua - okokBanking is auto-detected

Exports used:

exports['okokBanking']:GetAccount(society)
exports['okokBanking']:AddMoney(society, amount)
exports['okokBanking']:RemoveMoney(society, amount)

Verification: After setup, restart your server and check that the vvsgundealer society account appears in okokBanking’s banking UI.

Note: If okokBanking is running, it takes priority over qb-banking and qb-management regardless of Config.SocietyInBank.


ars_banking is another banking system that supports society accounts. It is auto-detected when the resource is running.

Setup:

  1. Install ars_banking following its own installation guide

  2. Ensure the vvsgundealer society account is registered in ars_banking

  3. No changes needed in ars_vvsguns_v2/config.lua - ars_banking is auto-detected

Exports used:

exports['ars_banking']:GetAccount(job)
exports['ars_banking']:AddMoney(job, amount)
exports['ars_banking']:RemoveMoney(job, amount)

Note: ars_banking is checked after okokBanking but before qb-banking in priority.


The following banking systems also support society accounts in QBCore but are not yet built into this script. If you use one of these, you will need to modify server/utils.lua to add support:

Banking SystemResource NameExports
Renewed-BankingRenewed-BankinggetAccountMoney(society), addAccountMoney(society, amount), removeAccountMoney(society, amount)
fd_bankingfd_bankingGetAccount(society), AddMoney(society, amount), AddGangMoney(society, amount)
Tgiann-bankTgiann-bankVaries - check Tgiann docs
tgg-bankingtgg-bankingAddSocietyMoney(society, amount)
kartik-bankingkartik-bankingAddAccountMoney(society, amount, reason)
p_bankingp_bankingaddAccountMoney(society, amount, reason)

To add support for one of these, open server/utils.lua and add the resource check in the GetSocietyMoney, AddSocietyMoney, and RemoveSocietyMoney functions, following the existing pattern:

-- Add this in GetSocietyMoney, AddSocietyMoney, and RemoveSocietyMoney:
if GetResourceState('Renewed-Banking') == 'started' then
return exports['Renewed-Banking']:getAccountMoney(job)
end

ESX uses esx_society and esx_addonaccount for society accounts. This is handled automatically when Config.Framework = 'esx'.

Setup:

  1. Ensure esx_society is running

  2. The script automatically registers society accounts on startup using:

    TriggerEvent('esx_society:registerSociety', job, job, 'society_'..job, 'society_'..job, 'society_'..job, {type = 'private'})
  3. No additional configuration needed for ESX


  1. Check which banking system is running on your server
  2. Verify the correct Config.SocietyInBank setting for qb-banking vs qb-management
  3. If using okokBanking, verify the job is added to Config.Societies
  4. Check server console for any export errors
  5. Verify the job name matches exactly between ars_vvsguns_v2 config and your banking system
  • QB: The job vvsgundealer does not have a society account in your banking system
  • Fix: Add the job to your banking system’s society configuration (see setup guides above)
  • Verify the resource name is exactly okokBanking (case-sensitive)
  • Check that okokBanking is started before ars_vvsguns_v2 in your server.cfg
  • Ensure okokBanking SQL has been run and okokbanking_societies table exists
  • The boss menu reads from a different source than the society account
  • Verify you are checking the correct bank account (society account, not personal)
  • For qb-management: the boss menu reads from qb-management’s account
  • For qb-banking/okokBanking: check the society banking tab

If you are switching from one banking system to another:

  1. Stop your server
  2. Update Config.SocietyInBank in ars_vvsguns_v2/config.lua if needed
  3. Update your banking system’s society configuration
  4. Restart your server

Important: okokBanking and ars_banking are auto-detected and take priority. If you have one of these running but want to use qb-banking instead, you must stop/remove the other banking resource.


Banking SystemAuto-DetectedConfig RequiredESX Support
qb-managementNoConfig.SocietyInBank = falseNo
qb-bankingNoConfig.SocietyInBank = trueNo
okokBankingYesAdd job to Config.SocietiesYes
ars_bankingYesNoneNo
Renewed-BankingNoManual code editNo
fd_bankingNoManual code editNo
esx_societyYesNone (ESX only)Yes

Note: This guide is written by a third party. If you find any incorrect or outdated information, please contact us on Discord so we can update it for you.