Blip Manager
This is a step-by-step installation guide, configuration preview, and full explanation of all settings for legends_blips.
If you lack programming experience, ensure you read each step thoroughly without skipping, as all documentation is essential!
Before submitting a support ticket or following the guides in this documentation, please make sure that you are running the latest version of the resource.
What is legends_blips?
legends_blips is an advanced map blip management system that allows server owners to add custom blips through both configuration files and an in-game editor. It features three types of blips, ACE permission-based access control, and real-time editing capabilities.
Key Features
- In-Game Management - Create, edit, and delete blips directly in-game with an intuitive menu
- Three Blip Types:
- Normal Blips - Standard map markers that are always visible
- Area Blips - Blips with radius circles for marking zones/areas
- Closest Only Blips - Only shows the nearest blip from a category to reduce map clutter
- ACE Permission System - Secure command access using FiveM's built-in permissions
- JSON Configuration - Easy-to-edit JSON config file for manual setup
- Categorized Blips - Organize blips into logical categories
- Live Editing - Real-time blip management with instant map updates
- Performance-Friendly - Configurable cooldown to optimize closest blip updates
- Debug Mode - Toggle debug output for troubleshooting
Need help? Join our Discord (opens in a new tab) for support!
FAQ
How do I add a new blip category with its own color and icon set?
Open the in-game editor with /blipsmenu (requires add_ace group.admin command.blipsmenu allow) and click New Category. Set the category name, icon sprite id, color, and whether it should obey closest-only mode. Categories persist to disk through the built-in JSON storage so they survive restarts.
How do I add a blip programmatically from another resource?
Call exports.legends_blips:AddBlip({ coords, sprite, color, label, category }) from any server or client script. The function returns a unique id that you can later pass to RemoveBlip. This is useful for dynamic locations like job-specific waypoints or temporary event markers.
How does the "closest only" display work and can I disable it per category?
In closest-only mode the resource shows only the N nearest blips in a category (configurable), hiding the rest. Toggle the showClosestOnly flag per category in the in-game editor or in the JSON store. Categories without the flag always show every entry, useful for stores and landmarks.
Where are blips stored and how do I bulk-import from my existing framework?
Blips are persisted in data/blips.json as a flat array of objects. You can hand-edit the file when the resource is stopped, or paste an export from qb-core/blips.lua mapped to the legends_blips schema. Restart the resource or call exports.legends_blips:Reload() to pick up changes without a server restart.
Can I restrict certain blip categories to specific jobs only?
Yes. Each category supports a jobs array in the JSON store (e.g. jobs = {"police", "ambulance"}). Non-matching players simply do not see those blips. Useful for hidden stash points, officer-only POIs or job training yards.