Resource Configuration

This page provides comprehensive information about our configuration files, assisting in the setup of the resource.

---

cfg.alboFMS

This feature allows integration with Albos FMS. When enabled, any units connected to a CAD and defined in the resources configuration will have their station turnout system activated automatically. The CAD information will then be printed on the tip sheet. If disabled, the resource will not receive Albos FMS events.

Albos Force Management System (FMS)

---

cfg.zWigWags

This feature enables integration with zWigWags. When enabled, WigWags will activate at the station when they are mobilized. zTurnout-System will activate the WigWag groupId that corresponds to its own systemId. This systemId can be located at the beginning of each block in the config.lua file under cfg.turnoutSystems. This implies that your configured wigwags must match the block number of the stations. An example can be located below. Both of the blocks identified as [1] will collaborate in the execution of the scripts.

-- // zWigWags: Config.lua

cfg.wigwagGroups = {
   -- BLOCK START --
   [1] = {
      {
         coordinates = vector3(0.0, 0.0, 0);
         rotation = vector3(0.0, 0.0, 0);
         stopRadius = 15.0
      };
      {
         coordinates = vector3(0.0, 0.0, 0);
         rotation = vector3(0.0, 0.0, 0);
         stopRadius = 15.0
      }
   };
   -- BLOCK END --
}

-- // zTurnout-System : Config.lua

cfg.turnoutSystems = {
  -- BLOCK START --
   [1] = {
      stationName = 'Bolton Central Fire Station';
      stationCallsign = 'G50';
      -- / Station Appliances: 
      ['stationAppliances'] = {
         'G50P1';
         'G50P2';
      };
      -- / Countertop Location: 
      ['counterLocation'] = {
         coordinates = vector3(0.0, 0.0, 0.0);
         rotation = vector3(0.0, 0.0, 0.0)
      };
      -- / Printer Location: 
      ['printerLocation'] = {
         coordinates = vector3(0.0, 0.0, 0.0);
         rotation = vector3(0.0, 0.0, 0.0)
      };
      -- / lollipop Settings: 
      ['lollipopSettings'] = {
         allow = true;
         coordinates = vector3(0.0, 0.0, 0.0);
         rotation = vector3(0.0, 0.0, 0.0);
            colours = {
               ['BLUE'] = 'G50P1';
               ['AMBER'] = 'G50P2';
               ['RED'] = '';
               ['GREEN'] = '';
               ['WHITE'] = '';
            };
         displayTime = 30
      };
      -- / Speaker Settings: 
      ['speakerSettings'] = {
         coordinates = vector3(0.0, 0.0, 0.0);
         soundFile = 'LIFERISK';
         distance = 25.0
      };
   };
  -- BLOCK END --
}

zWigWags Store Page

---

cfg.notificationSound

Set this option to 'true' to enable notification sound effects when receiving notifications, or set it to 'false' if you prefer not to have sound effects for notifications.

---

cfg.interactKeybind

This feature allows you to customize the keybind for printer interaction. It is important to note that this feature only accepts whole numbers and does not support decimal values or text. You can access a comprehensive list of FiveM's keybinds and their respective numerical codes through the provided hyperlink.

FiveM Controls

---

cfg.discordLog

In this section, you have the option to activate Discord logging for mobilizations.

• Allow: If this option is enabled, a message will be sent to the designated webhook URL when mobilizations occur. The message will contain all relevant information regarding the mobilization. If this option is disabled, no messages will be sent to Discord.

• Webhook: This option enables you to input your desired Discord webhook URL, which is the channel where log messages will be sent. If you are unsure of how to obtain a webhook URL, please visit the link provided below.

• Community Name: This option allows you to input your community's name. This text will be displayed in the Discord log message.

• Community Logo: This option enables you to upload your community's logo, and this image will be displayed in the Discord log message.

Introduction to Discord Webhooks

---

cfg.commands

In this section, you have the capability to make adjustments to all of the resource's commands.

• Incident Form: In this section, you have the option to modify the command used for displaying the incident form.

• Tip Sheet: In this section, you have the option to modify the command used for viewing your current tip sheet.

• Give Sheet: In this section, you have the option to modify the command used for sharing your current tip sheet with another client.

---

cfg.translations

This section allows you to customize the script's strings based on your preferences, whether it's modifying the language or making general edits to message aspects.

---

cfg.turnoutSystems

In this section, you have the ability to indicate the locations of turnout systems.

Within the table cfg.turnoutSystems, there is a separate table or block of code for each station. These blocks are identified by unique numbers, such as [1], [2], and so on. The beginning and end of each block are delineated by comments within the config.lua file.

