1. Home
  2. Docs
  3. Paid Resources
  4. oELS
  5. Configurating oELS

Configurating oELS

The main configuration file (Config.lua) is where you will find all options for oELS related to the default settings, soundpacks for custom sirens, and Patterns. Each setting group has its own section on this page as well as brief descriptions in the file.

Debugging & Version Checking

This section contains options relating to version checking your oELS version, to ensure that it is up to date to the newest version. Setting the value of Config.VersionCheck to TRUE will complete this check each time you restart the script.

Debugging is something that should only be activated when attempting to find any errors with your oELS setup. This can cause a reduced performance due to the amount of debugging which takes place, this should be FALSE when not in use.

Keybinds

As part of the update to Version 3.0.0 of oELS, we added the functionality to allow users to set their own keybinds. However, Server Owners may modify both the default keyboard and controller keybinds to suit their needs.

You can find the custom key bind codes at these URLs:

Soundpacks

In this section you can set the custom soundpacks used by oELS from your server-sided sirens script, by default we have included the basic WMServerSided Sirens one. You should remove the — before the line if you wish to use it.

PLEASE NOTE: Server-sided sirens are external to our oELS resource. We do not provide support for siren-related issues.

You are able to configure if you would like to use the small blips between siren changes by enabling and disabling Optilink. As well as this, you are able to configure which vehicles utilize the “999 Mode Activated” sound by inputting their spawn codes in “. You are required to use this punctuation as opposed to “” due to the way in which the script is configured.

Non-ELS

If your vehicles as Non-ELS but you would like them to still have oELS-controlled sirens, you simply input their spawn codes in “ to the table. You are required to use this punctuation as opposed to “” due to the way in which the script is configured.

WigWags

In this section you can enable and disable the use of WigWags in the script, simply set the value to TRUE to enable them and FALSE to disable them.

Custom Patterns

One of the simplest tasks within our ELS is creating custom patterns for your vehicles to use, at first this seems daunting due to the large number of numbers involved but once you understand it you are good to go at creating any pattern that you want for your vehicles.

When adding a pattern you should follow the format provided below.

["Pattern Name"] = {{{Extras Controlled}, Time in Miliseconds}},

To demonstrate we will be using extras 1,2,3 and 4 and would like them to flash with extra 1 and 2 together then stop and flash extra 3 and 4 together with a really small delay of 75 milliseconds. To give you an idea, 1 second in milliseconds is 1000.

["NewPattern"] = {{{1,2}, 75}, {{}, 75}, {{3,4}, 75}},

That is for our primary lights, we would then repeat the same process to make our Secondary and Warning patterns before setting the JSON file’s light pattern to the name of our new pattern.