Configuration

Learn how to configure Command Maker for your needs. All configuration is done through simple JSON files.

Configuration File Locations

Command Maker stores all configuration in JSON files located at:

  • Single Player: .minecraft/config/CommandMaker/
  • Servers: config/CommandMaker/
  • Launchers: instance-name/minecraft/config/CommandMaker/

The folder is automatically created on first launch.

aliases.json

This is the main configuration file where you define all your aliases and custom commands.

File Structure

{
  "alias_name": "minecraft command",
  "another_alias": "another minecraft command",
  "greet": "say Hello, ${player}!"
}

Key Points

  • Each alias is a key-value pair
  • Keys are the alias names (what you type in chat)
  • Values are the actual Minecraft commands to execute
  • Supports variables like ${player}, ${x}, ${y}, ${z}
  • Must be valid JSON (proper commas, quotes, etc.)

Example Configuration

{
  "home": "tp ${player} 0 64 0",
  "spawn": "tp ${player} 100 100 100",
  "greet": "say Hello, ${player}!",
  "admin": "give ${player} diamond 64"
}

Reloading Configuration

After editing your aliases.json, reload the configuration with:

/addcommand reload

You should see a message confirming the aliases were loaded.

Managing Aliases In-Game

You can manage aliases directly in-game using commands:

Add a New Alias

/addcommand add <alias> <command>

Example: /addcommand add test "say This is a test!"

Delete an Alias

/addcommand del <alias>

Example: /addcommand del test

Delete via GUI

/deletealiases-gui

Opens a graphical interface to manage and delete aliases.

Reload All Aliases

/addcommand reload

Variable Substitution

Command Maker supports several built-in variables:

  • ${player} - Current player name
  • ${x} - Player's X coordinate
  • ${y} - Player's Y coordinate
  • ${z} - Player's Z coordinate

Example: "home": "tp ${player} ${x} 64 ${z}"

Learn more: Variables & Substitution

JSON Validation

Your aliases.json must be valid JSON. Common mistakes:

  • ❌ Missing commas between entries
  • ❌ Single quotes instead of double quotes
  • ❌ Trailing commas after the last entry
  • ❌ Unescaped special characters

Use a JSON validator to check your file.

Troubleshooting Configuration

❌ Aliases not loading?

  • Check that aliases.json is valid JSON
  • Ensure the file is in the correct location
  • Use /addcommand reload after making changes
  • Check the console for error messages

More help: Troubleshooting Guide

Next Steps

  1. Create your first alias in aliases.json
  2. Use /addcommand reload to apply changes
  3. Learn about Custom Syntax for advanced features
  4. Explore Examples for inspiration