Java wrapper for the popular chat & VOIP service: Discord https://discord.com
This is a small bugfix release, including some missing features for premium app entitlements.
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());
}
IPostContainerManager#setTopic
by @freya022 in https://github.com/discord-jda/JDA/pull/2666
Full Changelog: https://github.com/discord-jda/JDA/compare/v5.0.0-beta.23...v5.0.0-beta.24
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.24")
}
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.24</version>
</dependency>
This release includes an updated README, please let us know if you spot any issues with it!
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.
CommandInteractionPayload#getCommandString
in autocomplete interactions by @freya022 in https://github.com/discord-jda/JDA/pull/2659
Full Changelog: https://github.com/discord-jda/JDA/compare/v5.0.0-beta.22...v5.0.0-beta.23
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.23")
}
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.23</version>
</dependency>
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.
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.
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:
Full Changelog: https://github.com/discord-jda/JDA/compare/v5.0.0-beta.21...v5.0.0-beta.22
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.22")
}
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.22</version>
</dependency>
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.
Full Changelog: https://github.com/discord-jda/JDA/compare/v5.0.0-beta.20...v5.0.0-beta.21
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.21")
}
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.21</version>
</dependency>
With this release, we reworked a lot of internals related to how we cache channels. Ideally, you should not notice any difference.
Full Changelog: https://github.com/discord-jda/JDA/compare/v5.0.0-beta.19...v5.0.0-beta.20
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.20")
}
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.20</version>
</dependency>
Smaller release with some bug fixes and added support for voice channel status feature.
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.
Full Changelog: https://github.com/discord-jda/JDA/compare/v5.0.0-beta.18...v5.0.0-beta.19
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.19")
}
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.19</version>
</dependency>
This release fixes a race-condition in the default rate-limiter implementation that very rarely resulted in an orphaned rate-limit bucket.
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.
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!
Full Changelog: https://github.com/discord-jda/JDA/compare/v5.0.0-beta.17...v5.0.0-beta.18
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.18")
}
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.18</version>
</dependency>
This release fixes some issues with webhook executions in thread channels.
Full Changelog: https://github.com/discord-jda/JDA/compare/v5.0.0-beta.16...v5.0.0-beta.17
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.17")
}
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.17</version>
</dependency>
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.
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.
Your bot can now tell what super-reactions are used. You still cannot send them because the API is too unstable.
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.
Full Changelog: https://github.com/discord-jda/JDA/compare/v5.0.0-beta.15...v5.0.0-beta.16
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.16")
}
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.16</version>
</dependency>
This release fixes a bug introduced by 5.0.0-beta.14
.
Full Changelog: https://github.com/discord-jda/JDA/compare/v5.0.0-beta.14...v5.0.0-beta.15
repositories {
mavenCentral()
}
dependencies {
implementation("net.dv8tion:JDA:5.0.0-beta.15")
}
<dependency>
<groupId>net.dv8tion</groupId>
<artifactId>JDA</artifactId>
<version>5.0.0-beta.15</version>
</dependency>