#BlipMaker — Help & Troubleshooting

This page covers everything from installing BlipMaker to fixing the most common "why isn't this working" issues. Jump to what you need:

• For Players — how to view blips, and what "view-only" means
• For Server Owners — installation, database setup, configuration, and fixing errors
• FAQ
• Still Stuck?

#For Players

#How to open the panel

Press F7 or type /blipmenu in chat. Everyone can open the panel and see the current list of blips.

#"I can't add or delete blips"

Adding and deleting is restricted to server admins. If you're not an admin, you'll see a "view-only access" note in the Add tab, and the Delete buttons will be greyed out — that's expected, not a bug. Ask a server admin if you think you should have access.

#"I clicked Add Blip and nothing happened"

If you're not an admin, the button is disabled on purpose (see above). If you are an admin and it's still not working, see the server owner troubleshooting below — it's likely a database issue on the server's end, not something on your end.

#"The panel opened but F7 usually does something else for me"

Some servers use F7 for another script's menu, or you may have rebound it yourself. Check Settings > Key Bindings > FiveM for a conflict, or just use /blipmenu instead.

#For Server Owners

#Requirements

• A FiveM server (FXServer / Cfx.re).
• Either oxmysql or mysql-async — whichever one you already run is detected automatically, you don't need both.
• A MySQL/MariaDB database.

Unlike CES_WashCar and CES_GunSafty, this one is not a no-dependency standalone script — it needs a database.

#Installation

1. Extract the whole blipmaker folder into your server's resources directory.
2. Run the SQL in map_blips.sql against your database to create the map_blips table.
3. In server.cfg, make sure your database resource starts before this one:
   Copy

   ensure oxmysql
   ensure blipmaker

   (or ensure mysql-async instead of oxmysql, whichever you use)

4. Edit config.lua to add the identifiers of players who should be able to add/delete blips — it's empty by default, so only the server console has that access until you add some.
5. Restart the resource (or the server).

#Configuration (config.lua)

#Adding an admin identifier

1. Have the player join your server once.
2. Check your server console for their connection log, or use a debug command to print GetPlayerIdentifiers for their player ID — you're looking for something like steam:1100001abcde123 or license:abcdef....
3. Add that exact string to Config.AdminIdentifiers in config.lua.
4. Restart the resource.

#Troubleshooting

Resource won't start / "resource mysql-async not found" or similar in the console

• Make sure you actually have oxmysql or mysql-async installed and started, and that it's listed before ensure blipmaker in server.cfg.
• Check the console for a line like [blipmaker] Using oxmysql for blip storage. on startup — if you instead see Neither oxmysql nor mysql-async is running, your database resource either isn't installed, isn't started, or is starting after this one.

Adding a blip does nothing / players get "The database isn't available right now"

• This means the database resource wasn't detected when blipmaker started. Check your server.cfg order (database resource must ensure before blipmaker), and check the console for startup errors from oxmysql/mysql-async itself (bad database credentials, database not reachable, etc.).

A blip's name got cut off

• Blip names are capped at 50 characters to match the database column — this is expected, not a bug.

Admin can't add/delete blips

• Double check the identifier in Config.AdminIdentifiers exactly matches that player's identifier (prefix and all — steam:..., license:..., etc. are not interchangeable). You can see a player's identifiers in the server console when they connect.
• Restart the resource after editing config.lua — changes don't apply until it restarts.

Blips don't persist after a restart

• Confirm the map_blips table actually exists in your database (re-run the SQL in map_blips.sql if you're not sure) and that your database resource is pointed at the same database every time (check its own connection string config).

The panel doesn't appear at all

• Verify html/index.html, html/style.css, and html/script.js all exist under the resource folder.
• Check for a conflicting resource also bound to F7 — try /blipmenu instead to rule that out.

#FAQ

Do I need both oxmysql and mysql-async?
No — just one. Whichever is running on your server is used automatically.

Can regular players add or delete blips?
Not by default. Only identifiers listed in Config.AdminIdentifiers (or the server console) can — everyone else has view-only access to the panel.

Do blips survive a server restart?
Yes — they're stored in your database, not in memory.

Can I add my own custom blip sprites or colors to the dropdown?
Yes — edit the <option> lists in html/index.html. GTA V's sprite and color IDs are documented in several community reference lists online.

#Still Stuck?

If none of the above solves it, reach out through the Discord link in the site header — that's the fastest way to get help.