OMSolutions Documentation
ShopDiscord Server
  • Welcome
  • General
    • Downloading Resources
    • Installing Resources
  • Paid Resources
    • Emergency Lighting System
      • Configuring this resource
      • Adding Vehicles
    • Vehicle Boots
      • Configuring this resource
      • Loadout Types
    • Custody Bundle
      • Configuring this resource
  • OMSolutions Radio
    • Installing the Teamspeak Plugin
Powered by GitBook
On this page
  • Debugging & Version Checking
  • Framework
  • Weapon Blacklist
  • Integrations
  • Vehicle Boots
  • Custom Doors
  1. Paid Resources
  2. Vehicle Boots

Configuring this resource

We've made it as simple as possible to configure oVehicleBoots

Our config.lua file contains all customisable options to make your initial configuration of oVehicleBoots as simple as possible. Many of the values are accompanied by comment lines where needed but you can find the options below with details.

Debugging & Version Checking

These settings are useful to server owners and developers as they allow you to ensure your resource is the most up-to-date version of the script as well as toggle the debugging prints which will be useful to locate an error or where something is not going right.

If you are opening a ticket, the team will ask for your debugging logs.

Framework

We made oELS able to be integrated with FMS to ensure that you can secure certain items in the boots to certain skills as created on your FMS system. This prevents untrained members from using equipment they are not allowed to.

Weapon Blacklist

Want to make it so people can only use weapons defined in boots if they have collected them from the boot? Simply set this value to true and it will despawn the weapon from players if they attempt to spawn the weapon from vMenu.

Integrations

This resource is easily integrated with the oEssentials system allowing you to limit the system to only those who are onDuty with our resource providing an extra immersion to the roleplay preventing civilians from accessing the vehicle's boot.

Vehicle Boots

In this table, you need to add both the Spawn Code of the vehicle and which boot it will be using. Simply use the format provided below replacing SPAWNCODE with the Spawn Code of your vehicle and BOOTTYPE with the name of a boot loadout you have provided in your bootTypes.json file.

["SPAWNCODE"] = "BOOTTYPE",

Custom Doors

If your vehicle is configured so they can access the weapon safe or equipment from the rear doors rather than the boot, you can customise that right here by inserting a new entry into the table. Simply use the format provided below replacing SPAWNCODE with the Spawn Code of your vehicle and DOORINDEX with the index of the door you want to open (list provided below).

["SPAWNCODE"] = "DOORINDEX",

Door Index:

  • 0 - Drivers Side

  • 1 - Rear Passenger (Driver's Side)

  • 2 - Front Passenger

  • 3 - Rear Passenger (Passenger's Side)

  • 4 - Bonnet

  • 5 - Boot

PreviousVehicle BootsNextLoadout Types

Last updated 1 year ago