Example of a block

cfg.turnoutSystems = {
  -- BLOCK START --
   [1] = {
      stationName = 'Bolton Central Fire Station';
      stationCallsign = 'G50';
      -- / Station Appliances: 
      ['stationAppliances'] = {
         'G50P1';
         'G50P2';
      };
      -- / Countertop Location: 
      ['counterLocation'] = {
         coordinates = vector3(0.0, 0.0, 0.0);
         rotation = vector3(0.0, 0.0, 0.0)
      };
      -- / Printer Location: 
      ['printerLocation'] = {
         coordinates = vector3(0.0, 0.0, 0.0);
         rotation = vector3(0.0, 0.0, 0.0)
      };
      -- / lollipop Settings: 
      ['lollipopSettings'] = {
         allow = true;
         coordinates = vector3(0.0, 0.0, 0.0);
         rotation = vector3(0.0, 0.0, 0.0);
            colours = {
               ['BLUE'] = 'G50P1';
               ['AMBER'] = 'G50P2';
               ['RED'] = '';
               ['GREEN'] = '';
               ['WHITE'] = '';
            };
         displayTime = 30
      };
      -- / Speaker Settings: 
      ['speakerSettings'] = {
         coordinates = vector3(0.0, 0.0, 0.0);
         soundFile = 'LIFERISK';
         distance = 25.0
      };
   };
  -- BLOCK END --
}

New tables should always be positioned after the comment -- BLOCK END --. This comment indicates the conclusion of the previous block.

It's crucial that the ID you insert within the brackets is both unique and non-duplicate.

---

Station Name:

This field should contain the name of the station. This value is not referenced in the script and is intended to assist you in managing all your configured stations within the config.lua file.

---

Station Callsign:

This field should include the callsign of the station. The callsign should be displayed in front of all its appliance callsigns, for example, 'G50'.

---

Station Appliances:

The callsigns of all the appliances at the station should be entered in this field. Each callsign should include the station's callsign as a prefix. For instance, 'G50P1', where G50 represents the station callsign and P1 represents the appliance callsign.

---

Counter Location:

In this section, you can determine the placement and rotation of the countertop within the station.

• Coordinates: In this field, please input the 3D world coordinates for the countertop location. This information determines where the countertop will spawn. The format for this option is vec3(x, y, z)

• Rotation: In this section, you will specify the rotation for the countertop . This enables you to position the countertop precisely in the desired orientation. The format for this option is vec3(pitch, roll, yaw)

---

Printer Location:

In this section, you can determine the placement and rotation of the printer within the station.

• Coordinates: In this field, please input the 3D world coordinates for the printers location. This information determines where the printer will spawn. The format for this option is vec3(x, y, z)

• Rotation: In this section, you will specify the rotation for the printer. This enables you to position the printer precisely in the desired orientation. The format for this option is vec3(pitch, roll, yaw)

---

Lollipop Settings:

In this section, you have the ability to determine the placement and rotation of the lollipop light within the station. Additionally, you can further configure the callsign associated with each colour that will be displayed by the lollipop light.

• Allow: This is a Boolean value that indicates whether the lollipop light should be used at this station. If the Boolean is set to 'true', the lollipop light will be spawned and function as intended. Conversely, if the boolean is set to 'false', the lollipop light will not be spawned or function at the station.

• Coordinates: In this field, please input the 3D world coordinates for the lollipop light. This information determines where the lollipop light will spawn. The format for this option is vec3(x, y, z)

• Rotation: In this section, you will specify the rotation for the lollipop light. This enables you to position the lollipop light precisely in the desired orientation. The format for this option is vec3(pitch, roll, yaw)

• Colours: In this section, you have the option to configure a distinct light colour for each callsign. This colour will be showcased on the lollipop light when the callsign is mobilised.

• Display Time: Here, you have the capability to adjust the duration in seconds for which the light will remain active. This value should be an integer and must not include any decimal points.

---

Speaker Settings:

In this section, you will be able to specify the placement of the alarm speaker and its audible distance.

• Coordinates: Here, you should enter the 3D world coordinates for the alarm speaker, specifying the location from which the turnout alarm sound will emanate. This option is formatted as vec3(x, y, z)

• Distance: Here, you will specify the distance at which the turnout alarm can be heard. This value must be a float, which implies it should always include a ".0" at the end. For instance, 35.0, 25.0, and so on.

• Sound File: This field should contain the name of the audio file you wish to play when the station is mobilized. These audio files can be found within the /interface/sounds directory. Please ensure that you do not include the file type (e.g., .mp3) when entering the name.

---

---