> For the complete documentation index, see [llms.txt](https://xcs-plugin.gitbook.io/cursorcs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xcs-plugin.gitbook.io/cursorcs/guides/menu-aliases.md).

# menu aliases

Menu aliases let players open a menu with a short command.

Instead of typing:

```bash
/cursor start shop_menu
```

they can type:

```bash
/shop
```

## Why aliases are useful

Aliases are useful for:

* shops
* profile menus
* class selectors
* language menus
* quick-access buttons

## Activable group example

If you have an activable menu in `config/holograms/`:

```yaml
group: "shop_menu"
alias: "shop"

title:
  text: "Shop"
```

Players can use:

* `/shop`
* `/cursor start shop`

## Normal group example

If you are using a normal group file:

```yaml
shop_menu:
  alias: "shop"

  title:
    text: "Shop"
```

Players can use:

* `/shop`
* `/cursor start shop`

## Good alias names

Good aliases are:

* short
* easy to remember
* one word if possible

Examples:

* `shop`
* `classes`
* `profile`
* `language`
* `settings`

## Combining alias with sound and open animation

Aliases work very well with menu open sound and menu open animation:

```yaml
group: "shop_menu"
alias: "shop"
sound: "minecraft:ui.button.click"

open_animation:
  preset: "slide_from_right"
  duration: 0.35
  stagger_delay: 0.04
```

## Recommended usage

Use aliases for menus that players open often.

Examples:

* main shop
* class selection
* profile
* language selector

For one-off internal UI states, you usually do not need an alias.


---

# 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://xcs-plugin.gitbook.io/cursorcs/guides/menu-aliases.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.