Executing Commands

Nevi supports two ways to run commands:

Admins can change the prefix with /prefix set. Prefixes can be 1-5 characters with no spaces — common choices are !, ,, ., or n!.

You don't need to type the full command name. Nevi uses a greedy prefix matching system — type any unique starting characters of a command name and it will resolve automatically.

If what you typed matches multiple commands (ambiguous), Nevi will ask "Not sure what you mean, sorry! Did you mean...?" and suggest the closest match.

Some very short shortcuts are reserved for specific commands so they always resolve without ambiguity:

Greedy matching also works for subcommands. If a command has subcommands like farm plant and farm plantall, you can shorten them:

Choice-based arguments work the same way — typing eas resolves to easy if that's the only choice starting with those letters.

Commands accept arguments in order — just type the values after the command name, separated by spaces. No need to write argument names.

Nearly all the time, you don't need quotes. Nevi's argument parser is smart — the last text argument in any command is greedy, meaning it automatically captures everything remaining in your message as one value.

Quotes are only needed in one situation: when a multi-word value isn't the last argument and you need to separate it from arguments that come after it.

A single unmatched quote (no closing quote) is treated as a regular character, so don't worry about stray quotes breaking anything.

Different argument types are parsed differently from text:

For arguments with fixed choices (like difficulty levels), greedy matching also applies — typing eas resolves to easy if it's the only choice starting with those letters.

Many commands have a default subcommand that runs when you don't specify one. This means you can skip the subcommand name entirely for the most common action:

If you type something that doesn't match any subcommand, Nevi uses the default and treats your input as arguments to that subcommand instead.

While positional arguments are the primary way to use commands, Nevi also supports an optional named syntax using name:value pairs. This can be useful when you want to skip optional arguments or set them out of order.

You can mix positional and named arguments freely. Named arguments are extracted first, then the remaining values are mapped positionally. Most users will never need this — positional arguments are simpler and work for everything.