Built for

A minimap that drops into a QBCore server

QBCore servers already run a long resource list, and the last thing a map should do is add another thing that can break on restart. Every map in this shop is a stream-only resource: it replaces the twelve texture dictionaries the base game already loads and sets the radar zoom levels, and that is the whole of it. qb-core, qb-hud, qb-inventory and everything else keep working exactly as before.

Our picks

What we would run on this kind of server

Three concrete recommendations rather than a shrug — with the reason attached.

Black OBSIDIAN FiveM minimap for GTA V — without postal codes — showing Los Santos street detailBlack OBSIDIAN FiveM minimap for GTA V — without postal codes — showing the whole San Andreas map No postals
BlackOBSIDIAN

Neutral under the blue and green qb-hud accents.

6144 × 9216 px · 78 files · without postal codes
$8.00+ $1 / elementView
Blue COBALT FiveM minimap for GTA V — with postal codes — showing Los Santos street detailBlue COBALT FiveM minimap for GTA V — with postal codes — showing the whole San Andreas map Postal codes
BlueCOBALT

Matches the default QBCore palette without shouting.

6144 × 9216 px · 78 files · with postal codes
$8.00+ $1 / elementView
Mixed dark TOPO NIGHT FiveM minimap for GTA V — google style — showing Los Santos street detailMixed dark TOPO NIGHT FiveM minimap for GTA V — google style — showing the whole San Andreas map Google style
Mixed darkTOPO NIGHT

For servers that have rebuilt the HUD and want the map to match.

6144 × 9216 px · 78 files · google style
$8.00+ $1 / elementView

Where it goes in a QBCore server

Drop the folder into [standalone] or any resources subfolder and add it to server.cfg. Load order does not matter against qb-core because there is nothing to depend on — the resource has no server file, no shared file and no exports.

The only client code in the download sets the radar zoom levels so the new textures line up with the game world. It runs once, on resource start, and then does nothing for the rest of the session.

  • ensure pityus_minimap_<theme> in server.cfg
  • No entry needed in qb-core/shared
  • No changes to qb-hud, qb-radialmenu or qb-inventory
  • Restart the resource alone — a full server restart is not required

It does not fight qb-hud

qb-hud draws the radar frame, the compass and the status rings; the map is what shows through underneath. Because the two never touch the same file, changing the map never breaks the HUD and updating the HUD never breaks the map.

If your HUD already carries strong colour, the monochrome and grey palettes stay out of the way. If the HUD is deliberately plain, the colour themes are what people notice first.

Postal codes on a QBCore server

A lot of QBCore servers run a postal resource that draws codes as text on the map. If yours does, take the no postals base map so the two do not print numbers on top of each other. If you do not run one, the postal codes base map bakes the grid straight into the texture and you need no extra resource at all.

Questions

Does it need qb-core to be running?
No. The resource is framework-agnostic — it works on QBCore, QBox, ESX, vRP and standalone servers without a single line of configuration.
Will it survive a QBCore update?
Yes. It reads nothing from the framework, so a qb-core update cannot break it.
Can I put my server name on it?
Yes — the browser studio bakes text and logos into the texture itself for $1.00 per element, so it shows up on the radar with no extra resource running.

Not sure yet?

Open the live preview and look at any street on any theme before you spend a cent.