How to Set Up MyCommand on a Minecraft Server

What MyCommand Does

MyCommand, also called MyCMD, is a Minecraft plugin for building custom commands and server functions. It can create simple text commands, command shortcuts, clickable messages, broadcasts, menus, shop-like trades, aliases, and more.

This is useful when an existing plugin almost does what a server needs, but the command syntax is too long, too awkward, or not quite friendly enough for players. Instead of asking players to remember a paragraph disguised as a command, MyCommand lets administrators create cleaner commands with custom output and permissions.

The plugin is powerful, but that also means its configuration can be picky. Most work happens inside YAML files, so spacing, command names, options, and variables need to be written carefully.

Installing MyCommand

1. Open the MyCommand page on Spigot and click Download in the top-right corner.

1. Open the HolyHosting server panel, go to the file manager, and log in with the server password.

1. Enter the `plugins` folder and choose Upload.

1. Drag the MyCommand `.jar` file into the upload area.

1. Wait until the upload reaches 100%, then restart the Minecraft server.

After the restart, MyCommand should generate its plugin folder and default files. If the folder does not appear, confirm that the server is running a plugin-compatible platform such as Paper, Spigot, or Bukkit.

Understanding MyCommand Configuration

MyCommand is mostly controlled through files rather than in-game setup commands. That makes it flexible, but it also means every command needs the correct structure.

A custom command usually includes:

• A command name
• A command type
• One or more output lines or actions
• Optional permissions
• Optional variables such as player names or command arguments

Common Command Types

MyCommand supports many command types, but these are some of the most common starting points:

• `TEXT`: Creates a command that sends plain text to the player.
• `RAW_TEXT`: Sends formatted text and can include clickable or hoverable elements.
• `RUN_COMMAND`: Runs another command, often with variables.
• `ALIAS`: Creates a shorter version of an existing command without variable handling.

Use `TEXT` for information commands, `RAW_TEXT` for clickable lists, `RUN_COMMAND` for shortcuts that need arguments, and `ALIAS` for simple command replacements.

Useful Variables

Variables allow a command to react to the player using it or the arguments they type.

• `$arg1`, `$arg2`, `$arg3`: Reads specific arguments from the command.
• `$multiargs`: Reads multiple arguments, usually for custom messages.
• `$player`: Returns the command sender's username.
• `$world`: Returns the command sender's current world.
• `$online`: Shows the number of online players.
• `$money`: Shows the sender's currency balance when Vault is installed.

For example, if a command uses `$arg1`, and a player runs `/vip Steve`, then `$arg1` becomes `Steve`.

Common Options

Options control how the command behaves in-game.

• `registered: true` or `false`: Controls whether the command appears in tab completion.
• `permission-required: true` or `false`: Controls whether a permission is needed.
• `permission-node: example.permission`: Sets the permission node for the command.
• `permission-error: 'Message here'`: Sends a custom message when a player lacks permission.

Permissions are especially useful for staff commands, rank tools, or anything that should not be handed to every player like a suspiciously sharp object.

Creating a Command File

Before adding custom commands, create a new YAML file inside the MyCommand commands folder. Keeping commands split by category can make the plugin much easier to manage later.

1. Open the HolyHosting server panel and go to the file manager.
2. Enter the `plugins` folder.
3. Open the `MyCommand` folder.
4. Open the `commands` folder.
5. Click New file.
6. Name the file after its purpose and end it with `.yml`, such as `aliases.yml`, `rules.yml`, or `shop.yml`.
7. Add the command configuration, save the file, and restart the server.

After editing command files, MyCommand can also be reloaded in-game with:

```text /mycmd-reload commands all ```

The `commands` folder may include an `examples.yml` file. It can be useful for reference, but remember that commands inside enabled files may be usable by players. Remove or disable example commands that should not be active on the server.

Practical MyCommand Examples

MyCommand can handle a lot, so examples are the fastest way to understand how the pieces fit together.

Shortcut Command for a Warp

A simple alias can turn a longer plugin command into something easier for players to remember. For example, if the server has a PvP arena warp, an alias could turn a longer warp command into `/pvp`.

This is best for commands that always run the same way and do not need player input.

Shortcut Command With an Argument

For commands that need a player name, item amount, or other value, use variables such as `$arg1`.

A common example is a staff shortcut for LuckPerms. Instead of typing a long rank command every time, a custom command can accept a player name as the first argument and pass it into the full command.

If the command is `/vip Steve`, then `$arg1` becomes `Steve`. The permission option can limit usage to staff members or rank managers. For example, players could need a permission node such as `server.vip` before they can run it.

Rules Command

A rules command is one of the simplest MyCommand uses. Each configured line displays as text in chat when a player runs the command.

This same setup can be used for:

• `/rules`
• `/help`
• `/info`
• `/discord`
• `/store`

Color codes can be added for cleaner formatting, as long as the server version and chat setup support them.

Voting Links

A vote command can show a list of voting sites with clickable links. For clickable URL lines, MyCommand uses `$OPEN_URL$` before the displayed text, then separates the hover text and URL with semicolons.

Normal text lines can be mixed in as labels or instructions. This makes the command useful for vote lists, website links, maps, rules pages, or any external resource players need often.

Custom Trade Command

MyCommand can also create villager-style trades that act like a small shop. These trades can use in-game items, set required costs, and define maximum uses.

The general `merchant_items` format is:

```text item:amount(cost)item:amount(max_uses)number ```

The first item and amount are what the player receives. The item after `(cost)` is what the player must pay. More `merchant_items` lines can be added to create multiple trade options.

Troubleshooting

Registered Commands Do Not Work

If `registered: true` is set but the command still does not appear or run properly, restart the server first. If that does not fix it, reload a specific command file in-game:

```text /mycmd-reload commands file_name ```

Replace `file_name` with the exact file name that contains the command. If the file is named `rules.yml`, use the matching name expected by the plugin command.

Custom Commands Fail to Run

Most MyCommand problems come from YAML formatting or command conflicts. Check these items first:

• The command has a valid type.
• Indentation is correct.
• Required spaces are present.
• The command name is not already used by another plugin.
• Variables match the command being run.
• Permission settings are not blocking the player.

If a custom command has the same name as a command from another plugin, MyCommand may not override it. In that case, choose a different command name or adjust the original plugin's settings if it supports command aliases.

Final Notes

MyCommand is a flexible plugin for turning long commands, information pages, links, trades, and server tools into cleaner custom commands. Start with a small YAML file, test one command at a time, and reload or restart after changes. Once the formatting makes sense, the plugin becomes much easier to work with and much less likely to complain about a missing space like it has a legal department.