Ivan Abarca

Even though I can get by [using the copy constructor](https://github.com/Discord4J/Discord4J/commit/e3f387fed4425a7a83520044d722024c1ae8b2d8#diff-446b6f1861d3391dc5343fe96648a5c8R703-R721), we might want to aim for a more elegant solution. So keeping this open for now.

Looking into this after quite a while 😓 . Most specs could have their `XSpecGenerator` annotated with: ```java @JsonSerialize(as = XSpec.class) @JsonDeserialize(as = XSpec.class) ``` Some considerations must be taken...

Applying a potential fix in the next release. I wonder if we could do better with the `RequestQueueFactory#buffering` [implementation](https://github.com/Discord4J/Discord4J/blob/370891784d4c7506a89bc4f00c7123fa33bee3fa/rest/src/main/java/discord4j/rest/request/RequestQueueFactory.java#L79-L83). Currently there's a 256 item buffer and if full, returns `EmitResult.FAIL_OVERFLOW`....

`gateway.logout()` needs to be subscribed with `subscribe` or `block` in order to disconnect and begin to release resources. Can you check if the issue persists after adding that? Beyond that,...

No issues, that's the recommended approach for a general use case. You would only have to spin multiple GatewayDiscordClients if you need to use different bot tokens. However if you...

Thanks for bringing this up, from what I can remember to explain the weirdness: In Discord4J 3.0, sharding/login process was done differently: - You had to attach all event listeners...

> we shouldn't be making a request with this ID regardless of how discord will respond. We're probably accidentally using Snowflake#asLong instead of asString somewhere. I think our Store or...