EN 
DE 
FR 
PT 
Sandy Shores M.C. Clubhouse (V2)
Ursprünglicher Preis war: $82.99$32.99Aktueller Preis ist: $32.99.
Premium MultiJob
Ursprünglicher Preis war: $40.99$20.99Aktueller Preis ist: $20.99.
-45%
(ESX/QB) Advanced Police Job
Ursprünglicher Preis war: $82.99$45.99Aktueller Preis ist: $45.99.
Features
- Optimized with 0.00ms idle
- Multiple LEO departments(No need for separate scripts for separate police jobs)
- Full handcuff props and animations
- Escorting animation
- Keybinds for arrest(Configurable)
- Resisting arrest via skill-check
- Compatible with ox_inventory, qb-inventory, qs-inventory, and mf_inventory(Code open to incorporate a different inventory)
- Tackling(Configurable)
- Job Menu (Configurable)
- Fine players(Compatible with QBCore, okokBilling and esx billing OR any billing can be added to open code)
- Boss menu(Compatible with wasabi_multijob, qb-management and esx_society)
- Cloakroom(Compatible with esx_skin and my fork of fivem-appearance OR any skin script can be added to open code)
- Optional target(By default compatible with qtarget/qb-target/ox_target)
- Armory(Configurable by job grade)
- Garage for land & air(Configurable by job grade)
- Vehicle interaction menu added to job menu which includes vehicle ownership information, lockpicking vehicle, and impounding vehicle (New As of 1.0.5)
- Ability to incorporate jail script(See docs)
- Ability to view suspect’s identification
- Ability to view and revoke licenses
- Most if not all of the pre-existing esx_policejob features
- EXTREMELY configurable
- Full replacement for any script that depends on esx_policejob
- And more!
Frequent updates / feature additions planned so stay tuned!
$ USD
-
Instant Download
-
Satisfaction Guarantee
-
100% Open Source
Beschreibung
Config.Lua
local seconds, minutes = 1000, 60000
Config = {}
Config.jobMenu = 'F6' -- Default job menu key
Config.customCarlock = false -- If you use wasabi_carlock(Add your own carlock system in client/cl_customize.lua)
Config.billingSystem = false -- Current options: 'esx' (For esx_billing) / 'okok' (For okokBilling) (Easy to add more/fully customize in client/cl_customize.lua)
Config.skinScript = false -- Current options: 'esx' (For esx_skin) / 'appearance' (For wasabi-fivem-appearance) (Custom can be added in client/cl_customize.lua)
Config.customJail = false -- Set to true if you want to add jail option to menu(Requires you to edit wasabi_police:sendToJail event in client/cl_customize.lua)
Config.inventory = 'ox' -- NEEDED FOR SEARCHING PLAYERS - Current options: 'ox' (For ox_inventory) / 'mf' (For mf inventory) / 'qs' (For qs_inventory) / 'custom' (Custom can be added in client/cl_customize.lua)
Config.searchPlayers = true -- Allow police jobs to search players (Must set correct inventory above)
Config.weaponsAsItems = false -- This is typically for older ESX and inventories that still use weapons as weapons and not items(If you're unsure leave as true!)
Config.esxIdentity = true -- Enable to gain option additional information when checking ID of suspect. (Requires esx_identity or similar)
Config.esxLicense = true -- Enable if you use esx_license or something similar for weapon licenses/etc
Config.tackle = {
enabled = true, -- Enable tackle?
policeOnly = true, -- Police jobs only use tackle?
hotkey = 'G' -- What key to press while sprinting to start tackle of target
}
Config.handcuff = { -- Config in regards to cuffing
timer = 20 * minutes, -- Time before player is automatically unrestrained(Set to false if not desired)
hotkey = 'J', -- What key to press to handcuff people(Set to false for no hotkey)
skilledEscape = {
enabled = true, -- Allow criminal to simulate resisting by giving them a chance to break free from cuffs via skill check
difficulty = {'easy', 'easy', 'easy'} -- Options: 'easy' / 'medium' / 'hard' (Can be stringed along as they are in config)
}
}
Config.policeJobs = { -- Police jobs
'police',
'sheriff'
}
Config.Locations = {
LSPD = {
blip = {
enabled = true,
coords = vec3(464.57, -992.0, 30.69),
sprite = 60,
color = 29,
scale = 1.0,
string = 'Mission Row PD'
},
bossMenu = {
enabled = true, -- Enable boss menu?
jobLock = 'police', -- Lock to specific police job? Set to false if not desired
coords = vec3(460.64, -985.64, 30.73), -- Location of boss menu (If not using target)
label = '[E] - Access Boss Menu', -- Text UI label string (If not using target)
distance = 3.0, -- Distance to allow access/prompt with text UI (If not using target)
target = {
enabled = false, -- If enabled, the location and distance above will be obsolete
label = 'Access Boss Menu',
coords = vec3(460.64, -985.64, 30.73),
heading = 269.85,
width = 2.0,
length = 1.0,
minZ = 30.73-0.9,
maxZ = 30.73+0.9
}
},
armoury = {
enabled = true, -- Set to false if you don't want to use
coords = vec3(480.32, -996.67, 30.69-0.9), -- Coords of armoury
heading = 86.95, -- Heading of armoury NPC
ped = 's_f_y_cop_01',
label = '[E] - Access Armoury', -- String of text ui
jobLock = 'police', -- Allow only one of Config.policeJob listings / Set to false if allow all Config.policeJobs
weapons = {
[0] = { -- Grade number will be the name of each table(this would be grade 0)
['WEAPON_PISTOL'] = { label = 'Pistol', multiple = false, price = 75 }, -- Set price to false if undesired
['WEAPON_NIGHTSTICK'] = { label = 'Night Stick', multiple = false, price = 50 },
-- ['ammo-9'] = { label = '9mm Ammo', multiple = true, price = 10 }, -- Set multiple to true if you want ability to purchase more than one at a time
-- ['armour'] = { label = 'Bulletproof Vest', multiple = false, price = 100 }, -- Example
},
[1] = { -- This would be grade 1
['WEAPON_COMBATPISTOL'] = { label = 'Combat Pistol', multiple = false, price = 150 },
['WEAPON_NIGHTSTICK'] = { label = 'Night Stick', multiple = false, price = 50 },
-- ['ammo-9'] = { label = '9mm Ammo', multiple = true, price = 10 }, -- Example
-- ['armour'] = { label = 'Bulletproof Vest', multiple = false, price = 100 }, -- Example
},
[2] = { -- This would be grade 2
['WEAPON_COMBATPISTOL'] = { label = 'Combat Pistol', multiple = false, price = 150 },
['WEAPON_NIGHTSTICK'] = { label = 'Night Stick', multiple = false, price = 50 },
['WEAPON_ASSAULTRIFLE'] = { label = 'Assault Rifle', multiple = false, price = 1100 },
-- ['ammo-9'] = { label = '9mm Ammo', multiple = true, price = 10 }, -- Example
-- ['ammo-rifle'] = { label = '5.56 Ammo', multiple = true, price = 20 }, -- Example
-- ['armour'] = { label = 'Bulletproof Vest', multiple = false, price = 100 }, -- Example
},
[3] = { -- This would be grade 3
['WEAPON_COMBATPISTOL'] = { label = 'Combat Pistol', multiple = false, price = 150 },
['WEAPON_NIGHTSTICK'] = { label = 'Night Stick', multiple = false, price = 50 },
['WEAPON_ASSAULTRIFLE'] = { label = 'Assault Rifle', multiple = false, price = 1100 },
-- ['ammo-9'] = { label = '9mm Ammo', multiple = true, price = 10 }, -- Example
-- ['ammo-rifle'] = { label = '5.56 Ammo', multiple = true, price = 20 }, -- Example
-- ['armour'] = { label = 'Bulletproof Vest', multiple = false, price = 100 }, -- Example
},
}
},
cloakroom = {
enabled = true, -- Set to false if you don't want to use (Compatible with esx_skin & wasabi fivem-appearance fork)
coords = vec3(462.36, -999.62, 30.69), -- Coords of cloakroom
label = '[E] - Change Clothes', -- String of text ui of cloakroom
range = 2.0, -- Range away from coords you can use.
uniforms = { -- Uniform choices
['Recruit'] = { -- Name of outfit that will display in menu
male = { -- Male variation
['tshirt_1'] = 15, ['tshirt_2'] = 0,
['torso_1'] = 5, ['torso_2'] = 2,
['arms'] = 5,
['pants_1'] = 6, ['pants_2'] = 1,
['shoes_1'] = 16, ['shoes_2'] = 7,
['helmet_1'] = 44, ['helmet_2'] = 7,
},
female = { -- Female variation
['tshirt_1'] = 15, ['tshirt_2'] = 0,
['torso_1'] = 4, ['torso_2'] = 14,
['arms'] = 4,
['pants_1'] = 25, ['pants_2'] = 1,
['shoes_1'] = 16, ['shoes_2'] = 4,
}
},
['Patrol'] = {
male = {
['tshirt_1'] = 58, ['tshirt_2'] = 0,
['torso_1'] = 55, ['torso_2'] = 0,
['arms'] = 30,
['pants_1'] = 24, ['pants_2'] = 0,
['shoes_1'] = 10, ['shoes_2'] = 0,
['helmet_1'] = 46, ['helmet_2'] = 0,
},
female = {
['tshirt_1'] = 15, ['tshirt_2'] = 0,
['torso_1'] = 4, ['torso_2'] = 14,
['arms'] = 4,
['pants_1'] = 25, ['pants_2'] = 1,
['shoes_1'] = 16, ['shoes_2'] = 4,
}
},
['Chief'] = {
male = {
['tshirt_1'] = 15, ['tshirt_2'] = 0,
['torso_1'] = 5, ['torso_2'] = 2,
['arms'] = 5,
['pants_1'] = 6, ['pants_2'] = 1,
['shoes_1'] = 16, ['shoes_2'] = 7,
['helmet_1'] = 44, ['helmet_2'] = 7,
},
female = {
['tshirt_1'] = 15, ['tshirt_2'] = 0,
['torso_1'] = 4, ['torso_2'] = 14,
['arms'] = 4,
['pants_1'] = 25, ['pants_2'] = 1,
['shoes_1'] = 16, ['shoes_2'] = 4,
}
},
}
},
vehicles = { -- Vehicle Garage
enabled = true, -- Enable? False if you have you're own way for medics to obtain vehicles.
jobLock = 'police', -- Job lock? or access to all police jobs by using false
zone = {
coords = vec3(463.69, -1019.72, 28.1), -- Area to prompt vehicle garage
range = 5.5, -- Range it will prompt from coords above
label = '[E] - Access Garage',
return_label = '[E] - Return Vehicle'
},
spawn = {
land = {
coords = vec3(449.37, -1025.46, 28.59), -- Coords of where land vehicle spawn/return
heading = 3.68
},
air = {
coords = vec3(449.29, -981.76, 43.69), -- Coords of where air vehicles spawn/return
heading = 0.01
}
},
options = {
[0] = { -- Job grade as table name
['police'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Police Cruiser',
category = 'land', -- Options are 'land' and 'air'
},
['police2'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Police Cruiser #2',
category = 'land', -- Options are 'land' and 'air'
},
['polmav'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Maverick',
category = 'air', -- Options are 'land' and 'air'
},
},
[1] = { -- Job grade as table name
['police'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Police Cruiser',
category = 'land', -- Options are 'land' and 'air'
},
['police2'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Police Cruiser #2',
category = 'land', -- Options are 'land' and 'air'
},
['polmav'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Maverick',
category = 'air', -- Options are 'land' and 'air'
},
},
[2] = { -- Job grade as table name
['police'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Police Cruiser',
category = 'land', -- Options are 'land' and 'air'
},
['police2'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Police Cruiser #2',
category = 'land', -- Options are 'land' and 'air'
},
['polmav'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Maverick',
category = 'air', -- Options are 'land' and 'air'
},
},
[3] = { -- Job grade as table name
['police'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Police Cruiser',
category = 'land', -- Options are 'land' and 'air'
},
['police2'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Police Cruiser #2',
category = 'land', -- Options are 'land' and 'air'
},
['polmav'] = { -- Car/Helicopter/Vehicle Spawn Code/Model Name
label = 'Maverick',
category = 'air', -- Options are 'land' and 'air'
},
},
}
}
},
}
Reviews (0)
Only logged in customers who have purchased this product may leave a review.
How to install
How to install resources
Installing mods on FiveM allows you to customize your server with unique assets, scripts, MLOs, and other enhancements. Here's a clear, detailed guide on how to install mods to your FiveM server.
Step 1: Download the Desired Mod
Find a Mod: Start by browsing through websites that offer FiveM mods, such as fivem-mods.net, GTA5-Mods.com, or community-based forums and Discord servers. You can also download mods from repositories like GitHub or from script developers' personal websites.
Check Compatibility: Ensure that the mod you're downloading is compatible with the version of FiveM you're running (especially if you're using specific frameworks like QBCore or ESX).
Download Files: Download the mod files, usually compressed in a
.zipor.rarfile format. These files will contain the necessary resources for installation.
Step 2: Prepare Your Server
Access Your Server Files: Log into your FiveM server’s file manager. This can be done either through an FTP client like FileZilla or through the control panel provided by your hosting provider.
Create a Backup: Before making any changes, it's essential to back up your server files. This ensures you can restore your server in case something goes wrong.
Locate the Resources Folder: Once inside your server files, locate the resources folder. This is where all mods and scripts are installed.
Step 3: Install the Mod
Extract the Files: If the mod is in a compressed file, extract the contents to a folder on your local computer.
Upload the Mod Files:
- Use your FTP client or file manager to upload the extracted folder into the resources folder of your server.
- Ensure the folder name is descriptive, as you will reference it in the server configuration.
Configure the Server to Load the Mod:
- Open your server’s server.cfg file (found in the main directory of your server).
- Add a line to ensure the server loads the mod. Typically, this will be in the form of:
- For example, if you added a mod called
my_car_mod, you would add:
Step 4: Set Up Dependencies (If Any)
Some mods may have dependencies, such as specific libraries, frameworks, or resources that need to be installed separately. Always check the mod’s documentation for any such requirements.
Install Dependencies: If the mod requires any additional resources, download and install them in the same resources folder, following the same process outlined in Step 3.
Load Dependencies: Add any necessary dependencies to your
server.cfgfile just as you did for the main mod.
Step 5: Restart the Server
- Restart the Server: Once the mod and its dependencies have been uploaded and configured, restart your server.
- You can either use the Restart button in your control panel or manually restart it through an FTP client or terminal command.
- Check the Console: After the restart, monitor the server console for any error messages. If you see any issues related to the mod, check the mod’s documentation or troubleshoot based on the error message.
Step 6: Test the Mod In-Game
Join Your Server: Open FiveM and connect to your server to test the mod.
Check for Issues: Test whether the mod functions as expected. Ensure that the new features, vehicles, or scripts are loading properly.
Step 7: Troubleshoot (If Necessary)
If the mod isn't working as expected, you may need to troubleshoot:
- Check File Paths: Ensure all files are in the correct folders and paths.
- Review Logs: Look at the server logs for any errors or conflicts.
- Update Dependencies: Ensure any required dependencies are correctly installed and up to date.
- Mod Compatibility: Verify that the mod is compatible with the version of FiveM and other mods you’re using.
Final Thoughts
Installing mods on your FiveM server is a great way to enhance gameplay, offer unique content to players, and make your server stand out. Always remember to back up your server before making any changes, and be mindful of mod compatibility to prevent conflicts.
By following the steps outlined above, you can easily install and manage mods to enrich your FiveM server experience.
Mods that will extend Roleplay
- Money-Back Guarantee: If you're not satisfied, we've got you covered with a no-questions-asked refund policy.
- Exclusive Content: Our mods and scripts are professionally crafted and exclusive to our platform.
- Trusted by the Community: Join thousands of FiveM server owners who rely on us for quality resources.
- High-Quality Design: Built with optimized coding practices for top-tier performance.
- Seamless Integration: Easily install and run on any FiveM server without compatibility issues.
- Customizable Options: Adjust settings and features to fit your server's unique style.
- Optimized Performance: Tested to ensure minimal resource usage and maximum efficiency.
- Lifetime Updates: Stay ahead with ongoing updates and improvements included at no extra cost.
Reviews
There are no reviews yet.