# /hotbutton

## Syntax

**/hotbutton \[ Name ] \[ color# ] \[ Line#:Cursor#:/YourCommand YourText ]**

## Description

Extends the built in /hotbutton command with multiple lines support

## Examples

|                                    |                                                                                                        |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Example**                        | **Description**                                                                                        |
| /hotbutton TheName 14 1:0:/echo hi | Where 14 1:0: in this case means use color 14, then place /echo hi on LINE 1 and NO Cursor Attachment. |
| /hotbutton TheName 14 1:/echo hi   | Where 14 1: in this case means use color 14, then place /echo hi on LINE 1.                            |
| /hotbutton TheName 1:0:/echo hi    | Where 1:0: in this case means place /echo hi on LINE 1 and NO Cursor Attachment.                       |
| /hotbutton TheName 1:/echo hi      | Where 1: in this case means place /echo hi on LINE 1.                                                  |
| /hotbutton TheName 0:/echo hi      | Where 0: in this case means NO Cursor Attachment.                                                      |
| /hotbutton TheName 14 /echo hi     | just calls the eq function like before.                                                                |
| /hotbutton TheName /echo hi        | just calls the eq function like before.                                                                |


---

# 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://macroquest.gitbook.io/macroquest/commands/slash-commands/hotbutton.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.