The camera is used in the creation panel or the property management portal. It's used to take photos of the properties you create. The script depends on chip's screencapture and the photos are uploaded to fivemanage by default, but all that functionality is open in nolag_properties/server/Camera.lua . We are not going to provide support on changing that because we strongly encourage you to use that instead of screenshot-basic or any other screenshot resources.
1
Configure the API Key
Go to your server.cfg file and put the following variable. You need to put your fivemanage api key instead of PUT_YOUR_API_KEY_HERE
set PROPERTIES_UPLOAD_TOKEN "PUT_YOUR_API_KEY_HERE"
2
Restart the server
Restart your server, and your camera should work if you did everything correctly.
Shells
You can enable the shells you are using in config.lua under the Shells section. If you are using any shells that are not added by default, you can refer to the Add More Shells section.
-- Supported Shells by default
-- If you want to add more shells you can take a look at the custom/shells folder
Shells = {
K4mb1StarterShells = true, -- [FREE] https://k4mb1maps.com/product/5015840
EnviShells = false, -- [FREE] https://envi-scripts.tebex.io/package/6407814
AllShellsBundle = false, -- [PAID] https://k4mb1maps.com/product/4741607 (Lifetime) | https://k4mb1maps.com/product/5107241-1 (Monthly)
AllShellsBundle2 = false, -- [PAID] https://k4mb1maps.com/product/4741607 (Lifetime) | https://k4mb1maps.com/product/5107241-1 (Monthly)
JamaringV1 = false, -- [PAID] https://jamaring-maps.tebex.io/package/6095279
JamaringV2 = false, -- [PAID] https://jamaring-maps.tebex.io/package/6274927
JamaringV3 = false, -- [PAID] https://jamaring-maps.tebex.io/package/6377855
JamaringV4 = false, -- [PAID] https://jamaring-maps.tebex.io/package/6559637
MaxCreations = false, -- [PAID] https://maxcreationsstore.tebex.io/package/6177840
FuryV1 = false, -- [PAID] https://fury.tebex.io/package/6215866
FuryV2 = false, -- [PAID] https://fury.tebex.io/package/6629276
},
