> For the complete documentation index, see [llms.txt](https://yourmaps.gitbook.io/yourmaps-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yourmaps.gitbook.io/yourmaps-docs/yourtools/yourmaps-coords-tool.md).

# YourMAPS Coords Tool

**YourMAPS Coords Tool** is a practical in-game coordinate tool for RedM, made for mappers, developers, and server staff.

It helps you quickly get player coordinates, target information, model hashes, door data, headings, rotations, and ready-to-copy formats directly inside the game.

No framework is required.\
No database is required.\
Just install, configure, and use.

### What You Can Do

With YourMAPS Coords Tool, you can:

* View player coordinates in-game
* Copy coordinates in multiple formats
* Use `vector3`, `vec3`, `vector4`, XYZ, heading, and more
* Aim at objects, props, doors, or entities to get useful data
* Get model name, model hash, entity type, position, and rotation
* Check door information when available
* Use a clean draggable NUI panel
* Copy data with one click
* Use Eye Crosshair or Spot 3D Line mode
* Enable optional admin tools
* Use optional noclip and teleport commands
* Control access with ACE permissions
* Use optional Discord webhooks for admin actions

### Perfect For

This tool is useful for:

* RedM server owners
* Map creators
* MLO developers
* Script developers
* Staff teams
* Testing props, doors, interiors, and map positions
* Getting coordinates faster while working in-game

### Why Use It?

This tool saves time when working with maps, scripts, props, doors, interiors, and custom locations.

Instead of manually typing commands or using external tools, you can open one panel, aim at what you need, copy the information, and keep working.

It is simple, clean, and made for real development work inside RedM.

### Installation

1. Unzip the folder into your server `resources` folder.
2. Add the resource to your `server.cfg`.
3. Configure permissions and options in `config.lua`.
4. Use the in-game command to open the panel.

This resource is protected by escrow.

### Important

* This resource is made for RedM.
* It does not require VORP, QBCore, or any other framework.
* Admin features such as noclip and teleport are optional.
* Admin features can be controlled through ACE permissions or allowlist.
* Discord webhooks are optional and can be used for admin action logs.

### Support

* Questions or doubts: join the YourMAPS Discord.
* For personalized exterior/interior textures, custom buildings, or custom props: open a ticket on Discord.

### Update Notice

This resource has received an update.

The current HTML / NUI interface is newer and more updated than the version shown in the video preview.

The video is still useful to understand the main purpose of the tool, but the latest version has an updated interface similar to the current product images.

### Disclaimer

YourMAPS Coords Tool is designed to help you work faster, copy cleaner data, and manage mapping or development tasks directly inside your RedM server.

If you encounter any issue, please first check your configuration, permissions, and server console.

If the problem remains after testing, open a support ticket on Discord and we will assist you.

### Shop Link

You can purchase **YourMAPS Coords Tool** here:

[Buy YourMAPS Coords Tool](https://yourmaps.tebex.io/package/6579341)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://yourmaps.gitbook.io/yourmaps-docs/yourtools/yourmaps-coords-tool.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.