Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update dependency com.github.DV8FromTheWorld:JDA to v5.0.0-alpha.3 #4

Merged
merged 1 commit into from
Jan 9, 2022
Merged

Update dependency com.github.DV8FromTheWorld:JDA to v5.0.0-alpha.3 #4

merged 1 commit into from
Jan 9, 2022

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 8, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.github.DV8FromTheWorld:JDA v5.0.0-alpha.3 -> 5.0.0-alpha.3 age adoption passing confidence

Release Notes

DV8FromTheWorld/JDA

v5.0.0-alpha.3

Changelog
New Features
Changes
Removed
  • N/A

Full Changelog: discord-jda/JDA@v5.0.0-alpha.2...v5.0.0-alpha.3

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-alpha.3")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-alpha.3</version>
</dependency>

v5.0.0-alpha.2

Changelog
New Contributors
New Features
Changes
Removed

Full Changelog: discord-jda/JDA@v5.0.0-alpha.1...v5.0.0-alpha.2

Installation
Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-alpha.2")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-alpha.2</version>
</dependency>

v5.0.0-alpha.1

Welcome to the v5 alpha

While we are working through the alpha stage it is expected that things will not be completely hardened yet. Functionality may contain bugs. Docs will be may be missing for new features. Code is still subject to breaking changes. This is the edge of the edge, but this is where the new fun features are to play with. What life without a little danger? 😎

As such, we encourage you to jump in, update your bots, and play with the new feature, but also recognize that v5 is still very much a work-in-progress. We'll do our best to provide a bug free space, but there are additional breaking changes planned for v5, so keep an eye out! 🛠️

Branch Changes

In v4 we had 3 branches:

  • development - In-progress work for v4 releases went here. All PRs were pointed at this.
  • docs/development - Documentation only changes went here. This would get merged into development to keep development history cleaner
  • release - When a new release was made a merge commit was made from development to release. release always showed the code at the time of release for the latest release.

In v5 we are simplifying this:

  • development - This branch is being removed.
  • docs/development - This branch is being removed
  • release - This branch is being removed
  • master - This will be the primary and only branch. It will serve the same purpose that development did in v4, but with a more consistent naming expected by the community. All changes (PRs), regardless of their content, are to be made against this branch.

Additionally, just like with all major-revisions of JDA, the legacy code will be maintained.
As such, the contents of development are currently available on legacy/v4 and will be available there even after development is deleted. Any critical bug fixes that we backport to v4 will be made to legacy/v4.

Version Schema changes:

Starting with v5, we are changing how we handle versions.
The new version schema: <major>.<minor>.<revision>[-<classification>.<classificationRevision>]
Examples:

  • 5.0.0-alpha.1
  • 5.0.0-beta.14
  • 5.1.2

Historically, we versioned JDA as <major>.<minor>.<revision>_<buildVersion> where buildVersion was a continuously incremented number. This led us to have situations where we didn't make an actual release for a long time because developers could just update to the latest <buildVersion>, effectively rendering the normal versioning meaningless. As such, in v5 we have decided to create releases much more often and in doing so we are dropping the <buildVersion> identifier. As a note, these builds where the only part of the version that changed was the buildVersion were JDA's snapshot builds.

Going forward, we are no longer going to be publishing our snapshot builds. This means that not every commit will lead to a repository-published version. The only version that will be published are releases. Releases are when the actual version of JDA has been changed. Anything that is not a release is a snapshot.

Snapshot builds will still be available in 2 ways:

  1. Jitpack
  2. Jenkins CI via JAR downloads

Additionally, the snapshot builds have a slight variant on the new versioning scheme in terms of build assets. For snapshot builds the assets are versioned as <major>.<minor>.<revision>[-<classification>.<classificationRevision>]_<git-commit-7-char-hash>
Examples:

  • 5.0.0-alpha.1_d3fac3k
  • 5.0.0-beta.14_67ylgde
  • 5.1.2_fl1opac
