Studios
Security Camerascams-2.jpg

Installation

FreeSecurity CamerasStandalone
PAGE 02 OF 06  ·  OVERVIEW → INSTALLATION → CONFIGURATIONdocs.glitchstudios.dev
Browse docs

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#

  1. Put the glitch-securityCameras folder in your server's resources directory. The folder name is case sensitive on Linux.
  2. Open shared/config.lua. Add your cameras to Config.Cameras, or set Config.EnableExamples = true to load two test cameras. Their prop models and some coordinates are placeholders.
  3. Add this to server.cfg, after ox_lib and after glitch-minigames if you use it:
ensure ox_lib
ensure glitch-minigames
ensure glitch-securityCameras
  1. 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.