> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-pausemenu/map-and-blip-names.md). # Map & Blip Names The Map screen opens GTA's own pause map under the menu, so streamed maps (postal maps, for example) show as they are. Its legend is replaced by the places panel: groups like GTA's legend, places of the same kind merged into one row (nearest first), the game's own blip icons, a route with Enter. ## Blip names No game function returns a blip's name, so the map reads the name GTA's own legend shows while the Map screen is open (`Config.Map.GameNames`). Names come in this order: what a script tells it, GTA's name, what the shim saw, the category name. * From your own scripts: `exports.daddy_pausemenu:SetBlipMeta(blip, { label = 'Fleeca', category = 'bank' })` and `ClearBlipMeta(blip)`. * For other Lua resources (banks, garages, shops): add `client_script '@daddy_pausemenu/shim/blipnames.lua'` as the **first** client script of their `fxmanifest.lua`, and again after updating them. Without it a blip shows its category name (Bank, Garage). ## Keys on the map While the map is up, Tab, Space, Left Shift and Left Ctrl (pad X, Y, LS, RS) belong to the places panel: GTA's own map actions on those keys do not run. Dragging and the mouse wheel move and zoom GTA's map. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-pausemenu/map-and-blip-names.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.