Changelog
New Contributors
New Features
  • JDA now supports threads via the new ThreadChannel construct.
  • StageChannel is now its own type, not an extension of VoiceChannel
  • NewsChannel is now a full-fledge type, not just a subset of TextChannel via isNews()
  • AudioChannel now exist as an interface that contains the shared parts of VoiceChannel and StageChannel. The various parts of the audio system that dealt with channels now deal with AudioChannel instead of explicitly VoiceChannel
  • Introduced "attribute" interfaces that allow interop between concrete channel types:
    • IInviteContainer
    • IPositionableChannel
    • IPermissionContainer
    • ICategorizableChannel
    • etc
  • Introduced GuildChannel#getPermissionContainer to easily get access to an instance of IPermissionContainer for the current channel. In the majority of cases this method will simply return the same channel but cast to IPermissionContainer, but it can return other channels instead, like with ThreadChannel as ThreadChannel doesn't support IPermissionContainer and relies on its parent channel to determine permissions.
    • Additionally, you don't have to use this method. If you know the current GuildChannel instance you have implements IPermissionContainer you can just cast to it. No big deal. This getter is just here for simplicity without casting.
  • Unified channel events:
    We've simplified detecting and handling events for channels by replacing the type-specific events (like TextChannelCreateEvent) with unified events that fire for every channel. You can differentiate between the specific channel types as needed via event.getChannelType()
    • ChannelCreateEvent
    • ChannelUpdateXEvent (e.g: ChannelUpdateNameEvent)
    • ChannelDeleteEvent
  • Type-trimmed Channel Managers
    • ChannelManager
    • attributes
      • IPermissionContainerManager
      • IPositionableChannelManager
      • ICategorizableChannelManager
    • middleman
      • AudioChannelManager
      • BaseGuildMessageChannelManager
    • concrete
      • CategoryManager
      • NewsChannelManager
      • StageChannelManager
      • TextChannelManager
      • ThreadChannelManager
      • VoiceChannelManager
Changed
  • ActivityType.DEFAULT renamed to ActivityType.PLAYING
  • Many permissions were renamed or removed
    • MESSAGE_READ -> Removed. Use VIEW_CHANNEL instead.
    • MESSAGE_WRITE -> MESSAGE_SEND
    • USE_SLASH_COMMANDS -> USE_APPLICATION_COMMANDS
    • MANAGE_EMOTES -> MANAGE_EMOTES_AND_STICKERS
    • USE_PUBLIC_THREADS -> CREATE_PUBLIC_THREADS
    • USE_PRIVATE_THREADS -> CREATE_PRIVATE_THREADS
  • OptionData#addChoice(String, int) -> OptionData#addChoice(String, long)
  • MessageBulkDeleteEvent#getChannel now returns GuildMessageChannel instead of TextChannel
  • WebhookClient#getChannel and WebhookManager#getChannel now both return BaseGuildMessageChannel instead of TextChannel
Removed
  • All deprecated code from v4
  • ChannelManager#getType(). Use ChannelManager#getChannel()#getType()
  • ChannelManager#setNews. Use TextChannelManager#setType or NewsChannelManager#setType
  • ChannelAction#setNews. Use Guild#createNewsChannel
  • NewsChannel related methods removed from TextChannel as NewsChannel is a full-fledged entity now
    • TextChannel#follow -> NewsChannel#follow
    • TextChannel#crosspostMessage -> NewsChannel#crosspostMessage
  • Removed all <Type> specific channel events. Use the new Unified Channel events mentioned above.
    This includes:
    • <Type>ChannelCreateEvent (ex: TextChannelCreateEvent)
    • <Type>ChannelUpdate<Field>Event (ex: TextChannelUpdateNameEvent)
    • <Type>ChannelDeleteEvent (ex: TextChannelDeleteEvent)
  • Removed all <Context>Message<X>Events (ex: GuildMessageReceivedEvent)
    This includes:
    • Generic<Context>MessageEvent (ex: GenericGuildMessageEvent)
    • <Context>MessageReceivedEvent (ex: GuildMessageReceivedEvent)
    • <Context>MessageUpdateEvent (ex: GuildMessageUpdateEvent)
    • <Context>MessageDeleteEvent (ex: GuildMessageDeleteEvent)
    • <Context>MessageEmbedEvent (ex: GuildMessageEmbedEvent)
    • <Context>MessageReaction<X>Event (ex: GuildMessageReactionAddEvent)
    • etc

