Requirements#
| Framework | None. The resource works on any framework. |
| Resources | ox_lib (tested with 3.40.0) |
| Server | FiveM artifact with OneSync enabled |
| Database | None. The hacked list is kept in memory and resets when the resource restarts. |
| Optional | glitch-minigames, the default hack minigame (Config.DefaultHack). Point it at any other minigame resource, or set export = false and give each prop its own hackExport or hackEvent. |
There are no items and no SQL to install.
Installation steps#
- Put the
glitch-securityCamerasfolder in your server'sresourcesdirectory. The folder name is case sensitive on Linux. - Open
shared/config.lua. Add your cameras toConfig.Cameras, or setConfig.EnableExamples = trueto load two test cameras. Their prop models and some coordinates are placeholders. - Add this to
server.cfg, after ox_lib and afterglitch-minigamesif you use it:
ensure ox_lib
ensure glitch-minigames
ensure glitch-securityCameras
- Restart the server or the resource. Then follow Examples to enter a camera and test a hack.
The resource has no commands or ACE permissions. Access is controlled by the resources that call its exports.
Updating#
Back up shared/config.lua first, since it is the one file meant for editing. Replace the other files, merge any new settings from the new shared/config.lua into your copy, then restart the resource. Version 1.2.0 removed the onSuccessServerEvent and onFailServerEvent prop fields. If you used them, listen for glitch-securityCameras:server:hackCompleted instead. Keep the folder name glitch-securityCameras, because the exports use it.
Stuck on a step?Ask in the Discord →