> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/gpcscripting/gpc-script-guide/gpc-developer-guide/constants/controller/led.md).

# LED

The below table outlines all of the LED which is defined, with value and what character they represent.

| **Name**   | **Description**                                                                      | **Value** |
| ---------- | ------------------------------------------------------------------------------------ | --------- |
| LED\_NONE  | set\_ledx identifier used to turn off all blinks                                     | -1        |
| LED\_1     | get/set\_led/x identifier for Player 1/Upper left quadrant                           | 0         |
| LED\_2     | get/set\_led/x identifier for Player 2/Upper right quadrant                          | 1         |
| LED\_3     | get/set\_led/x identifier for Player 3/Lower left quadrant                           | 2         |
| LED\_4     | get/set\_led/x identifier for Player 4/Lower right quadrant                          | 3         |
| PS4\_RED   | get\_ps4\_lbar identifier for the red color coming from the console                  | 1         |
| PS4\_GREEN | get\_ps4\_lbar identifier for the green color coming from the console                | 2         |
| PS4\_BLUE  | get\_ps4\_lbar identifier for the blue color coming from the console                 | 0         |
| DS4\_RED   | get\_ps4\_lbar identifier for the red color currently being sent to the controller   | 5         |
| DS4\_GREEN | get\_ps4\_lbar identifier for the green color currently being sent to the controller | 6         |
| DS4\_BLUE  | get\_ps4\_lbar identifier for the blue color currently being sent to the controller  | 4         |


---

# 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://guide.cronuszen.com/gpcscripting/gpc-script-guide/gpc-developer-guide/constants/controller/led.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.