Full Changelog: discord-jda/JDA@v4.4.0...v5.0.0-alpha.1

Installation

With v5 we are finally moving back to Maven Central for our releases. m2.dv8tion.net will continue to host our v4 artifacts until the v4 LTS concludes, but going forward we will be publishing releases to Maven Central. For snapshot builds, please use jitpack.

Gradle
repositories {
    mavenCentral()
}
dependencies {
    implementation("net.dv8tion:JDA:5.0.0-alpha.1")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>5.0.0-alpha.1</version>
</dependency>

v4.4.0

This release is long overdue, but with it comes the decision to place v4 into LTS status.

Support for v4 will consist only of bug fixes from this point forward as development focus turns to v5. No additional features, documentation changes, or enhancements will be accepted for v4. Additionally, No changes to support the new GuildIntents.MESSAGE_CONTENT will be backported into v4. This shouldn't be a problem, as v4 handles things well, but it bares mentioning.

The LTS support timer will start once v5 reaches a level of maturity that we feel confident enough in, such that we would recommend transition to it for all developers. It will likely start once v5 hits beta and 6 months after that we will drop support for v4.

Going forward, we will be working on getting the v5.0.0 alpha builds out.

Also, Please take a moment to look at the deprecated features as they will all be removed in v5
New Features
Deprecation

All deprecated features in v4 will be removed in v5!
Detailed javadoc can be found in the deprecated tab of the docs

Installation

The release version is: 4.4.0_350
The latest version is: latest version

Gradle
repositories {
    mavenCentral()
    maven {
        name 'm2-dv8tion'
        url 'https://m2.dv8tion.net/releases'
    }
}
dependencies {
    implementation("net.dv8tion:JDA:4.4.0_350")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>4.4.0_350</version>
</dependency>
<repository>
    <id>dv8tion</id>
    <name>m2-dv8tion</name>
    <url>https://m2.dv8tion.net/releases</url>
</repository>
Changelog
New Contributors

Full Changelog: discord-jda/JDA@v4.3.0...v4.4.0

v4.3.0

In this release, we are adding support for the new interactions API for bots. You can now use slash-commands and buttons with your bot to enhance the integration into the Discord interface.

Some useful resources:

Keep in mind that Slash-Commands are a lot more limited and always require a response. You should make sure you understand the restrictions implied by slash-commands before converting your existing implementations. I wrote some guidelines you should be aware of in this gist: Slash Command Limitations

Support for stage channels will be added in the next release. In the meantime, just imagine a place where it's implemented!

New Features

You can check the full list of pull requests for more details:
4.3.0 Milestone

Thank you all for your contributions!

Deprecation

Detailed javadoc can be found in the deprecated tab of the docs

Installation

The release version is: 4.3.0_277
The latest version is: latest version

Gradle
repositories {
    mavenCentral()
    maven {
        name 'm2-dv8tion'
        url 'https://m2.dv8tion.net/releases'
    }
}
dependencies {
    implementation("net.dv8tion:JDA:4.3.0_277")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>4.3.0_277</version>
</dependency>
<repository>
    <id>dv8tion</id>
    <name>m2-dv8tion</name>
    <url>https://m2.dv8tion.net/releases</url>
</repository>

v4.2.1

With this release, we are addressing the sunset of the jcenter repository. (Read More)
We switched our release to a custom solution which is now hosted on https://m2.dv8tion.net/releases
See below in the Installation section for further details on the new repository.

Slash Commands, Stage Channels, and API v8 are going to be addressed in 4.3.0.

New Features

You can check the full list of pull requests for more details:
4.2.1 Milestone

Thank you all for your contributions!

Deprecation

Detailed javadoc can be found in the deprecated tab of the docs

Installation

The release version is: 4.2.1_253
The latest version is: latest version

Gradle
repositories {
    mavenCentral()
    maven {
        name 'm2-dv8tion'
        url 'https://m2.dv8tion.net/releases'
    }
}
dependencies {
    implementation("net.dv8tion:JDA:4.2.1_253")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>4.2.1_253</version>
</dependency>
<repository>
    <id>dv8tion</id>
    <name>m2-dv8tion</name>
    <url>https://m2.dv8tion.net/releases</url>
</repository>

v4.2.0

All support for AccountType.CLIENT has been removed. We can no longer support this API as it has diverged too much from the bot API.

In this release, we have to take a look at the new Discord API changes. As of late discord has been putting a lot of work into the privacy protection of their users. Unfortunately, that also includes limiting the data available to bots.
Bots are now required to explicitly state which features they intend to use by providing a set of GatewayIntents.

Additionally, bots should no longer directly depend on the cache of users/members with methods like getUserById() and getMembers(). You should now use lazy loading and load members through methods like retrieveMemberById or retrieveMembersByPrefix.

The old default behavior was to perform chunking on startup (explained in wiki article below). However, chunking is now a privileged feature which bots should not depend on. For this reason, we deprecated the old JDABuilder (and DefaultShardManagerBuilder) constructors in favor of new factory methods:

I've added a new wiki page that explains this in more detail: Gateway Intents and Member Cache Policy.

We have switched to the new domain discord.com. This will be required as of November 7, 2020.

New Features
  • GatewayIntents
  • MemberCachePolicy
  • Invite events
  • Mention Whitelist
  • RestAction timeout/deadline

You can check the full list of pull requests for more details:
4.2.0 Milestone

Thank you all for your contributions!

Deprecation

Detailed javadoc can be found in the deprecated tab of the docs

Installation

The release version is: 4.2.0_168
The latest version is: version

Gradle
repositories {
    jcenter()
}
dependencies {
    compile("net.dv8tion:JDA:4.2.0_168")
}
Maven

The jcenter repository now only works with https! Please change your URL from http to https

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>4.2.0_168</version>
</dependency>
<repository>
    <id>jcenter</id>
    <name>jcenter-bintray</name>
    <url>https://jcenter.bintray.com</url>
</repository>

v4.1.1

A lot of people use nested callbacks for things like sending private messages or adding reactions:

@&#8203;Override
public void onMessageReceived(MessageReceivedEvent event) {
  if (event.getMessage().getContentRaw().equals("!hello")) {
    user.openPrivateChannel().queue(
      channel -> channel.sendMessage("Hello Friend").queue(null,
        error -> event.getChannel().sendMessage("Failed to send message!").queue()));
  }
}

This gets very hard to read and maintain. Instead you can use something like submit() which returns a CompletableFuture to allow using continuations such as thenCompose and similar. This is great and all but that API is rather bad as it will swallow any errors by default and the error handling methods are not very nice.
We added a few new operators for common actions on RestAction:

  • map
    Convert the result of the RestAction to a different value
  • flatMap
    Chain another RestAction on the result
  • delay
    Delay the element of the previous step

Let's look at the same example using the new flatMap operator:

@&#8203;Override
public void onMessageReceived(MessageReceivedEvent event) {
  if (event.getMessage().getContentRaw().equals("!hello")) {
    user.openPrivateChannel()
           .flatMap(channel -> channel.sendMessage("Hello Friend"))
           .queue(null, error -> event.getChannel().sendMessage("Failed to send message!").queue()));
  }
}

This can be expanded to even more complicated chains:

@&#8203;Override
public void onMessageReceived(MessageReceivedEvent event) {
  if (event.getMessage().getContentRaw().equals("!hello")) {
    event.getChannel().sendMessage("I'll contact you in 10 seconds") // MessageAction
      .delay(Duration.ofSeconds(10)) // delay next flatMap by 10 seconds
      .flatMap(m -> user.openPrivateChannel()) // RestAction<PrivateChannel>
      .flatMap(channel -> channel.sendMessage("Hello Friend, this will self destruct in 30 seconds")) // RestAction<Message>
      .delay(Duration.ofSeconds(30)) // delay next flatMap by 30 seconds
      .flatMap(Message::delete) // RestAction<Void>
      .queue(null, error -> event.getChannel().sendMessage("Failed to send message!").queue()));
  }
}

You can imagine how this would look with just queue/queueAfter:

@&#8203;Override
public void onMessageReceived(MessageReceivedEvent event) {
  if (event.getMessage().getContentRaw().equals("!hello")) {
    event.getChannel().sendMessage("I'll contact you in 10 seconds").queue(m ->
      user.openPrivateChannel().queueAfter(10, TimeUnit.SECONDS, channel -> 
        channel.sendMessage("Hello Friend, this will self descruct in 30 seconds").queueAfter(30, TimeUnit.SECONDS,
          message -> message.delete().queue(),
          error -> event.getChannel().sendMessage("Failed to send message!").queue()
        )
      )
    );
  }
}

We also changed the implementation for the Rate Limiter in JDA which will now properly keep track of the "new" X-RateLimit-Bucket header to track which endpoints share the same rate-limit. This also means that JDA will now allow multiple requests to the same path while they follow different HTTP methods. For the user this just means, JDA now has a better understanding of how discord will limit your requests.

The new rate-limiter also has improved logging. You can now see which routes have what rate-limit by setting the logging level of net.dv8tion.jda.internal.requests.RateLimiter to trace. This will log messages such as this:

Updated bucket 80c17d2f203122d936070c88c8d10f33:guild_id:125227483518861312:webhook_id to (4/5, 4408)

The numbers at the end have this meaning (remaining requests/allowed requests in the reset time, milliseconds until reset).
The long bucket id is composed of the hash and the major parameters of the request. You can figure out which hash is for which bucket fairly quickly by looking for the corresponding cache log:

Caching bucket hash POST/channels/{channel_id}/messages -> 80c17d2f203122d936070c88c8d10f33
New Features
  • RestAction operators (flatMap, map, delay)
  • JDABuilder#setMaxBufferSize (same for shard manager)
  • Message#suppressEmbeds and Message#getFlags
Deprecation

Detailed javadoc can be found in the deprecated tab of the docs

Installation

The release version is: 4.1.1_101
The latest version is: version

Gradle
repositories {
    jcenter()
}
dependencies {
    compile "net.dv8tion:JDA:4.1.1_101"
}
Maven

The jcenter repository now only works with https! Please change your URL from http to https

<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>4.1.1_101</version>
</dependency>
<repository>
    <id>jcenter</id>
    <name>jcenter-bintray</name>
    <url>https://jcenter.bintray.com</url>
</repository>
Pull Requests

You can view the 4.1.1 Milestone for a list of accepted pull requests for this release. Thank you to everyone who contributed!

v4.1.0

We added support for lazy loading and now allow to disable guild subscriptions!

To enable lazy loading you have to configure a ChunkingFilter on your builder of choice [1]. Lazy loading means that JDA will not attempt to request the entire member list of a guild before starting to send events. Instead, members will be loaded on their first activity and members who are never active will never be loaded into cache.

new JDABuilder(TOKEN)
    .setChunkingFilter(ChunkingFilter.NONE) // don't chunk any guilds
    .build();

1) Example how to enable lazy loading

The more extreme choice is to disable guild subscriptions [2]. This feature completely disables member and user cache for the shard/jda session. Note that if you need methods like Guild#getMembers or similar things that require knowledge of the entire member list this is not something you should be using. JDA cannot determine the size of a guild or member join/leave with this disabled. The benefit of this is a greatly reduced memory footprint with the disadvantage of losing member state tracking.

new JDABuilder(TOKEN)
    .setGuildSubscriptionsEnabled(false)
    .build();

2) Example how to disable guild subscriptions

