Releases: Revxrsal/Lamp
Releases · Revxrsal/Lamp
Lamp v4: Beta 2
#2 beta candidate for Lamp v4.
Lamp v4: Beta 1
The first beta candidate for Lamp v4.
Lamp v3.2.1
- Add a no-arg constructor to SendMessageException and CommandErrorException, to allow users to signal command failing without sending a message. This is useful if users want to use their own way of sending error feedback to the user.
- (Bukkit) Add
@LiteralEnum
annotation andBukkitBrigadier#showEnumsAsNativeLiterals
to make enums appear as native parameters. This allows commands to have literals between parameters. - (Velocity) Add a sender resolver for
Audience
, and a response handler forComponentLike
Lamp v3.2.0
- Use native player completions for OfflinePlayer (#87)
Lamp v3.1.9
What's Changed
- Add EntitySelector#containsExactly by @iiAhmedYT in #77
- Fixed bugs in Brigadier Paper with empty commands or commands that contain
\
- Fixed a bug in Kotlin functions that contain no parameters
Full Changelog: 3.1.8...3.1.9
Lamp v3.1.8
- Fixed a bug in commands that contain
:
. OfflinePlayer
will automatically get the online players for completions
Full Changelog: 3.1.7...3.1.8
Lamp v3.1.7
- Support for Kotlin's default arguments 🎉 (they must use
@Optional
) @DefaultFor
now accepts a~
for parent paths- Removed
@Optional#def()
@Optional
is now allowed on primitive types, in which case they will use the default primitive value (zero for numbers, false for booleans, etc.)
Full Changelog: 3.1.6...3.1.7
Lamp v3.1.6
- Fixed Brigadier numerical and boolean arguments not working
- Fixed Brigadier commands showing the Unknow command message when they are missing an argument
- Fixed the EntitySelector not showing suggestions
- Fixed parameters sometimes getting
null
when they aren't optional - JDA slash commands by @bivashy 🎉
- Sponge 8 by @creatorfromhell 🎉
- OfflinePlayer fixes
What's Changed
- OfflinePlayer resolver by @SrBlecaute01 in #54
- Bump JDA version 4.4.0_352 -> 5.0.0-beta.9 by @bivashy in #55
- JDA Slash commands support. Backward compatible by @bivashy in #62
- Properly handle DefaultFor in JDA Slash commands by @bivashy in #63
- Call JDAActor#checkInGuild only if this is required. by @bivashy in #68
- Add support of '@default' and '@optional' to JDA Slash commands by @bivashy in #65
- Sponge 8 Base Support. by @creatorfromhell in #67
- Support for JDA slash commands by @Revxrsal in #69
New Contributors
- @SrBlecaute01 made their first contribution in #54
- @creatorfromhell made their first contribution in #67
Full Changelog: 3.1.5...3.1.6
Lamp v3.1.5
- Allow commands to be defined and customized in the plugin.yml
- New API: ParameterNamingStrategy
- Add
AutoCompleter#filterToClosestInput(boolean)
to customize whether inputs are filtered to match the closest input by default or not - Fix a small issue in commodore classloading
Lamp v3.1.4
- Scheduled removal of the
ArgumentParser
API - Scheduled removal of the
ArgumentStack#copy
methods @Default
functionality has been reduced to default parameters only, and is no longer applicable on methods. Use@DefaultFor
instead- Added
CommandActor#dispatch(...)
methods - Code cleanups
Migrating
@Default
has been replaced by @DefaultFor
, which requires explicitly supplying the path to be the default action for. For example:
@Command("foo")
public class FooCommand {
@Subcommand("help") // The main path is /foo help <page>
@DefaultFor("foo") // <--- We can run /foo <page> and /foo help <page> and
// get the same result
public void help(CommandActor actor, @Default("1") int page) {
...
}
}