Hey guys! Well, I'm here to criticise BungeeCord, and try to give possible suggestions to fix the issues. You might say i love bungeecord its da best or something ugly like that. But, try to look at this post unbiased, please, as there are many issues with BungeeCord that almost everyone knows and ignore it, just because BungeeCord is too popular. So, moving on: 1. Open-source code, but not open-minded This is something that BungeeCord needs to improve. Although the source code is available for everyone to see and improve upon, however, for a long time md_5 hasn't been really open to contributors outside of the eco-system, and this makes BungeeCord not really open in its codebase. Like, all the codes are from md_5, and if you are reading this, md_5, I can see that you are (almost) never going to merge a pull request if it was made by someone outside of the SpigotMC dev teams, despite them having a real advantage over the old code. Oh, and by the way, md_5 is even hostile to simple fixes to bad code. md_5 is almost always rude in his words, and you can probably see that if he replies to this post. 2. Not so lightweight API I guess everyone knows this. BungeeCord has a heavyweight underlying API which makes it easily outperformed by other L7 Minecraft proxy implementation. Well, I'm gonna skip this as many people know it. Please revamp, or completely renew the underlying API. 3. Does not support non-Vanilla clients natively Well, again, literally all people around the world knows this. md_5 does not even want to support Forge, so don't talk about Fabric. I can't think of a fix for a big project like this, though, sadly. 4. Code quality? Bruh, seriously, don't even talk about this. The code looks messy, and the code quality is not that high either. If BungeeCord uses FindBugs/SpotBugs there would be something like 100+ bugs reported. Is md_5 gonna improve the code, or is md_5 going to use @SuppressFBWarnings? 5. Easily affected by attacks Well, I wouldn't blame BungeeCord for being affected heavily by attacks, considering the popularity of the project. However, these attacks could easily be mitigated even without the use of plugins, it's just that md_5 doesn't want to make BungeeCord even worse in its weight. Also, I'm not talking about bot attacks. I'm talking about packet exploits. These can be mitigated easily by not making the console spam exceptions, and for advanced packet exploits... I'm not a protocol expert, so it's time for md_5 to find out the solution. 6. Performance Well, uhm... By switching to Waterfall you will be able to get at least 5% performance increase. Guaranteed. BungeeCord is too heavyweight, and this is the main factor that causes BungeeCord to be laggy. By using multithreading, BungeeCord can be easily an asynchronous software implementation, and thus bringing the performance up at least by 20%. Well, I wrote this in something like 15 minutes, so don't blame me for having a post with lower quality. Please review this seriously, md_5, and one day I'll switch from (the speed of an object moving) back to BungeeCord.