-
-
Notifications
You must be signed in to change notification settings - Fork 6
Command Aliases File
Yao Chung Hu edited this page Jun 15, 2022
·
5 revisions
Command Aliases File will be located in config/commandaliases.json it uses the JSON format.
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.
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
}
}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+))?]
- Home
- Command Aliases File
- Command Aliases Commands
- Command Modes for 0.3.0 and above
- Create a Command Alias (0.9.0)
- Create a Command Alias (0.8.0)
- Create a Command Alias (0.7.0)
- Create a Command Alias (0.5.0)
- Create a Command Alias (0.3.0 - 0.4.2)
- Create a Command Alias (0.0.9 - 0.2.0)
- Roadmap