💿 Configure
Config Editor (Recommended for Updates)
Use the NoLag config editor to upload, edit, and export your Properties config:
https://config.nolag.properties
When updating to a newer version, this is the recommended workflow. The editor helps identify newly introduced config options and adds them into your existing config, making updates safer and easier than fully manual merges.
Camera
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.cfgfile and put the following variable. You need to put your fivemanage api key instead ofPUT_YOUR_API_KEY_HEREset 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.
Shell Detection System
The nolag_properties resource includes an automatic shell detection system, designed to simplify the process of adding and managing custom shell packs.
Shells are automatically detected and registered by nolag_properties without requiring any manual configuration inside the core script.
How it works
Each shell pack must include a JSON configuration file located at:
custom/shells/ShellPackName.json
For the system to correctly detect and load the shell pack, the resource name must match the name defined in the JSON file.
Important Requirement
- The resource folder name must be identical to the shell pack name used in the JSON configuration.
- If the names do not match, the shell pack will not be detected or loaded by the system.
Example
If your JSON file is:
custom/shells/MainHousingPack.json
And inside it the shell pack is defined as:
{
"resourceName": "K4MB1-MainHousingPack"
}
Then your resource folder must be named:
K4MB1-MainHousingPack
Notes
- The system automatically scans available resources on server start.
- Multiple shell packs are supported.
- This approach allows easy drag-and-drop installation of new shell packs without modifying existing code.