Releases: KapiMC/Kapi
Releases · KapiMC/Kapi
v0.2.1
Fixed
- Command
@Literal
annotations conflicting when method signature is identical. - Command tab completion sometime not suggesting arguments or suggesting wrong arguments.
- Entity-based renders such as
TextDisplayRender
,BlockDisplayRender
andItemDisplayRender
did not update their position every tick.
v0.2.0
Added
- More number parsers in
Utils
class, for types such as short/int/long/float/double. Log.Level.KAPI
, for internal logging inside of Kapi.
This should help with testing and debugging Kapi, while not cluttering theDEBUG
level.- Command System:
Command
class that can be extended to create a command.@SubCommand
annotation to mark methods inside a class that extendsCommand
.KapiPlugin#registerCommand(String, Command)
to register aCommand
subclass.ArgumentParser<T>
to allow for parsing a generic type inside a subcommand method.ArgumentRegistry
to manage argument parsers and what classes they apply to.- Argument parsers can be implemented by users and registered in the registry,
this allows users to create their own parsers for their own custom types. - Built-in argument parsers for primitives, any enums, arrays,
List<T>
,Option<T>
,Location
andPlayer
. - Automatic reporting of possible subcommands to the user if no subcommands match.
SqliteDB
to manage file-based Sqlite databases andQueryBuilder
to ease the process of creatingSqlQuery
.
Deprecated
Utils#col24(String)
should be replaced withUtils#col(String)
which supports 24-bit "true color".
See this website for how to format it.