Migrate to V5

With V4 we have made a clean cut during development to finally have a stable release. However, V4 is based on JDA 5 and doesn't have support for Components V2 or Modals. With JDA-Commands V5, we finally support these features. But as always, some things have changed in the meantime. This guide will help you to migrate from V4 to V5.

New Features

• You can now reply with Components V2
• The Modal API has changed to also support CV2
• The new Introspection API allows you to access JDA-Commands' properties and event system
• The Reply Config now supports JDA's setSuppresedNotifications and setAllowedMentions
• Command Choices can now be dynamically loaded
• IMentionable objects now will be automatically localized
• You can now update the guild commands for a specific guild
• You can now add custom String Resolvers to the localization system

Note

You can find the full changelog here

Changes

• After calling MessageReply#embeds(String...), MessageReply#components(String...) or MessageReply#builder(Consumer) you can no longer access the ConfigurableReply
• InteractionDefinition.ReplyConfig#editReply(), InteractionDefinition.ReplyConfig#keepComponents() and InteractionDefinition.ReplyConfig#keepSelections() can now only be called on a ComponentEvent
• The ErrorMessageFactory now uses Components V2. It has to return a MessageTopLevelComponent instead of MessageCreateData
• The DefaultErrorMessageFactory now uses Components V2
• Removed EmbedConfig#errorSource()
• Removed Event#i18n(), use Event#messageResolver() instead

Renaming

• ErrorMessageFactory#getCommandExecutionFailedMessage() -> ErrorMessageFactory#getInteractionExecutionFailedMessage(ErrorMessageFactory.ErrorContext, Throwable)
• @EntitySelectMenu -> <@EntityMenu>
• @StringSelectMenu -> <@StringMenu>
• Event#localize -> Event#resolve(String, Entry...)
• Priority#PERMISSIONS -> Priority#HIGHEST