BungeeCord fork that aims to improve performance and stability.
Go to file
Techcable 2187ad029c
Always CAS the disconnecting variable when we disconnect.
When we changed the disconnect check to use proper concurrent behavior (using CAS), the disconnecting flag wasn't set the first time we disconnect because the OR short-circited the CAS.

Upstream doesn't have this issue because they don't set the flag in the if statement (with CAS), and therefore aren't short circuted.

I have no idea why this check was an OR statement in the first place, so maybe this will cause more crazy bugs.
2016-05-31 12:52:17 -06:00
BungeeCord@ec48077dbe Turn waterfall into a patch-based fork like Spigot and Paper (WIP) 2016-05-30 14:51:51 -06:00
BungeeCord-Patches Always CAS the disconnecting variable when we disconnect. 2016-05-31 12:52:17 -06:00
.gitignore Turn waterfall into a patch-based fork like Spigot and Paper (WIP) 2016-05-30 14:51:51 -06:00
.gitmodules Turn waterfall into a patch-based fork like Spigot and Paper (WIP) 2016-05-30 14:51:51 -06:00
applyPatches.sh Turn waterfall into a patch-based fork like Spigot and Paper (WIP) 2016-05-30 14:51:51 -06:00
LICENSE.txt Turn waterfall into a patch-based fork like Spigot and Paper (WIP) 2016-05-30 14:51:51 -06:00
README.md Turn waterfall into a patch-based fork like Spigot and Paper (WIP) 2016-05-30 14:51:51 -06:00
rebuildPatches.sh Turn waterfall into a patch-based fork like Spigot and Paper (WIP) 2016-05-30 14:51:51 -06:00

Waterfall

Waterfall is a fork of the well-known BungeeCord server teleportation suite.

Waterfall focuses on three main areas:

  • Stability: Waterfall aims to be stable. We will achieve this through making the code base testable and discouraging practices that lead to proxy lag.
  • Features: Waterfall aims to include more features than canonical BungeeCord.
  • Scalability: Waterfall should be able to handle a large number of concurrent players, given a reasonably modern CPU, memory, and good network connection.

Why fork BungeeCord?

Think of Waterfall as a principles fork.

Waterfall was forked because of the fact that upstream does not accept many contributions that are intended to better the ecosystem. Simply put, Waterfall aims to better the ecosystem by allowing changes to be exposed to a wider audience more quickly.

Waterfall will still track upstream BungeeCord and merge changes as needed.

Join us

  • Feel free to open a PR! We accept contributions.
  • Join us on IRC (irc.esper.net #waterfall, webchat).
  • Visit our forums on Aquifer.

Special Thanks To

YourKit-Logo

YourKit, makers of the outstanding Java profiler, supports open source projects of all kinds with their full-featured Java and .NET application profilers. We thank them for granting Waterfall an OSS license so that we can make our software the best it can be.