Notice that, if Config.RenewedBanking is true, TriggerEvent is being called for the following events:
qb-bossmenu:server:addAccountMoneyqb-bossmenu:server:removeAccountMoneyqb-gangmenu:server:addAccountMoneyqb-gangmenu:server:removeAccountMoney
These are old, deprecated events, right? So why are they being used when Config.RenewedBanking is true?
-- If qb-management, grab info directly from database
if Config.RenewedBanking then
local result = MySQL.Sync.fetchAll('SELECT * FROM management_funds')
...
The comment suggests checking for qb-management, but the code checks for Config.RenewedBanking and then proceeds to retrieve from the management_funds table, which I don't think Renewed-Banking even utilizes.
These seem mixed up, but maybe you can shed some light on why the code is doing this. Thank you.
Please see this file: https://github.com/jimathy/jim-payments/blob/main/server/atmserver.lua
1. Old Events
Notice that, if
Config.RenewedBanking
is true,TriggerEvent
is being called for the following events:qb-bossmenu:server:addAccountMoney
qb-bossmenu:server:removeAccountMoney
qb-gangmenu:server:addAccountMoney
qb-gangmenu:server:removeAccountMoney
These are old, deprecated events, right? So why are they being used whenConfig.RenewedBanking
is true?2. management_funds Table
Also, in the same file, please see lines 215-217: https://github.com/jimathy/jim-payments/blob/4ec75a90faaaa24a3933bda632d5406d5b169f33/server/atmserver.lua#L215-217
The comment suggests checking for qb-management, but the code checks for
Config.RenewedBanking
and then proceeds to retrieve from the management_funds table, which I don't think Renewed-Banking even utilizes.These seem mixed up, but maybe you can shed some light on why the code is doing this. Thank you.