Performance: 0.00ms while not near a locker | 0.03-0.05ms while in storage unit.
Escrow Protected
Price: ÂŁ8.00 (ÂŁ9.60 with tax - Tax is subject to region) Purchase Link
Unescrowed Version
Price: ÂŁ28.00 (ÂŁ33.60 with tax - Tax is subject to region) Purchase Link
This resource uses FiveM’s Asset Escrow System This uses RPC events on the server side so will require onesync to be enabled.
Editable Notifications and Language settings. // Editable HTML and Javascript
Updates
31/05/22: Added config option to use an item to open the locker creation menu instead of command based.
-- This allows an item to be used by anyone to create a storage locker.
useItem = false
-- The name of the item required.
itemName = 'storage_locker'
-- Should the item be removed on use.
removeItemOnUse = false
Brilliant idea, I will look at adding the ability to specify during the create command if you would like to create a prop at the location and if so which prop.
it seems that the database has accepted the queries correctly, if you would like further support, you can reach out via support option listed on my tebex store or via my dms on the forums.
Would it be possible, instead of using a collande /addlocker to open the menu, to ensure that when I buy the “chest” object it opens the menu?
And delete the item, so I make sure that the companies that will put the chests, must buy the chest beforehand to resell it to their customers
Seen that the script and locks I can’t do it myself
Update: Added config option to use an item to open the locker creation menu instead of command based.
-- This allows an item to be used by anyone to create a storage locker.
useItem = false
-- The name of the item required.
itemName = 'storage_locker'
-- Should the item be removed on use.
removeItemOnUse = false
Hey, for which Chezza inventory version is this? and how does that work when you use esx because instead of the QB menu as I see it like video the ESX menu is opened or how exactly is that done I would look forward to a positive feedback
This is set to work with chezza-inventory for ESX however the inventory event can be changed in the functions file, when it comes to the menu, if you set esx in the config then it will use the esx menu, if its qbcore then it will use the qbcore menu.
I am not sure if it will work with other versions of ESX as I have only tested this within the Zap Hosting ESX Pack as this is what is supplied with txAdmin by standard. anyone with the pin can access the storage, it can be set in config if you want only the owner to be able to do specific things like change pin and so on.