Follow these steps to get JM-Blips running on your server.
Prerequisites#
- A FiveM server (Windows or Linux).
oxmysqlinstalled and running (required for persistent blips).- Framework resource (
qb-coreorqbox) if you are not running standalone.
Steps#
- Download the resource from your CFX Portal granted assets.
- Extract the folder and place it inside your server's
resourcesdirectory. Do not rename the folder — keep it asJM-Blips. - Add the following line to your
server.cfg:
ensure JM-Blips- Open
config.luaand setConfig.Frameworkto match your setup:
Config.Framework = "standalone" -- "standalone", "qbcore", or "qbox"- In
fxmanifest.lua, comment or uncomment the dependency that matches your framework:
dependencies { 'qb-core', -- comment this out if using QBox or standalone -- 'qbox' -- uncomment this if using QBox 'oxmysql'}- Import the database table by running the contents of
JM-Blips.sqlon your server's MySQL database. This creates the table used for persistent dynamic blips. - Save all files and restart your server, or use the console commands:
refreshensure JM-BlipsVerifying the installation#
Once the resource starts you should see a line similar to the following in the server console:
Started resource JM-BlipsJoin the server and open the map. Your configured blips should appear at the coordinates defined in config.lua.
Warning
If you see a Failed to verify protected resource error, check that the resource folder is named exactly JM-Blips. Renaming the folder breaks the escrow verification.
Duplicate blips#
If a blip appears twice on your map, another installed resource is likely creating the same blip. Set enabled = false for that blip in the other resource's config — do not disable it in both places or it will not appear at all.