1.2.3

1.2.3 Release Notes:

• Enabled remaning tests.
• Skipped tests prevent compiler errors on JitPack.

Special thanks to @gamerover98 for their contributions with tests.

What's Changed

• Updated paper-api to 1.20.1 and added MockBukkit test suites by @gamerover98 in #6

New Contributors

• @gamerover98 made their first contribution in #6

Full Changelog: 1.2.2...1.2.3

1.2.2

1.2.2 Release Notes:

• Replaced CommandFramework#setAnyMatch method which is Java Consumer with CommandFramework#setMatchFunction which is a Java Function from functional interfaces feature, now you can return a boolean value and consider sending command usages to sender. Sender will receive usage message by default.

	/**
	 * Function to apply if there is no matched commands related framework.
	 *
	 * <pre>
	 *     // To disable sending usage to command sender return true
	 *     CommandFramework#setMatchFunction(arguments -> true);
	 * </pre>
	 */
	@Nullable
	private Function<CommandArguments, Boolean> matchFunction = (arguments) -> false;

Full Changelog: 1.2.1...1.2.2

1.2.1

1.2.1 Release Notes:

• Fixed command aliases do not support case-sensitive. (#3)
• Added unregistering command methods. (#4)

Full Changelog: 1.2.0...1.2.1

1.2.0

1.2.0 Release Notes:

• Removed Commons from libraries and added some parts of the library to Utils class.
  • Possible fix to prevent overlapping classes when users both using Commons and CommandFramework.

Full Changelog: 1.1.9...1.2.0

1.1.9

1.1.9 Release notes:

• Fixed the empty permissions cause some bugs.
• Fixed the sub-commands are registering as a main command which causes duplication.

1.1.8

1.1.8 Release notes:

• Added optional permission to tab completer annotation.

1.1.7

1.1.7 Release notes:

• Now command cooldowns work with sub commands.

1.1.6

Bump version

1.1.5

1.1.5 Release notes:

Fixes:

• Fixed empty command permissions not passing permission check.

Additions:

• Updated Commons library.

1.1.4

1.1.4 Release Notes:

• Fixed cooldown commands can be executed twice after the first execution.
• Now CommandFramework.WAIT_BEFORE_USING_AGAIN message shows remaining time to execute command again.