Florian Spieß

> I feel like that could be a bit confusing I think it's more confusing for it not to work, which is why I'm suggesting it. > making an overload...

That isn't an issue because we have a limit to the number of cached events: ```java public static final long TIMEOUT_AMOUNT = 100; ``` https://github.com/DV8FromTheWorld/JDA/blob/6ba908ca54b1888211ffa754aa73098c3e77c0fd/src/main/java/net/dv8tion/jda/internal/handle/EventCache.java#L40 https://github.com/DV8FromTheWorld/JDA/blob/6ba908ca54b1888211ffa754aa73098c3e77c0fd/src/main/java/net/dv8tion/jda/internal/requests/WebSocketClient.java#L916

No there are no warnings about the event cache.

I need to read myself back in on this PR and make some decisions regarding which events to cache and if we can be smarter about it.

These cache settings raise the question of how `ThreadChannel#getParentChannel` is currently implemented. Why does it use a cache getter instead of a field?

You can get permissions without the special cases by using `PermissionUtil.getExplicitPermissions(...)`

PermissionUtil will likely not be updated until a new permission change is made by discord. This is likely to happen with the release of channel categories.

Since we've been waiting half a year for a change in channel permissions, I updated the handling for now to properly respect the current (bad) channel permission system. This is...

This has been resolved in release 3.5.1 I will keep this issue open until discord fixes their permissions

Available in [alpha 18](https://github.com/DV8FromTheWorld/JDA/releases/tag/v5.0.0-alpha.18)