# DXS Telegram V2

<figure><img src="/files/Rt3TKsTZJ7L9C1R3XnSZ" alt=""><figcaption></figcaption></figure>

## **Installation**

1: First download the script from you cfx keymaster.

2: Create the \[DXS\_Scripts] folder in your server resource.

3: Paste the DXS\_Telegram Folder in the \[DXS\_Scripts].

4: Run the Telegram.sql in your server Database.

5: Ensure \[DXS\_Scripts] in your server.cfg&#x20;

6: Restart your server and enjoy.

## **Dependency**&#x20;

1: Vorp\_core

2: Vorp\_Inventory

## Configuration

Edit config.lua :

* Config.debug — verbose logging.
* Config.locale — language key ( en , fr , nl , pt ).
* Config.keyToOpen — UI open key (default U ).
* Config.locations — mailbox coordinates for interaction and blips.
* Config.BlipName — map blip label.
* Config.TimeBetweenUsersRefresh — users cache refresh interval.
* Config.DelayBetweenTwoMessage — cooldown between sends (seconds).
* Config.MessageSendPrice — price to send a message.
* Config.ItemSendPrice — price to send items.

<figure><img src="/files/RqihWvYYRpRdwAG1vI7T" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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://dxs-scripts.gitbook.io/home/documentation/redm/dxs-telegram-v2.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.