> For the complete documentation index, see [llms.txt](https://wiki.helpch.at/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.helpch.at/helpchat-plugins/deluxemenus/options-and-configurations/command-registration.md).

# Command Registration

More information about registering menu commands

How to register a command?

Each menu can have 2 options:

### [open\_command](/helpchat-plugins/deluxemenus/options-and-configurations/gui.md#open-command)

This is used to specify a list of commands that can be used to open the menu.

{% hint style="danger" %}
Note that by using this option alone, you will get no tab completion and other plugins will override this command
{% endhint %}

### [register\_command](/helpchat-plugins/deluxemenus/options-and-configurations/gui.md#register-command)

This accepts a boolean value (true or false). If the value is set to true, then on every server restart, DeluxeMenus will make an effort to register the command with the server. This should provide tab completion.

## I have another plugin that registers the same command. What can I do?

When a command is registered with the server, an alias is provided: `/deluxemenus:<menu-command>`.

To better explain this, let's take an example:

We have a menu named `randomteleportmenu` with `open_command: "rtp"` and `register_command: true`. We'll consider that the server was restarted since the menu was created so the command was registered.\
We are also using a RandomTeleport plugin that also registers the `/rtp` command.

Now when we execute `/rtp`, we get randomly teleported instead of having our menu open.

How do we fix this?\
We could use `/deluxemenus:rtp` to open the menu, but we don't want our players to use prefixed commands as they are too long.\\

The solution is to use the [commands.yml](https://bukkit.fandom.com/wiki/Commands.yml) file provided by our server. We can find the file in the server's root directory where we find the the server jar file and the eula.txt file. If you've never modified the file, it will look something like this by default:

```yaml
command-block-overrides: []
ignore-vanilla-permissions: false
aliases:
  icanhasbukkit:
  - version $1-
```

Now, we modify the file like this:

```yaml
command-block-overrides: []
ignore-vanilla-permissions: false
aliases:
  icanhasbukkit:
  - version $1-
  rtp:
  - deluxemenus:rtp $1-
```

Save, restart the server and you're all done!

{% hint style="danger" %}
Make sure to save the changes and restart the server if you want the changes to properly apply!
{% endhint %}

{% hint style="success" %}
If you want to read more about the commands.yml file, you can do so here: <https://bukkit.fandom.com/wiki/Commands.yml>
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.helpch.at/helpchat-plugins/deluxemenus/options-and-configurations/command-registration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.