Skip to content

Command Aliases File

Yao Chung Hu edited this page Jun 15, 2022 · 5 revisions

Command Aliases File

Command Aliases File will be located in config/commandaliases.json it uses the JSON format.

Command Aliases Client File (0.5.0 and above)

Command Aliases Client File will be located in config/commandaliases-client.json it uses the JSON format. This file works identically to the Command Aliases File, but it will only load the commands client-sided. Please use these client-sided commands responsibly, we do not endorse using this in any harmful way.

Command Aliases Configuration File (0.7.0 and above)

The Command Aliases Configuration File will be located in config/command-aliases-config.json it uses the JSON format.

// Version 0.7.0
{
  "debug_settings": {
    "debug_mode": true, // Displays errors when creating new custom commands
    "show_processing_time": true, // Shows the amount of time it takes to process each command and execute them
    "broadcast_to_ops": true // Whether commands will be broadcasted to operators
  }
}

Creating Command Alias (No Longer Supported)

If you are using Sublime Text, enable Regular Expressions with Alt+R and Case sensitive with Alt+C.

Here are the patterns being used for:

  • Required Arguments - \{(?<classTool>\w+)(::(?<method>[\w:]+))?(#(?<variableName>\w+))?(@(?<formattingType>\w+))?}
  • Optional Arguments - \[(?<classTool>\w+)(::(?<method>[\w:]+))?(#(?<variableName>\w+))?(@(?<formattingType>\w+))?]

Clone this wiki locally