Aliases
Add alternative names to your Nevi custom commands with aliases. Create shortcuts, abbreviations, and multiple trigger names for the same command.
What are aliases?
Aliases are alternative names for an existing custom command. When someone uses an alias, it runs exactly the same response as the original command: same template, same variables, same actions, same everything.
This is useful when you want to provide shortcuts, alternative spellings, or multiple ways to trigger the same functionality without duplicating the command.
Quick example
If you have a command called /hello, you can add an alias /hi so that both /hello and /hi produce the same response.
Adding an alias
Use the /customcmd alias add command to create a new alias for an existing custom command.
Syntax
/customcmd alias add <command> <alias>command - The name of the existing custom command you want to create an alias for.
alias - The new alternative name.
Examples
/customcmd alias add hello hi - now /hi runs the same as /hello
/customcmd alias add serverinfo si - short abbreviation for /serverinfo
/customcmd alias add 8ball magic8ball - alternative full name
Removing an alias
Use the /customcmd alias remove command to remove an alias from a custom command.
Syntax
/customcmd alias remove <command> <alias>command - The original command name.
alias - The alias name to remove.
Example
/customcmd alias remove hello hiRemoves the hi alias from the hello command. The original /hello command continues to work. Only the alias is removed.
Multiple aliases
A single custom command can have multiple aliases. There is no practical limit. Add as many alternative names as you need.
Example: Greeting command with multiple aliases
Start with the original command:
/customcmd create hello Hey there, {user.name}!Then add multiple aliases:
/customcmd alias add hello hi/customcmd alias add hello hey/customcmd alias add hello greet/customcmd alias add hello yoNow /hello, /hi, /hey, /greet, and /yo all produce the same response.
Editing the original
If you edit the original command with /customcmd edit, all aliases automatically use the updated response. You never need to update aliases individually.
Deleting the original
If you delete the original command with /customcmd delete, all of its aliases are removed as well. Aliases cannot exist without a parent command.
Tips
Use abbreviations
Long command names are harder to type. Create short aliases for frequently used commands: serverinfo → si, leaderboard → lb, coinflip → cf.
Cover common misspellings
If users frequently misspell a command, add the misspelling as an alias. For example, if people keep typing /leaderbord instead of /leaderboard, add it as an alias so it still works.
Provide both casual and formal names
Some users prefer casual names while others prefer descriptive ones. You can have both: /roll and /diceroll, /bal and /balance, /rng and /randomnumber.
Aliases don't conflict with built-in commands
You cannot create an alias that shares a name with a built-in Nevi command. If you try, Nevi will let you know the name is already taken.
Related Commands
/customcmdmanagementRequires modCreate and manage custom commands with template support