Keeps causing Discord Extension to loopFixed
With this loaded, Discord Extension keeps looping with:

[Discord Extension] Discord socket opened!
12:22 AM
[Discord Extension] Your bot was found in 1 Guilds!
Okay, so even more weird. I add a bot to one server and paste the token in for that bot and this is what causes the looping. I then remove that bot from said Discord, add it to another and then it connects fine. It's only 1 Discord server it loops for. Why would this be?

Merged post

Reading this, seems to be a similar issue in another language though.

We have 13k members in our Discord so maybe something needs to be fixed with this plugin for larger servers?

https://github.com/sm00th/bitlbee-discord/issues/159
Hi Ryz0r,

If there isn't more information being printed in your console then this looks more to be a Discord Extension issue instead of Discord Core. You should probably open an issue over there.

MJSU
Only happens when Discord Core is loaded and attempting to make connection. It works on smaller servers but ones with a lot of people it doesn't.
Do you have other plugins that use the Discord Extension without issue?
Yes, I've tested it with a couple others and it works fine.
Can you try version 0.14.5 and let me know what is displayed in console
It's not failing to connect. It's connecting, but just keeps looping.

9:52 PM
[Discord Extension] Discord socket opened!
9:52 PM
[Discord Extension] Your bot was found in 1 Guilds!
9:52 PM
[Discord Extension] Discord socket opened!
9:52 PM
[Discord Extension] Your bot was found in 1 Guilds!

When I move it to a smaller server it will say something like "Connected to X server"


Merged post

9:54 PM
Loaded plugin Discord Core v0.14.5 by MJSU
9:54 PM
[Discord Extension] Discord socket opened!
9:54 PM
[Discord Extension] Your bot was found in 1 Guilds!
9:54 PM
[Discord Extension] Discord socket opened!
9:54 PM
[Discord Extension] Your bot was found in 1 Guilds!
Can you add me on discord MJSU#0814. I would like to give you a version with a bunch of debug in it so we can get to the root of the problem.
Added you
This issue has been resolved in version 0.14.6. 
Locked automatically