FAQ

Here you’ll find a quick and easy guide to features, troubleshooting tips, and answers to common questions.

🗺️ Where Do I Customize the Configuration of My Police Map?

You can customize police map settings and points in the following location:
Inside this folder (rcore_police/data/maps), you'll find files for each supported map (e.g., mrpd.lua, sandy_pd.lua, etc.).
Open the file that matches your map and edit the points and settings as needed for your server.

Note: If your map isn’t specifically supported (no matching .lua file is found), the script will automatically use default-mrpd.lua as a fallback configuration.

Tip:

For unique or custom maps, use /preset_creator in-game to define new map. (requires: admin rights)

🚗 Where Do I Define Garage Vehicles and Weapon Shop Items for Officers?

All police garage vehicles and shop items are managed inside your config.lua file, under the JobGroups section.

🚙 Police Garage Vehicles

To add, remove, or edit available vehicles for each police job (like police or sheriff):

Open your config.lua.
Find the relevant job group (e.g., 'police' or 'sheriff').
Under VehiclesToGrade, update:
- storage: List all vehicles, their names, models, images, and prices.
- access: Set which job grade can access each vehicle.

Example:

VehiclesToGrade = {
    storage = {
        ['police3'] = { label = "Police Cruiser (A)", model = 'police3', price = 300 },
        ['polmav'] = { label = "Police Maverick", model = 'polmav', price = 300, isAir = true },
        -- more vehicles...
    },
    access = {
        [0] = { "police3", "polmav" },
        [3] = { "police4" },
        [5] = { "*" }, -- "*" means all vehicles for this grade
    }
}

🛒 Weapon/Equipment Shop

To set what items your officers can buy or take:

Open your config.lua.
In the same job group, look for the Store section.
Under storage, add or remove items (with their label and price).
Under access, set which items each job grade can access.

Example:

Store = {
    storage = {
        [Items.Spikes] = { label = "Spikes", price = 0 },
        ['WEAPON_NIGHTSTICK'] = { label = "Nightstick", price = 500 },
        ['radio'] = { label = "Radio", price = 250 },
        -- more items...
    },
    access = {
        [0] = { "WEAPON_NIGHTSTICK", "radio", Items.Spikes },
        [3] = { "weapon_carbinerifle" },
        [5] = { "*" },
    }
}

Note: All higher grades automatically inherit access to items and vehicles from lower grades—no need to define them again! 😊

🗃️ Having trouble opening your stashes or searching other players?

This usually happens if you’re using an unsupported inventory system, or if the inventory author has changed how their exports or events work.
Double-check for updates to your inventory, and feel free to reach out to the inventory author if you’re unsure.
If you’re running a modified or out-of-date inventory, support might not be available. For the best experience, always use the official, latest supported versions.

🤔 Escort Feature Not Working Properly? (Strange Behavior When Putting In/Out of Vehicle)

If you notice that escorting a player acts strangely, or you can't re-escort them after putting them in or out of a vehicle, here’s what to check:

Reason:

This usually happens if you’re running another third-party resource that interferes with player handling or police actions.
We use emulated functions from popular scripts like qb-police, qbx, or esx_policejob to maximize compatibility.
However, if you have another resource doing similar things (like custom escort, drag, or put-in-vehicle code), it can cause weird conflicts.

How to fix:

Disable any other third-party police or escort-related scripts to avoid conflicts.
Make sure you’re only running the police resource you intend to use.

Tip: If you need to use custom features from a third-party script, make sure they’re not conflicting with rcore_police’s built-in functionality.

🚓 Why can't a player be put in a vehicle without cuffs?

This is working as intended!
A player must be cuffed before they can be placed into a vehicle by police or staff.

Why? Requiring cuffs makes sure the player is properly handled while in the vehicle—so they can’t escape, exploit, or glitch out. It helps prevent unwanted situations where an uncuffed player could exit the car or interfere with the roleplay scenario.

If you want to move a player to a vehicle, make sure to cuff them first using the appropriate command or menu option.

If you can’t open your F2 job menu after being revived, try this:

Check your config:

Open your config.lua in rcore_police.

Find this section:

Flags = {
    SkipDeathCheck = false, -- This allows to skip death check (helpful when issue with accessing menu / not running supported death system)
},

Set SkipDeathCheck to true:
```
Flags = {
    SkipDeathCheck = true,
},
```

Save your changes and restart your server/resource.

Tip: Setting SkipDeathCheck to true tells rcore_police to ignore the "dead" state check—so the F2 menu will work, even if there’s a death state issue or your server uses a custom death system.

ℹ️ Why does this happen?

Many servers use custom revive or death systems (for example, a modified ambulance job or custom logic using player death metadata).
These scripts can handle the player's "dead" state in ways rcore_police doesn't recognize, especially if the framework's death metadata is customized.
As a result, rcore_police may still think a player is dead after they’re revived—blocking features like the F2 menu.

Important: Setting SkipDeathCheck to true makes rcore_police ignore the "dead" check so the F2 menu works with your custom death system. However: Some features (like "escort" or picking up a downed player) may not work correctly if rcore_police can’t reliably tell who’s dead or alive with your custom logic.
If your death system and framework metadata aren’t fully compatible, some advanced features may not behave as expected.

🗺️ How to Define a Non-Supported Map

Want to add your own map that isn’t officially supported yet? Here’s how:

Enter the game and open the chat.
Type the command: /preset_creator.
A short form will appear — fill it out and follow the on-screen instructions until you’re done.

Note:
This command is not for customizing existing maps—adjust those manually if needed.
You must have admin rights to use this command.

PreviousInventory NextDeployer

Last updated 21 days ago

Was this helpful?