Refactored Set vehicle Properties

[l2rhydra]

Description

This PR enhances vehicle color compatibility by allowing props.color1 and props.color2 to accept RGB table values (e.g., {255, 255, 255}), in addition to the existing integer-based color indexes. This update ensures compatibility with scripts that utilize RGB values for vehicle customization.

---

Motivation

Currently, using RGB tables (e.g., via mechanic menus or valet services) causes a runtime error because ESX.Game.SetVehicleProperties expects a number rather than a table. This change ensures a seamless experience for servers and scripts using RGB color customization, preventing native call failures and improving script robustness.

---

Implementation Details

Checks if props.color1 or props.color2 is a table.

If so, it uses SetVehicleCustomPrimaryColour or SetVehicleCustomSecondaryColour respectively with the RGB values.

If not, it falls back to SetVehicleColours with default primary/secondary values to maintain backward compatibility.

---

Usage Example

-- Example using RGB table
props = {
color1 = {255, 0, 0}, -- Red (RGB)
color2 = {0, 0, 255}, -- Blue (RGB)
}

-- Example using GTA color index
props = {
color1 = 1, -- Graphite
color2 = 64, -- Blue
}

props.color1 and props.color2 can be either:

An RGB table, e.g. {255, 255, 255}

A GTA default color index, e.g. 1

This ensures full compatibility with both modern and legacy vehicle color formats.

PR Checklist

• My commit messages and PR title follow the Conventional Commits standard.
• My changes have been tested locally and function as expected.
• My PR does not introduce any breaking changes.
• I have provided a clear explanation of what my PR does, including the reasoning behind the changes and any relevant context.

[Zykem]

LGTM, Thanks!

[SophiaDLL]

Look's Good.

[Zykem]

esx-framework/esx-legacy-documentation@bc84ae3

Documentation update regarding your Pull Request.