Bodycam & Dashcam

Installation

ensure ox_lib
ensure sx_bodycamdashcam

set R2_BUCKET ""
set R2_ACCOUNT_ID ""
set R2_ACCESS_KEY_ID ""
set R2_SECRET_ACCESS_KEY ""

Configuration

Ace Permission Setup

Available Ace Permissions

Example Usage

add_ace group.admin "DashcamSetup" allow
add_ace group.police "BodycamDashcam" allow # Only needed for standalone mode

Inventory Integration

ox_inventory

If you are using the ox_inventory inventory, you must include the export table within the item data for the bodycam item.

Example:

['bodycam'] = {
  label = 'Bodycam',
  weight = 0.1,
  consume = 0,
  server = {
    export = 'sx_bodycamdashcam.bodycam'
  }
},

This is required for the item to function properly with ox_inventory.

Bodycam Configuration

The bodycam script is highly configurable via the ClientConfig.Bodycam section. Below are the key options and their explanations:

Recording Storage

Bodycam recordings support:

• Fivemanage
• Cloudflare R2

Discord webhooks are not supported for bodycam video uploads.

Fivemanage Setup

To use Fivemanage for recording storage, you need to generate an API key from your Fivemanage dashboard.

Fivemanage = {
  ApiUrl = 'https://api.fivemanage.com/api',
  ApiKey = 'replace_with_your_api_key', -- HERE
  OnlyShowDepartmentRecordings = true,
  DepartmentFolderPaths = {
    ['police'] = '/police',
  },
}

Storage = {
  Provider = "fivemanage"
}

Cloudflare R2 Setup

To use Cloudflare R2, configure both your Cloudflare credentials and storage provider.

set R2_BUCKET "your_bucket_name"
set R2_ACCOUNT_ID "your_account_id"
set R2_ACCESS_KEY_ID "your_access_key_id"
set R2_SECRET_ACCESS_KEY "your_secret_access_key"

Storage = {
  Provider = "r2"
}

Recording Time Limit: The maximum recording duration can be configured in Recording.RecordingLimit (default: 300 seconds).

Permissions Configuration

If you are using a framework (not standalone), you must configure the Permissions table to control access to bodycam and dashcam features. Example:

Permissions = {
  BodycamDashcam = {
    ['police'] = 1
  },
  ViewCameras = {
    ['police'] = 2
  },
  DeleteRecordings = {
    ['police'] = 3
  }
}

• BodycamDashcam: Allows the specified jobs to use bodycam & dashcam features.
• ViewCameras: Allows the specified jobs to view camera recordings.
• DeleteRecordings: Allows the specified jobs to delete recordings.

If you set ClientConfig.Framework to standalone, the script will ignore Permissions and instead require the ace permission BodycamDashcam (name is configurable).

Storage Options: OnlyShowDepartmentRecordings & DepartmentFolderPaths

• OnlyShowDepartmentRecordings: Ensures that players with a job can only see recordings from their own folder path set in DepartmentFolderPaths. For example, a player with the police job will only be able to see recordings in the /police folder.
• DepartmentFolderPaths: Specifies the folder where recordings for each job are saved. For example, ['police'] = '/police' saves police recordings in the /police folder. Leaving this table empty will save all recordings in the root directory.

Dashcam Configuration

The dashcam script is configurable via the ClientConfig.Dashcam section. Below are the key options and their explanations:

Usage

Bodycam

• Toggle the bodycam overlay using the /bodycam command.
• Start recording by pressing the X or using the /recordbodycam command.
• The bodycam must be equipped and allowed for your job.
• Recording uploads footage to your configured provider (fivemanage or r2).

Dashcam

• Use the /dashcamsetup command in-game to set up dashcam positions for vehicles. This command requires the DashcamSetup ace permission.

exports['sx_bodycamdashcam']:registerVehicleDashcam(netId, {
    jobName = player.PlayerData.job
})

Guides

Troubleshooting

• Ensure ox_lib is installed and started before sx_bodycamdashcam. Click here
• Make sure you have the correct ace permissions for dashcam setup. Click here