Bastian Oppermann

Results 49 issues of Bastian Oppermann

I've already suggested a design for an external cache module in https://github.com/Javacord/Javacord/issues/454#issuecomment-832957623. However, since this suggestion was not well received because of the immutability, this issue proposes a mutable external...

:sparkles: feature request
high priority
:hammer: breaking-change

In the wiki article https://javacord.org/wiki/basic-tutorials/interactions/components.html

medium priority

At the moment, the user cache is automatically enabled when the `GUILD_MEMBERS` intent is set. We should - offer an option to disable the user cache - offer a method...

medium priority

There are some reports about unusually high memory use from Javacord. We should take a look at what's causing it.

medium priority

We should mention that some colors are "reserved" by Discord as the default color. See https://github.com/Javacord/Javacord/issues/670

good first issue
📖documentation

![image](https://user-images.githubusercontent.com/5033001/92781911-d3186980-f3a4-11ea-8eb2-94959c11b31d.png) Here's the link from the screenshot: https://canary.discordapp.com/channels/151037561152733184/151326093482262528/693472922412646501 which points to this message: ![image](https://user-images.githubusercontent.com/5033001/92782101-fc38fa00-f3a4-11ea-9745-901992eb22b9.png)

:bug: bug
high priority

It should be possible to attach information to listeners. Together with the ability to modify listener execution order (https://github.com/Javacord/Javacord/issues/384), this can be very helpful in some cases. A generic solution...

improvement
low priority

> This idea came up in #383. It would be convenient to be able to give listener a "priority" to alter their execution order. A straight-forward solution would be to...

:sparkles: feature request
low priority

I'm thinking about something like this: ```java message.getReactionAddEventPipeline() .filter(event -> !event.getUser().isYourself()) .filter(event -> event.getEmoji().equalsEmoji("❌")) .map(ReactionAddEvent::getUser) .consume(user -> { // User clicked X }); ``` This is just my first idea...

:sparkles: feature request
low priority

The ratelimit manager has problems with account updates (username or avatar), because Discord ratelimits them differently.

:bug: bug
low priority