# Client Exports

## **GetJobCategory**

This export retrieve the job category for the job requested. Why is it useful? because in some mods as the origen\_masterjob (the one we are offering full compatibility), business can be created dynamically ingame with different names; and with this export we can identify the specific job for the user to which job category belong.

<pre class="language-bash"><code class="lang-bash">-- job_name must be the job you are trying to categorize
<strong>exports['p6_bridge']:GetJobCategory(job_name)
</strong></code></pre>

For example:

Mechanic business named "exotic\_motors" created with origen\_masterjob, you want to integrate a mechanic mod that can be used only by all the mechanics (not only this business), with our export you can do this validation quick and easy

```bash
if exports['p6_bridge']:GetJobCategory(business_name) == 'mechanic' then
    -- Execute the code allowed to mechanics
else
    -- Display a notification with an error, player is not a mechanic
end
```

## **GetOnDutyPlayers**

This export retrieve number of players in service for this job, integrated with origen dispatch so is not counting connected players only, it's filtering by the players which are on duty.

**If you use this export to jobs that are not integrated with the configured dispatch, will return 0.**

```bash
-- job_name must be the job you are trying to categorize
exports['p6_bridge']:GetOnDutyPlayers(job_name)
```

## **SendTaxiAlert**

This event is used to manage a taxi call using the dispatch system, generating a notification to the taxi system and logging to discord

```bash
TriggerServerEvent("p6_bridge:sendTaxiAlert")
```

## **SendPoliceAlert**

This event is used to manage a police call using the dispatch system, generating a notification to the police system and logging to discord

```bash
-- type: Type of alert (GENERAL, RADARS, 215, DRUGS, FORCE, 48X) This is to filter the alerts in the dashboard
-- title: Title of the alert
-- message: Alert message
-- metadata: Additional metadata of the alert (vehicle model, color, plate, speed, weapon, ammo type, name of the subject, unit)
TriggerServerEvent("p6_bridge:sendPoliceAlert", type, title, message, metadata)
```

## **SendServicesAlert**

This event is used to manage a police, ems and firefighter call using the dispatch system, generating a logging to discord

```bash
-- type: Type of alert (GENERAL, RADARS, 215, DRUGS, FORCE, 48X) This is to filter the alerts in the dashboard
-- title: Title of the alert
-- message: Alert message
-- metadata: Additional metadata of the alert (vehicle model, color, plate, speed, weapon, ammo type, name of the subject, unit)
TriggerEvent("p6_bridge:sendServicesAlert", type, title, message, metadata)
```

## **SendDiscord**

This event is used to log to discord a specific action or message using the gateway

```bash
-- type: Type of log (alerts, chat, command) you can add new ones in custom/server/logs.lua
-- title: Title of the message
-- message: Message text
-- metadata: Additional metadata of the alert (vehicle model, color, plate, speed, weapon, ammo type, name of the subject, unit)
TriggerServerEvent('p6_bridge:sendDiscord', type, title, message)
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://physix-engineering.gitbook.io/physix-engineering-documentation/p6-bridge/exports/client-exports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.