Skip to content

Commit

Permalink
Spelling
Browse files Browse the repository at this point in the history
  • Loading branch information
loaf-scripts authored Nov 7, 2021
1 parent 9add416 commit 032adca
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,4 +12,4 @@ YouTube Showcase: https://www.youtube.com/watch?v=D3UtNxFXnpU
The script works without ESX and with ESX. (please note that you should remove the spikestrip part from your esx_policejob if you intend on using this resource).
If you only want certain jobs to be able to use spikestrips but you don't have ESX, set `Config.JobBased.Enabled` to true, [line 3 in the config.lua](https://github.com/loaf-scripts/loaf_spikestrips/blob/main/config.lua#L3). You can edit who is able to use the script at the server.lua, simply add an identifier (any identifier works) to the `police` table in the [server/main.lua](https://github.com/loaf-scripts/loaf_spikestrips/blob/main/server/main.lua#L1) file.

If you only want certain jobs to be able to use spikestrips and you use ESX, set `Config.JobBased.Enabled` to ture [line 3 in the config.lua](https://github.com/loaf-scripts/loaf_spikestrips/blob/main/config.lua#L3) and also set `Config.JobBased.ESX` to true [line 4 in the config.lua](https://github.com/loaf-scripts/loaf_spikestrips/blob/main/config.lua#L4). You can configure what jobs are able to use spikestrips by editing the `PoliceJobs` table in the config.
If you only want certain jobs to be able to use spikestrips and you use ESX, set `Config.JobBased.Enabled` to true [line 3 in the config.lua](https://github.com/loaf-scripts/loaf_spikestrips/blob/main/config.lua#L3) and also set `Config.JobBased.ESX` to true [line 4 in the config.lua](https://github.com/loaf-scripts/loaf_spikestrips/blob/main/config.lua#L4). You can configure what jobs are able to use spikestrips by editing the `PoliceJobs` table in the config.

0 comments on commit 032adca

Please sign in to comment.