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

# Newily Notify

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

{% embed url="<https://newilyscripts.tebex.io/package/7351404>" %}

#### Features

* **Standalone** — No framework dependency, works with any resource
* **3 Notification Types** — `info`, `success` and `error` with distinct icons and colors
* **Progress Bar** — Left accent bar that drains over the notification duration
* **Configurable** — Set default position and duration in `shared/config.lua`
* **9 Positions** — Top, middle or bottom × left, center or right
* **Client Export** — Trigger notifications from any client-side script
* **Server Export** — Trigger notifications on a specific player from any server-side script
* **Framework Ready** — Drop-in integration guides for ESX and QBCore included


---

# 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, and the optional `goal` query parameter:

```
GET https://newily-scripts.gitbook.io/newily-scripts-docs/documentation/scripts/newily-notify.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.