JJM Modifications

Database

Setting up MySQL persistence for dynamically added blips.

JM-Blips uses oxmysql to store blips that were added at runtime via /addblip. Without the database, dynamically added blips are lost when the resource restarts.

Setup#

  1. Ensure oxmysql is installed and started before JM-Blips in your server.cfg.
  2. Run the SQL file included in the resource:

You can import this by pasting the contents of JM-Blips.sql into your database management tool (HeidiSQL, phpMyAdmin, etc.) or by running it via the MySQL CLI.

  1. Confirm the table exists before starting the resource.

How it works#

When an admin uses /addblip, the blip data is saved to the jm_blips table with a unique identifier. On resource start, all persisted blips are loaded and broadcast to connecting players alongside the blips defined in config.lua.

When an admin uses /removeblip, the matching record is deleted from the database so it does not reappear after a restart.

Note

Blips defined directly in config.lua are never stored in the database — they are always loaded from the file. Only blips added dynamically at runtime are persisted.