Configuration

Choose the Compatible Framework and Inventory Scripts

• Select the appropriate SQL and Inventory script versions that align with your server package to ensure compatibility.

Config.ChangeClothesSystem

• Determines whether the clothing change system is enabled. If set to true, the clothing change feature is active. If false, this feature is disabled.

Config.ClothingScript

• Specifies the clothing script being used. Supported options are: "fivem-appearance", "illenium-appearance", "esx_skin", and "qb-clothing". Here, it's set to "qb-clothing".

• If you’re not using any of the listed clothing scripts or a different script, make sure to check the refreshSkin function. This function is necessary to ensure character clothing updates properly with your specific script.

Config.TebexSystem

• Controls the Tebex system (in-game store access for players). If set to true, it’s enabled; if false, it’s disabled.

If your clothing script is not one of the supported options, consider modifying or checking the refreshSkin function to ensure compatibility with your custom setup.

This section of the configuration allows you to set up the coordinates, heading, and interaction point for the mission's starting NPC (ped). Here’s a breakdown of each entry:

• interactionCoords: Defines the coordinates for the interaction point used by target scripts. This is where the player can initiate an interaction with the NPC.

• ped: When set to true, it enables the presence of the NPC (ped) at the specified coordinates.

• pedCoords: Specifies the coordinates where the NPC (ped) should be located.

• pedHeading: Sets the direction the NPC is facing, using a heading value.

• pedHash: Indicates the specific NPC model or character to be used at this location.

This configuration is essential for setting up the mission's starting point and ensuring that the NPC appears in the correct location and orientation, with an interaction point compatible with target scripts.

Mission Completion Rewards

This section allows you to configure item rewards that players receive upon completing a mission. You can choose to give items in addition to any monetary reward. Here’s how to set it up:

• giveItemPlayer:

  • Set this to true if you want players to receive items upon mission completion.

  • If set to false, no items will be given, and only the default rewards (such as money) will apply.

• itemList:

  • This is a list of items that the player can receive. You can define multiple items here, and each item entry allows for customization of the quantity.

  • Example:

    • { item = "sandwich", count = math.random(1, 4) }: This entry will reward the player with a random quantity of sandwiches, ranging from 1 to 4.

    • { item = "sandwich", count = 1 }: This entry will give the player exactly 1 sandwich.

Using these options, you can add variety to mission rewards by including multiple items or randomizing the quantity of each item given.

Job Clothes Configuration

This section lets you set up the clothing for male and female characters in a job.

• male and female: Define specific clothing items with model and texture values for each part (e.g., jacket, shirt, shoes).

  • Example:

    • jacket: Model 97 for males, 239 for females, with different texture options.

Adjust the values as needed to match the desired appearance for each character in the job.

Key Functions Overview

This configuration handles three main features: assigning vehicle keys, removing vehicle keys, and managing fuel levels. Here's a simplified explanation:

1. Vehicle Key Assignment (Config.Vehiclekey)

   • This function is used to assign keys to a vehicle based on the selected vehicle key system.

   • Depending on the system defined in Config.VehicleSystem (like cd_garage, qs-vehiclekeys, wasabi-carlock, or qb-vehiclekeys), it triggers the appropriate event or export to give the player a vehicle key.

2. Vehicle Key Removal (Config.RemoveVehicle)

   • This function is used to remove keys from a vehicle if Config.Removekeyes is set to true.

   • It checks which vehicle key system is being used and removes the key accordingly through the configured event or export.

3. Fuel System (Config.FuelSystem and Config.SetVehicleFuel)

   • This section manages the fuel system, allowing you to set the fuel level of a vehicle.

   • Config.FuelSystem lets you choose between different fuel systems, such as LegacyFuel, x-fuel, ox_fuel, or cdn-fuel.

   • Config.SetVehicleFuel function sets the fuel level based on the selected system, ensuring compatibility with the fuel script you’re using.

This setup provides flexibility to integrate with various key and fuel management systems, making it adaptable to different server configurations.