Changelog for CommandsAPI Version 2.0.0

Note: This release introduces major changes that are not backward compatible with previous versions.

• Renamed TabConverter to TabCompleter for improved clarity and alignment with its function.
• Added dynamic runtime casting methods for commands. This enhancement allows type casting at runtime, in addition to the existing type declaration system used when defining commands.
• Major rework of the Executor class: The Executor now manages both tab completion and command execution (perform) with a more streamlined architecture, resulting in enhanced performance and flexibility.

Changelog - CommandsAPI v1.6.0
New Features

• Enhanced Contextual Tab Completion: The tab-completion feature now considers previously entered arguments, enabling smarter and more context-aware command suggestions based on prior inputs.
  
  
• Direct Argument Typing: Developers can now add arguments directly with their associated class type, enabling direct typing and easier validation. Previously, arguments could only be specified using the "arg:type" syntax. This new approach improves code readability and maintainability.
  

Changes

• Java 8 Compatibility: CommandsAPI has been downgraded to Java 8 to ensure broader support and compatibility with legacy runtime environments.

Fixes & Optimizations

• Minor Optimizations in permission handling and command requirements, ensuring a more reliable behavior when providing context-specific command suggestions for users.

Changelog for CommandAPI Version 1.5.1
Release Date: September 17, 2024

New Features

• Command Completion with /plugin-name:command Format:
  
  • Added support for command completion when prefixed with the plugin name (e.g., /plugin-name:command). This improves compatibility in environments where multiple plugins might use similar commands.
• Command Execution with /plugin-name:command Format:
  
  • Commands can now be executed using the full /plugin-name:command format, ensuring the correct command is used even when multiple plugins share identical command names.
• New setDebug() Method:
  
  • Introduced the setDebug() method, allowing developers to control the display of debug information in the console. This provides better control over the verbosity of debug logs, making it easier to troubleshoot during development without cluttering production logs.

Improvements

• Enhanced Compatibility with Multi-Command Environments:
  • This version improves the handling of commands shared between multiple plugins, allowing users to explicitly specify the plugin during both command completion and execution.

Upgrade Notes

• No major changes are expected for existing projects, but users are encouraged to test the new prefixed command syntax for better command handling in multi-plugin environments.
• The setDebug() method is optional but can be useful for adjusting the level of debug information displayed in the console.

This update focuses on functional improvements and developer flexibility, making CommandAPI more adaptable to complex environments and easier to customize for debugging and troubleshooting.

### Changelog for CommandAPI Version 1.5.0

**Release Date:** August 27, 2024

#### New Features
- **Customizable Logging System:**
- Added the ability to change the logging system used by CommandAPI. Users can now customize how and where log messages are recorded, enhancing flexibility and integration with different logging frameworks.

#### Improvements
- **Package Rework:**
- The internal package structure of CommandAPI has been reorganized to improve code readability and maintainability. This change may affect imports in existing implementations; ensure that your project is updated accordingly.

- **Command Executor Extraction:**
- The Command Executor logic has been extracted from the `CommandManager` class and placed into its own dedicated class. This separation of concerns improves the modularity of the codebase, making it easier to manage and extend.

#### Miscellaneous
- **Documentation Updates:**
- Updated the documentation to reflect the new package structure and provide guidance on how to utilize the customizable logging system and new command executor structure.

#### Upgrade Notes
- **Breaking Changes:**
- If your project depends on specific package structures or internal implementations of the `CommandManager` class, ensure that you update your imports and references to align with the new package layout.
- Review the updated documentation to understand the changes to the Command Executor and how to adapt your current implementation.

#### Bug Fixes
- **General Stability Improvements:**
- Minor bug fixes and performance enhancements have been applied throughout the codebase.

This version is a significant update that enhances customization, improves the architecture, and lays the groundwork for future features.

New Features:

• Conditional Command Requirements:
  
  • Added the ability to include conditional requirements for commands. This feature allows commands to be executed only if certain conditions outside the command execution environment are met.
  • Example Conditions:
    • Player in Overworld: Commands can now check if the player is in the Overworld before executing.
    • Player Health: Commands can verify if the player has full health before proceeding.
  These new conditional requirements enhance gameplay by allowing more complex and context-sensitive commands, providing greater control and flexibility for players and administrators.
  

Improvements:

• Command System Overhaul:
  • Enhanced the command system to support the integration of conditional checks without affecting performance.
  • Improved error messages to provide clearer feedback when conditions for command execution are not met.

Documentation:

• Updated the user guide to include detailed instructions on how to implement and use the new conditional command requirements.
• Added examples and best practices for utilizing conditional checks effectively.

We hope these new features improve your developement experience by offering more dynamic and responsive command execution!