> For the complete documentation index, see [llms.txt](https://legacydmc.gitbook.io/chaser/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacydmc.gitbook.io/chaser/user-interface/nui-events.md).
# NUI Events
Chaser has a couple of NUI events when the default hud is enabled, they’ll will always be send as “action” and follow as:
## “hide”
Hides the default ui
## “update”
The action that updates the hud main data, has the following keys:
* currentrpm - Engine speed in RPM
* currentspeed - Current speed, either in kmh or mph depending on chaserconfig.lua
* tcs - Traction control state, will be set to true when tcs is being used (different from active)
* ecs - Stability control state, will be set to true when ecs is being used (different from active)
* lc - Launch control state, returns a string of either “on” “off” or “active”
* atlockstatus - Returns true when AT gear lock is active.
* nitrous - Returns the nitrous capacity, in normal % (instead of 0.5, will be 50%)
* currentdriftscore - Returns the current drift score.
* currentdriftmultiplier - Returns the current drift score multiplier.
## “startspeedo”
The action that starts the speedometer, has the following keys:
* maxrpm- The vehicle max rpm
## “showassist”
The action that shows when a assist is active on the speedometer, has the following keys:
* assist - The assists to show, either “tcs” or “esc”
## “hideassist”
The action that hides when a assist is disabled on the speedometer, has the following keys:
* assist - The assists to show, either “tcs” or “esc”
## “update”
The action that updates the hud main data, has the following keys:
* currentgear- The vehicle current gear
* transmissiontype - The vehicle transmission type in id 0 = Sequential 1 = AT 2 = Manual w/ clutch 3= EV
* speedtype - The unit the speedo is in, depending on chaserconfig.lua either kmh or mph
---
# 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://legacydmc.gitbook.io/chaser/user-interface/nui-events.md?ask=&goal=
```
`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.