Skip to content
This repository has been archived by the owner on Sep 9, 2024. It is now read-only.

Update dependency net.dv8tion:JDA to v5.0.0-beta.24 #5

Merged
merged 2 commits into from
Jul 3, 2024
Merged

Update dependency net.dv8tion:JDA to v5.0.0-beta.24 #5

merged 2 commits into from
Jul 3, 2024

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 3, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
net.dv8tion:JDA 5.0.0-alpha.21 -> 5.0.0-beta.24 age adoption passing confidence

Release Notes

DV8FromTheWorld/JDA (net.dv8tion: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

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@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

Changes

Bugs Fixes

Full Changelog: discord-jda/JDA@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:

b306d1ccc7205d2291f4535f912a790e

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

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@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

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@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

Bug Fixes

Full Changelog: discord-jda/JDA@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

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@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

Bug Fixes

Full Changelog: discord-jda/JDA@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

Full Changelog: discord-jda/JDA@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

Bug Fixes

Full Changelog: discord-jda/JDA@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

Full Changelog: discord-jda/JDA@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

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@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

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@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>

v5.0.0-beta.12: | Bug fixes

Overview

This release fixes a few annoying bugs that were introduced by the username changes.

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.11...v5.0.0-beta.12

Installation

Gradle

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

Maven

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

v5.0.0-beta.11: | Bug fixes and embed from json

Compare Source

Overview

This release fixes a few issues introduced by the username changes. It also introduces EmbedBuilder.fromData as a way to deserialize embeds from JSON.

There are also some changes to our online presence.

  • The JDA repository has moved to the discord-jda GitHub organization
  • The javadocs moved away from the Jenkins CI host to GitHub pages and can be found at our wiki domain docs.jda.wiki
  • All commits on the master branch will from now on build and upload artifacts using the Artifacts Workflow. Those artifacts stay up for a total of 90 days and can be downloaded as a zip file. All releases will continue to provide artifacts for that specific version indefinitely.
Create Embeds From JSON (#​2471)

Using the new EmbedBuilder.fromData factory method, you can now create embed instances from JSON or ETF data.

MessageEmbed embed = new EmbedBuilder().setDescription("Hello, friend").build();

byte[] data = embed.toData().toJson(); // serialize to json data
Files.write(path, json); // store the embed somewhere on disk

DataObject json = DataObject.fromJson(Files.newInputStream(path)); // load the json data
MessageEmbed reconstructed = EmbedBuilder.fromData(json).build(); // reconstruct the same embed using the builder

New Features

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.10...v5.0.0-beta.11

Installation

Gradle

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

Maven

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

v5.0.0-beta.10

Compare Source

Overview

With this release, we are taking the first steps to transition into the new username system for Discord by marking some methods as incubating or deprecated. This release also introduces support for AutoMod, both events and changing the AutoMod rules of a guild.

AutoMod Support (#​2429)

You can now modify the AutoMod rules of a guild using AutoModRuleData and Guild#createAutoModRule.

Support for member profile AutoMod has not been added yet, due to the API being very unstable still.

Example

guild.createAutoModRule(
  AutoModRule.onMessage("No morbius memes", TriggerConfig.keywordFilter("*morb*"))
             .putResponses(AutoModResponse.blockMessage("This meme is unfunny."))
).queue();
Username Changes (#​2462)

Discord is changing to globally unique usernames and removing discriminators, this is explained in their blog post. We are taking the first steps to transition with this release.

Deprecated Features

  • JDA#getUserByTag
  • Guild#getMemberByTag
  • User#getDiscriminator
  • User#getAsTag
  • SelfUpdateDiscriminatorEvent
  • UserUpdateDiscriminatorEvent
  • AccountManager#setName

Incubating Features

These are likely to be deprecated and removed in the future.

  • JDA#getUsersByName
  • Guild#getMembersByName

Other Changes

  • In the future, User#getDiscriminator will return "0000" for users who have a globally unique username from the new system.
  • A new User#getEffectiveName has been introduced to get the "effective display name" of a user, meaning either the User#getGlobalName or User#getName. This also affects Member#getEffectiveName, which will now return based on precedence guild nickname > global name > username.
  • User#getDefaultAvatarId now depends on the user id instead of the discriminator (when they have the discriminator 0000)

New Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.9...v5.0.0-beta.10

Installation

Gradle

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

Maven

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

v5.0.0-beta.9: | Bug fixes and new permissions

Compare Source

Overview

This release fixes a few critical bugs related to rate-limiting. We also added support for voice message receiving and new permissions relating to soundboards.

You can now use EmbedBuilder#setUrl to create multi-image embeds. To create multi-image embeds, simply create one embed for each image and set the same URL on all of them. The client automatically merges embeds with the same URL.

Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.8...v5.0.0-beta.9

Installation

Gradle

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

Maven

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

v5.0.0-beta.8: | Hotfix NullPointerException

Compare Source

Overview

This is a small hotfix release for an error introduced in beta 7.

Features

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.7...v5.0.0-beta.8

Installation

Gradle

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

Maven

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

v5.0.0-beta.7: | Customize Rate-Limiter

Compare Source

Overview

You can now use RestConfig to customize parts of the REST handling in JDA. This allows you to create custom rate-limiter implementations and make use of rate-limit proxy services such as http-proxy.

Rate-Limiter Customization (#​2307)

Using RestConfig, you can change parts of the REST handling. This allows you to append to the User-Agent, add custom headers, or even completely replace the existing Rate-Limiter handling:

RestConfig config = new RestConfig();
config.setUserAgentSuffix("custom suffix"); // Changes user-agent to "DiscordBot(JDA, ...) custom suffix"
config.setBaseUrl("https://proxy.example.com/api/v10"); // requests will now go through this endpoint, allowing custom rate-limits
config.setRateLimiterFactory(...); // change the handling of rate-limits

builder.setRestConfig(config); // then simply set it on your JDABuilder or DefaultShardManagerBuilder

This can also be useful to implement a different queue system for rate-limit handling. By default, JDA will always use the SequentialRateLimiter, which handles requests to the same rate-limit bucket in sequence to avoid messages being unordered. A custom implementation could replace this to run requests in parallel.

To implement a custom rate-limiter, use the existing RestRateLimiter interface and implement the required methods as documented. Your implementation will be provided with Work instances to handle.

Member Flags (#​2417)

You can now access the flags on members and modify them. This allows to check if a member has rejoined the guild or passed onboarding. The rejoin flag is not entirely reliable, since Discord has only started tracking rejoins recently. Members who rejoined years ago will not have this flag set.

With Member#modifyFlags, you can change some of these flags. Only a subset of the existing flags are modifiable.

EnumSet<MemberFlag> flags = member.getFlags();
flags.add(MemberFlag.BYPASS_VERIFICATION); // Member bypasses verification level on guild
member.modifyFlags(flags).queue();

Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.6...v5.0.0-beta.7

Installation

Gradle

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

Maven

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

v5.0.0-beta.6: | Messages in Stage Channels

Compare Source

Overview

This release adds support for messages and interactions inside stage channels.

New Features

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.5...v5.0.0-beta.6

Installation

Gradle

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

Maven

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

v5.0.0-beta.5: | Hotfix voice connection issues

Compare Source

Overview

This is a minor release with some important bug fixes. All bots relying on voice connections should apply this update as soon as possible.

Changes

Bug Fixes

Full Changelog: discord-jda/JDA@v5.0.0-beta.4...v5.0.0-beta.5

Installation

Gradle

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

Maven

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

v5.0.0-beta.4: | Audit Log Events and Silent Messages

Compare Source

Overview

This release adds support for recent Discord features, such as linked roles and silent messages. We also improved the user experience for shutting down, which should come in handy for anyone building reloadable plugins.

Add GuildAuditLogEntryCreateEvent (#​2380)

Discord has finally introduced an event for new audit log entries. This can be used for keeping track of all kinds of moderation relevant activity in a guild. However, to receive this event you must have the View Audit Logs permission and enable the GUILD_MODERATION intent (formerly GUILD_BANS).

Silent Messages (#​2392)

You can now send and receive messages which do not trigger desktop and mobile push notifications. This is done in the client by prefixing a message with @silent. In JDA you can use setSuppressedNotifications(true) to achieve the same. Note that @silent is not the correct way to create these messages with a bot, as it is a client only feature.

You can check the release pull request for more information: discord/discord-api-docs#5910

Await Shutdown (#​2269)

The shutdown logic has adapted to allow more consistent behavior. We've introduced jda.awaitShutdown() as a way to allow blocking until all JDA subsystems reach completion. Note that this might take a long time, depending on how long your RestAction queue is at the time.

The recommended way to gracefully shutdown is to define a maximum wait threshold and use it to cancel requests after some time:

// Initating the shutdown, this closes the gateway connection and subsequently closes the requester queue
jda.shutdown();
// Allow at most 10 seconds for remaining requests to finish
if (!jda.awaitShutdown(Duration.ofSeconds(10))) { // returns true if shutdown is graceful, false if timeout exceeded
    jda.shutdownNow(); // Cancel all remaining requests, and stop thread-pools
    jda.awaitShutdown(); // Wait until shutdown is complete (indefinitely)
}

In order to save CPU time, we make use of conditional variables for all of our wait loops internally. This is much more efficient than using sleep polling, like suggested in the past.

New Features

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/net.dv8tion-jda-5.x branch from 8673fc0 to 5a0c48d Compare July 3, 2024 17:28
@rettichlp rettichlp merged commit 0065f51 into develop Jul 3, 2024
1 check passed
@rettichlp rettichlp deleted the renovate/net.dv8tion-jda-5.x branch July 3, 2024 17:31
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@rettichlp