A footnote is that CacheFlag.VOICE_STATE can still be tracked and users in voice channels will still be loaded into cache when this cache flag is enabled. This is useful for music bots that want to leave a voice channel if they are alone.

You can now ignore specific ErrorResponse failures more easily. With ErroResponseException.ignore(...) you can create a failure consumer that drops any ErrorResponseException for the specified set of responses. [3]

import static net.dv8tion.jda.api.exceptions.ErrorResponseException.ignore;
import static net.dv8tion.jda.api.requests.ErrorResponse.*;

message.delete().queue(null, ignore(UNKNOWN_MESSAGE)); // ignore if message doesn't exist anymore
message.delete().queue(null, ignore(Logger::error, UNKNOWN_MESSAGE)); // ignore otherwise log

3) Example how to ignore UNKNOWN_MESSAGE errors

New Features
  • Lazy Loading and disable guild subscriptions
  • Readonly support for custom status
  • Member#getActiveClients
  • ErrorResponseException.ignore(...)
Deprecation

Detailed javadoc can be found in the deprecated tab of the docs

  • GuildUnavailableException, Guild#isAvailable this is no longer used, unavailable guilds are no longer in the guild cache. You can check if a guild is unavailable with JDA#getUnavailableGuilds
  • Guild#retrieveVanityUrl replace with Guild#getVanityUrl
  • Invite#getCreationTime replace with Invite#getTimeCreated
  • JDA#getVoiceChannelByName replace with JDA#getVoiceChannelsByName
  • ShardManager#setGame replace with ShardManager#setActivity
  • SessionController#getGatewayBot replace with SessionController#getShardedGateway
