v1.5.0

CommandUtils 1.5.0

First release in a year.

Breaking

• Abstract*, Simple*, and the whole bukkit package moved into a new expansion/ package (expansion.simple, expansion.bukkit).
• Proxied command senders are gone.
• CommandPermission is now predicate-based. The old opLevel and string constructors no longer exist.

New

• Commands now run safely and catch throwable.
• You can register your own renderers for exception types with ExceptionRenderer / ExceptionRenderers.
• CommandPermission now has single, and, or, not, world, plus PLAYER_ONLY, CONSOLE_ONLY, OP, ALWAYS, and NEVER.
• BasicFlagsHelper is an opinionated helper for completing --key and --key value flags inside a greedy string argument, handling offsets, spaces, and multiple flags for you.
• doubleArg, floatArg, and longArg now have methods that take min and max bounds.

Misc

• Various small cleanups and fixes.

v1.3.0

Bug Fixes 🐛

• Fixes many issues with suggestions and current argument

Removal and Deprecation⚠

• SuggestionHelper is now deprecated
• CommandWrapper#senderTypeString is now obsolete
• suggestIfCurrentStartsWith was removed, and replaced by suggestIfValueStartsWithCurrent

v1.2.3

New Features 🎉

• New command system built upon CommandUtils itself, inspired by Bukkit's command API
• More flexible argument creation through CustomArgument
• Easier suggestion creation, including suggestions that start with the current argument
• Improved SuggestionsHelper with new methods and fixes
• Fixed issues in SuggestionsHelper, including returning the input without the command when empty
• Added new methods to SuggestionsHelper, including just and default methods

⚠ Breaking Change: Legacy Color Codes Removal

LegacyColorsTranslator has been removed due to compatibility issues with Minimessage format. Legacy color codes will no longer work.

Suggested Update:

• Before: &7
• After: <gray>
• More: https://docs.advntr.dev/minimessage/format.html

Recommended Fix:

If you were using legacy color codes, please update your code to use minimessage (or even components.)

v1.2.2

• Small bug fix of double player names in PlayerArgumentType

v1.2.1

• Ability to use arguments from strings (https://github.com/vansencool/CommandUtils/blob/main/src/main/java/dev/vansen/commandutils/argument/finder/ArgumentString.java).
• Ability to use legacy color codes in tooltips, messages, etc.
• Ability to add custom requirements to commands, subcommands, arguments.
• Ability to access the CommandDispatcher from CommandAPI.
• New SuggestionsHelper to make suggestions easier (such as getting the current argument that is being typed.)
• Fix in CommandWrapper#canExecute leading to re-execution of its own (causing a java.lang.StackOverflowError).

v1.2.0

• New argument (CommandBlockModeArgumentType)
• More flexible arguments provided by us (such as disabling tooltip entirely)
• Option to disable argument nesting
• Argument finder: https://github.com/vansencool/CommandUtils/blob/main/src/main/java/dev/vansen/commandutils/argument/finder/ArgumentFinder.java

⚠ Breaking Change: Generic Syntax Update

In this release, the usage of new Argument<>() is no longer valid and will result in a compilation error.

To resolve this issue, replace occurrences of new Argument<>(...) with new Argument(...) in your codebase.

Suggested Update:

• Before: new Argument<>(...)
• After: new Argument(...)

Recommended Fix:

Use IntelliJ's Find and Replace feature to apply the change across your project:

1. Open Edit > Find > Replace in Files....
2. Search for new Argument<>.
3. Replace with new Argument.
4. Hit replace
5. (Hit confirm if said)
   And you should be good to go!

v1.1.9

• Little changes

v1.1.8

• Little fix

v1.1.7

• Alot of adds, bug fixes, and performance improvements.

v1.1.6

• Better suggestions, and removal of Tooltiper