Releases: discord-jda/JDA
v5.0.0-beta.24 | Bug fixes and entitlement types
Overview
This is a small bugfix release, including some missing features for premium app entitlements.
Additional Entitlement Features (#2667)
This release adds support for test entitlements and consumed entitlements.
An entitlement can be consumed, marking it as already used. This can be useful for one-time entitlements, which are consumed on use.
public boolean hasEntitlement(long skuId, List<Entitlement> entitlements) {
return entitlements.stream().anyMatch(e -> e.getSkuIdLong() == skuId && !e.isConsumed());
}
public void consumeEntitlement(long skuId, List<Entitlement> entitlements) {
entitlements.stream()
.filter(e -> e.getSkuIdLong() == skuId && !e.isConsumed())
.findFirst()
.ifPresent(entitlement -> entitlement.consume().queue());
}
New Features
- Add
IPostContainerManager#setTopic
by @freya022 in #2666 - Add missing features relating to premium app subscriptions by @Tobias123567 in #2667
Changes
- Improve logging for gateway connection by @MinnDevelopment in #2665
- Add more static analyzer annotations by @MinnDevelopment in #2675
- Update SLF4J api and jackson by @MinnDevelopment in #2674
Bug Fixes
- Fix ClassCastException in EntityBuilder#updateMemberCache by @Xirado in #2660
- Properly copy poll data in MessageCreateRequest#applyData by @MinnDevelopment in #2662
- Make channel access checks consistent by @MinnDevelopment in #2679
Full Changelog: v5.0.0-beta.23...v5.0.0-beta.24
Installation
Gradle
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.24")
}
Maven
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.24</version>
</dependency>
v5.0.0-beta.23 | Message Polls
Overview
This release includes an updated README, please let us know if you spot any issues with it!
Polls (#2649)
Discord has recently released a new feature on their platform to start and vote in polls. These polls can now be sent in messages:
channel.sendMessage("Hello guys! Check my poll:")
.setPoll(
MessagePollData.builder("Which programming language is better?")
.addAnswer("Java", Emoji.fromFormatted("<:java:1006323566314274856>"))
.addAnswer("Kotlin", Emoji.fromFormatted("<:kotlin:295940257797636096>"))
.build())
.queue()
The poll automatically expires after a set duration, configurable in the MessagePollBuilder
using setDuration. A poll can also be ended manually using endPoll or endPollById.
You can check the poll votes on a message using the new Message#getPoll
:
MessagePoll poll = message.getPoll();
for (MessagePoll.Answer answer : poll.getAnswers()) {
System.out.printf("Poll Answer %s has %d votes\n", answer.getText(), answer.getVotes());
}
Note
The votes for polls are eventually consistent and need to be recounted after the poll ends. You can check whether the votes are validated using MessagePoll#isFinalizedVotes.
New Features
- Add USER_MUST_BE_VERIFIED ErrorResponse by @GitMilchi in #2651
- Update permission enum by @MinnDevelopment in #2654
- Poll support by @MinnDevelopment in #2649
Changes
- Update dependencies and use version catalog by @MinnDevelopment in #2652
Bugs Fixes
Full Changelog: v5.0.0-beta.22...v5.0.0-beta.23
Installation
Gradle
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.23")
}
Maven
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.23</version>
</dependency>
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
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
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
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
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>