v5.0.0-beta.22 | Bulk ban, premium apps, bug fixes

Overview

This release adds some newer API features, like premium app subscriptions, bot banners, and bulk banning users.

Besides new features, this release also includes improved errors and bug fixes.

Premium App Subscriptions (#2583)

If your bot is eligible for monetization, you can now use JDA to handle entitlements in interactions to restrict features. With event.replyWithPremiumRequired(), you can upsell a premium subscription to a user:

Read more about entitlements and premium app subscriptions in the Discord Developer Docs.

Bulk Ban (#2630)

You can now ban up to 200 users in one request using guild.ban(users, messageDeleteTimeframe).

This endpoint has a few quirks to keep in mind:

• The BulkBanResponse includes failed users and banned users
• If a user was already banned, they are in the failed users
• If you don't have permissions to ban a user (higher role / owner), they also appear in failed users
• The self user also appears in failed users
• If all users "failed" you get an error response instead

New Features

• Add support for bulk banning users by @MinnDevelopment in #2630
• Add the ability to set the bot banner by @freya022 in #2629
• Add support for premium app subscriptions by @Giuliopime in #2583

Changes

• Create an exception when receiving UNKNOWN_WEBHOOK in interaction hooks by @freya022 in #2621

Bug Fixes

• Fix format specifiers when adding invalid choices by @freya022 in #2628
• Fix FlatMapRestAction predicate with complete or submit by @Whizyyy in #2636
• Handle numeric keys for ETF maps by @MinnDevelopment in #2642

Full Changelog: v5.0.0-beta.21...v5.0.0-beta.22

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.22")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.22</version> 
</dependency>

v5.0.0-beta.21 | Bug fixes and enforced nonce on messages

Overview

This release fixes a few bugs but also implements a new behavior on message sending.

With the new enforce nonce behavior, messages will no longer be duplicated due to timeouts or discord outages. This means, any message request will now send an automatically generated nonce. You can still set a custom nonce using setNonce, but you should make sure that this nonce is unique. If you previously relied on this setter, ensure that you are not sending duplicated nonce values.

New Features

• Add DiscordLocale values for these locales: Indonesian and Latin America (Spanish LATAM) by @stackpan in #2627

Changes

• Add support for enforce_nonce by @MinnDevelopment in #2614

Bug Fixes

• Add missing generic type to shardmanager by @duncte123 in #2612
• Add missing proxy url field to the MessageEmbed.VideoInfo class by @shaksternano in #2618
• Fix suppressing embeds on messages with webhooks by @freya022 in #2620

Full Changelog: v5.0.0-beta.20...v5.0.0-beta.21

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.21")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.21</version> 
</dependency>

v5.0.0-beta.20 | Bug fixes and internal refactoring

Overview

With this release, we reworked a lot of internals related to how we cache channels. Ideally, you should not notice any difference.

New Features

• Added missing properties to ApplicationInfo by @freya022 in #2605

Changes

• Unified channel cache by @MinnDevelopment in #2528
• Return immutable lists when documented by @freya022 in #2607

Bug Fixes

• Fix clearing of voice status by @MinnDevelopment in #2601
• Handle canTalk for private threads in interactions by @MinnDevelopment in #2603

Full Changelog: v5.0.0-beta.19...v5.0.0-beta.20

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.20")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.20</version> 
</dependency>

v5.0.0-beta.19 | Bug fixes and voice channel status

Overview

Smaller release with some bug fixes and added support for voice channel status feature.

Voice Channel Status (#2532)

Bots can now configure the voice channel status, shown when opening a voice channel in full screen mode. This works similarly to a channel topic, but can be configured by everyone who is currently connected to the channel.

The new VOICE_SET_STATUS permission indicates whether a user can change the channel status while they are connected. When a user is not connected to the channel, the MANAGE_CHANNEL permission is required instead (similar to topics).

Note that this feature might be replaced by a new "hang status" in the future, which would instead show on the user rather than the channel.

New Features

• Add voice status feature by @MinnDevelopment in #2532

Changes

• Add more logging to request handling by @MinnDevelopment in #2589
• Add missing message types by @MinnDevelopment in #2531
• Updating Dependencies by @Lewox in #2591
• Add check for max number of fields in EmbedBuilder by @Andre601 in #2592

Bug Fixes

• Fix incorrect hook injection for message context commands by @MinnDevelopment in #2593

Full Changelog: v5.0.0-beta.18...v5.0.0-beta.19

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.19")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.19</version> 
</dependency>

v5.0.0-beta.18

Overview

This release fixes a race-condition in the default rate-limiter implementation that very rarely resulted in an orphaned rate-limit bucket.

Orphan Rate-Limit Buckets (#2585)

Sometimes the cleanup of buckets resulted in an active rate-limit bucket being orphaned. This means that the bucket was continuously trying to execute the same request without updating its state.

This release should resolve that problem, fixing the occasional bug where a 429 response was handled incorrectly.

New Thread Model (#2463)

The default thread model used for the handling of rate-limits has been changed. Instead of using a single scheduled executor, we now make use of an additional elastic pool that automatically scales up and down based on how many buckets run concurrently.

In the previous model, the scheduled executor limited the capabilities by only providing a fixed amount of threads. To handle scaling with larger bots, we simply used 5 threads for each shard. This has been adjusted now to use a shared pool, which scales up and down based on load instead.

Please let us know if you run into any problems with the defaults in your deployments!

New Features

• Add support for resetting min/max length in TextInput.Builder by @Xirado in #2584

Changes

• Change thread model used for requests by @MinnDevelopment in #2463
• Remove outdated todo comments and update outdated logic in thread channels by @MinnDevelopment in #2581

Bug Fixes

• Fix orphaned rate-limit buckets by @MinnDevelopment in #2585
• Fix incorrect index used in attachment update requests by @MinnDevelopment in #2588

Full Changelog: v5.0.0-beta.17...v5.0.0-beta.18

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.18")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.18</version> 
</dependency>

v5.0.0-beta.17 | Fix webhooks in thread channels

Overview

This release fixes some issues with webhook executions in thread channels.

Changes

• Add interface type to channel types by @freya022 in #2567

Bug Fixes

• Fix webhook send & edit where the thread ID was set by @RedDaedalus in #2572
• Fix else if for threadMetadata being on avatarUrl after #2572 by @Vankka in #2573

Full Changelog: v5.0.0-beta.16...v5.0.0-beta.17

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.17")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.17</version> 
</dependency>

v5.0.0-beta.16 | Webhook Execution and Super Reactions

Overview

With this release, we have redesigned a major flaw in our entity constraints. Previously, message instances required a known cached channel instance to be usable. This flaw has been remedied by reworking this implementation to be usable with only a known channel id.

This means, that methods such as message.addReaction(...) or message.pin() can now work for message instances that have no channel object in cache. You can find out if a channel is available on a message instance, by using hasChannel. Adding support for this behavior was necessary, in order to implement webhook executions!

With this change resolved, we can now fully support sending messages through arbitrary webhooks by using WebhookClient.createClient. This webhook client makes use of the JDA rate-limit system and request queue, to properly handle rate-limits for you.

Interactions Hidden Threads

This release also fixes the problem of not receiving interactions in hidden threads, for instance if the thread is a private thread and your bot has not been added yet. This problem was actually caused by JDA expecting a channel instance in cache that was not present, which stopped the interaction from going through.

Discord has added more information about the channel objects in interactions, so we can now properly construct the thread channel instance just in time for the interaction event.

Super Reactions

Your bot can now tell what super-reactions are used. You still cannot send them because the API is too unstable.

Beta Period Almost Done!

We plan to end the beta period for JDA 5.0.0 very soon. There are a few more changes we are thinking of merging first, but the current release already seems very complete. We hope to end the beta period before the end of the year, stay tuned.

New Features

• Handle messages from inaccessible threads and add webhook support by @MinnDevelopment in #2390
• Implement super reaction handling by @MinnDevelopment in #2554

Bug Fixes

• Fix createCopy not copying DefaultValues by @Kaktushose in #2556
• Fix ChannelManagerImpl#reset by @Almighty-Satan in #2563
• Fix MissingFormatArgumentException in DataArray#getOffsetDateTime by @Almighty-Satan in #2564

Full Changelog: v5.0.0-beta.15...v5.0.0-beta.16

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.16")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.16</version> 
</dependency>

v5.0.0-beta.15 | Bug fixes

Overview

This release fixes a bug introduced by 5.0.0-beta.14.

Bug Fixes

• Add null check in checkPosition by @MinnDevelopment in #2553

Full Changelog: v5.0.0-beta.14...v5.0.0-beta.15

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.15")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.15</version> 
</dependency>

v5.0.0-beta.14 | Media Channels, Custom Status, LRU Cache

Overview

This brings JDA up to date with newly released API features and fixes a few issues.

Support for Custom Status (#2521)

Many years ago, the "Custom Status" feature has been released on Discord, but has since been limited to client users. With a change recently, bots have finally been granted access to set this custom status as well. This, however, is limited to only setting the text value and no emoji.

You can set a custom status using Activity.customStatus(text).

Media Channels (#2516)

Discord is rolling out another new channel type. This time the type is a derivation of forum channels, specifically designed to share media such as images or videos. This release adds support for media channels.

A few places now return the new abstraction IPostContainer, where previously a ForumChannel was used. This abstraction is used to deduplicate and expand the API to handle both media and forum channels equally, as both of these types handle posts (threads with start messages).

LRU Member Cache (#2506)

The member cache has become slightly more powerful by introducing the new LRUMemberCachePolicy. A Least-Recently-Used (LRU) cache keeps members cached based on activity.

Example:

MemberCachePolicy.VOICE                             // Keep in cache if currently in voice (skip LRU and ONLINE)
    .or(MemberCachePolicy.ONLINE)                   // Otherwise, only add to cache if online
    .and(MemberCachePolicy.lru(1000)                // keep 1000 recently active members
        .unloadUnless(MemberCachePolicy.VOICE))     // only unload if they are not in voice

New Features

• Add DiscordLocale#toLocale by @freya022 in #2485
• Add custom status support for bots by @RedDaedalus in #2521
• Added support for custom statuses using Activity.of by @Jqnn in #2524
• Add Activity#withState by @MinnDevelopment in #2523
• Add LRUMemberCachePolicy by @MinnDevelopment in #2506
• Add initial support for media channels by @MinnDevelopment in #2516
• Add default_values support by @MinnDevelopment in #2542

Changes

• Add position check to timeouts by @MinnDevelopment in #2540
• Allow override of headers applied by default by @zaroxh in #2529

Bug Fixes

• fix symmetricity of CustomEmojiImpl/RichCustomEmojiImpl#equals by @danthe1st in #2519
• Allow slowmode & nsfw in Stage Channels by @kazuryyx in #2538
• Improve handling of query parameters in image proxy by @MinnDevelopment in #2551

Full Changelog: v5.0.0-beta.13...v5.0.0-beta.14

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.14")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.14</version> 
</dependency>

v5.0.0-beta.13

Overview

This release includes a few bug fixes and a new FileUpload variant to optimize memory usage when uploading larger files.

Supplier FileUpload (#2508)

With the new FileUpload.fromStreamSupplier, an upload will no longer retain the entire file content in memory. This comes at the cost of having to re-read the source each time.

Example:

FileUpload.fromStreamSupplier("image.png", () -> {
    return new FileInputStream("myimage.png");
});

Each time the request is attempted, which can be more than once due to rate-limit retries, the supplier is used to create a new readable input stream of the file. Once the request successfully writes the entire body, the stream is closed again.

Note that the supplier must always return a new instance or reset the stream accordingly.

Getting Message Author from Reactions (#2499)

The MessageReactionAddEvent now provides the author id of the original message. This can be useful in situations where retrieving the message is too expensive.

New Features

• Add the message author id to message reaction events by @MinnDevelopment in #2499
• Add supplier based FileUpload by @MinnDevelopment in #2508

Changes

• Deprecate and replace onUserSpeaking by @MinnDevelopment in #2496

Bug Fixes

• Fix handling of thread update for unknown parent by @MinnDevelopment in #2494
• Change return type of method in JDA class. by @kiLeo13 in #2504
• Fix choices having an "options" prefix when automatically localizing by @freya022 in #2490
• Fix MessageCreateRequest#applyData not suppressing embeds by @Almighty-Satan in #2513
• Fix IllegalStateException in Message#getCategory by @Almighty-Satan in #2514

Full Changelog: v5.0.0-beta.12...v5.0.0-beta.13

Installation

Gradle

repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-beta.13")
}

Maven

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-beta.13</version> 
</dependency>