Incubating
  • AccountType#CLIENT this is most likely going to break soon with impending changes to the gateway
  • JDABuilder(AccountType) this will be removed when AccountType#CLIENT breaks in the future
  • Activity#watching, ActivityType#WATCHING this is not officially supported by the API but currently usable
  • ActivityType#CUSTOM_STATUS this is currently not usable for bots and can only be seen on other users
  • AudioManager#getSpeakingMode, AudioManager#setSpeakingMode this is not a confident implementation and should be used with care
Installation

The release version is: 4.1.0_81
The latest version is: version

Gradle
repositories {
    jcenter()
}
dependencies {
    compile "net.dv8tion:JDA:4.1.0_81"
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>4.1.0_81</version>
</dependency>
<repository>
    <id>jcenter</id>
    <name>jcenter-bintray</name>
    <url>https://jcenter.bintray.com</url>
</repository>
Pull Requests

You can view the 4.1.0 Milestone for a list of accepted pull requests for this release. Thank you to everyone who contributed!

v4.0.0

This release bumps the major version because we have done a number of breaking changes. The most notable ones are:

  • Package rename core -> api
  • Removed GuildController
  • Renamed getX(): RestAction to retrieveX(): RestAction
  • Added @Nonnull and @Nullable annotations

More can be found in the migration guide.

The plan for version 3.X is to keep updating it with bug fixes until 01/01/2020. We recommend migrating your codebase before then.

New Features
  • MarkdownUtil A utility to easily apply markdown to text
  • MarkdownSanitizer A state-machine to sanitize discord markdown
  • GatewayPingEvent An event for updates to the gateway ping
  • ApplicationInfo#getTeam Team support in applications
  • Message#getMentionedXBag(): Bag<X> Bag accessors for mentions to check for duplicates
  • Guild#getVanityCode and Guild#getVanityUrl
  • Guild#getBoostTier, Guild#getBoostCount, and Guild#getBoosters
  • Guild#getBannerId and Guild#getBannerUrl
  • Guild#getMaxBitrate and Guild#getMaxEmotes
  • Guild#getMaxMembers and Guild#getMaxPresences
  • Guild#getDescription
  • Member#getTimeBoosted
  • AudioReceiveHandler#handleEncodedAudio and AudioReceiveHandler#canReceiveEncoded
  • AudioReceiveHandler#includeUserInCombinedAudio
  • Member#ban, Member#kick, Member#mute, Member#deafen, and Member#modifyNickname
  • Guild#getGuildChannelById and JDA#getGuildChannelById
  • Guild#kickVoiceMember
  • MessageChannel#getHistoryFromBeginning
  • Member#getOnlineStatus(ClientType)
  • ReactionEmote#isEmoji, ReactionEmote#getAsCodepoints, and ReactionEmote#getEmoji
  • AudioManager#setSpeakingDelay
  • JDA#getUserByTag, ShardManager#getUserByTag, and Guild#getMemberByTag
  • GuildChannel#upsertPermissionOverride
  • JDABuilder#setVoiceDispatchInterceptor and DefaultShardManagerBuilder#setVoiceDispatchInterceptor
  • CacheView#forEachUnordered, CacheView#applyStream, CacheView#acceptStream, and CacheView#lockedIterator
  • JDA#getRestPing
  • PaginationAction#skipTo
  • Support for StoreChannel
  • New message types
  • Lots of new events and setters on managers
Deprecation
  • Emote#hasRoles -> Emote#canProvideRoles
  • Guild#retrieveVanityUrl -> Guild#getVanityCode
  • Invite#getCreationTime -> Invite#getTimeCreated
  • JDA#getVoiceChannelByName -> JDA#getVoiceChannelsByName
  • DefaultShardManagerBuilder#setEventManager -> DefaultShardManagerBuilder#setEventManagerProvider
  • ShardManager#setGame -> ShardManager#setActivity
  • SessionController#getGatewayBot -> SessionController#getShardedGateway
Incubating
  • JDABuilder(AccountType)
  • Activity.watching
  • AudioManager#setSpeakingMode and AudioManager#getSpeakingMode
Installation

The release version is: 4.0.0_39
The latest version is: version

Gradle
repositories {
    jcenter()
}
dependencies {
    compile "net.dv8tion:JDA:4.0.0_39"
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>4.0.0_39</version>
</dependency>
<repository>
    <id>jcenter</id>
    <name>jcenter-bintray</name>
    <url>https://jcenter.bintray.com</url>
</repository>

v3.8.3

In this version we only updated the OkHTTP dependency to the stable 3.13.0 release.

Gradle
repositories {
    jcenter()
}
dependencies {
    implementation("net.dv8tion:JDA:3.8.3_464")
}
Maven
<dependency>
    <groupId>net.dv8tion</groupId>
    <artifactId>JDA</artifactId>
    <version>3.8.3_464</version>
</dependency>
<repository>
    <id>jcenter</id>
    <name>jcenter-bintray</name>
    <url>http://jcenter.bintray.com</url>
</repository>

v3.8.2

Important Notice

Recently we have started work on the new major version of JDA
This release signals the end of JDA v3's lifecycle in which we will only be fixing critical issues for the supported timeframe. Once v4 becomes the new stable release we will continue fixing issues with v3 for 6 months to give people with a huge codebase enough time for the conversion. The current expected time for the JDA version 4 release is mid May.

Currently JDA version 4 is in its alpha stadium. This means it receives breaking changes which are not yet supported by 3rd party extensions like lavalink. Once version 4 reaches its beta stadium we will make efforts to help extension developers to adapt to the new ABI provided as soon as possible. We attempt to make a clear separation between what we consider API and internal. We expect extensions to only target the API side of JDA in the future to reduce the possibility of causing incompatibilities.

New features and enhancements will only be coming to JDA 4. This includes new features of Discord as well as overhead reduction such as the changes done to CacheView. One of the major changes coming here is the removal of client-only features such as group channels/messages. We will however continue to support using JDA with AccountType.CLIENT but it will be reduced to features available to bot accounts.

To track what is happening with JDA 4 you can take a look at the milestone: v4

Pull Requests
PR Description
#​793 Read-only MessageActivity support
#​795 Add Guild#getChannels for convenience
#​811 Added setPresence to ShardManager and improved documentation consistency
#​814 Added appendCodeLine(CharSequence text)
#​819 Add ChannelAction#setPosition(Integer)
#​820 Close socket on malformed zip data
#​825 Added copying of the slowmode when cloning a channel
#​826 Hacktoberfest Changes
#​827 Don't check admin on permission overrides
#​843 Update OkHTTP to 3.12.0
#​849 Create User#getAsTag
#​887 Add MESSAGE_ADD_REACTION to text only permissions
#​896 Ignore alpha when comparing colors in MessageEmbed

Thank you all for your contributions!

Versions

Latest version: Download

The latest release build: 3.8.2_459

Changelog

Additions

  • Guild#getChannels to get the display order of the channels in a guild
  • MessageBuilder#appendCodeLine for more intuitive monospace usage
  • ShardManager#setPresence to update both game an online-status in one request
  • ChannelAction#setPosition for applying a channel position before its creation
  • User#getAsTag for easy retrieval of Minn#​6688 format
  • MessageActivity support for spotify and game invites

Changes

  • The WebSocket will now reconnect when malformed data is received for better recovering
  • MessageEmbed#equals now only checks RGB value of the raw color instead of RGBA

Fixes

  • VoiceJoin events now fire with updated muted/deafened status
  • Slowmode property is now copied with Channel#createCopy
  • ContextException are now fired properly again
  • The ADMINISTRATOR permission is no longer checked when set on permission overrides
Gradle
repositories {
    jcenter()
    // Required for OkHTTP 3.13.0-SNAP

</details>

---

### Configuration

📅 **Schedule**: 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.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by [WhiteSource Renovate](https://renovate.whitesourcesoftware.com). View repository job log [here](https://app.renovatebot.com/dashboard#github/ryzech/smpcore).

@renovate renovate bot force-pushed the renovate/com.github.dv8fromtheworld-jda-5.x branch 3 times, most recently from b00b8df to 6453b97 Compare January 9, 2022 05:58
@renovate renovate bot changed the title Update dependency com.github.DV8FromTheWorld:JDA to v5.0.0-alpha.3 Update dependency com.github.DV8FromTheWorld:JDA to v5.0.0-alpha.3 - autoclosed Jan 9, 2022
@renovate renovate bot closed this Jan 9, 2022
@renovate renovate bot deleted the renovate/com.github.dv8fromtheworld-jda-5.x branch January 9, 2022 11:53
@renovate renovate bot changed the title Update dependency com.github.DV8FromTheWorld:JDA to v5.0.0-alpha.3 - autoclosed Update dependency com.github.DV8FromTheWorld:JDA to v5.0.0-alpha.3 Jan 9, 2022
@renovate renovate bot restored the renovate/com.github.dv8fromtheworld-jda-5.x branch January 9, 2022 14:06
@renovate renovate bot reopened this Jan 9, 2022
@renovate renovate bot force-pushed the renovate/com.github.dv8fromtheworld-jda-5.x branch 3 times, most recently from dfce482 to a45bd82 Compare January 9, 2022 21:14
@renovate renovate bot force-pushed the renovate/com.github.dv8fromtheworld-jda-5.x branch from a45bd82 to 3d44c66 Compare January 9, 2022 21:29
@ryzech ryzech merged commit ada3b80 into main Jan 9, 2022
@renovate renovate bot deleted the renovate/com.github.dv8fromtheworld-jda-5.x branch January 9, 2022 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.

None yet
2 participants
@ryzech @renovate-bot