BungeeCord fork that aims to improve performance and stability.
Go to file
Jamie Mansfield a5e6cc087b
Farewell...
Today, Friday 17th August 2018, marks 2 years, 2 months, and 2 days since my first contribution
to the Waterfall project (that’s a total of 792 days!). Throughout that time, 3 major Minecraft
versions have been released, Waterfall has become the go-to for modded networks, and Sponge has
become a very viable option for servers - no longer lacking in implementation.

Before the Bukkit drama, I had written very little software for the server - though I’d written
a bunch of fairly basic client mods. I had run a bunch of servers however - I had very extensive
knowledge of the Classic server software, and I’d run a lot of bukkit servers. Though vanilla
has never really been my cup-of-tea, and ever since I started to do a lot of work with the server
my time playing the game has decreased. The truth is, I’ve never played any of those 3 major
releases that have come out since I’ve been maintaining Waterfall.

Sadly I have fallen out of love with the game, and don’t see myself likely to play it anytime soon.
However, I find a certain joy in writing software so I’ve stuck around - the communities I’ve landed
on are really great :D I’ve found projects to work on that are independent from Minecraft, yet keep
me within the same communities.

Today I work on a lot of software related to obfuscation and Java - namely Lorenz, Bombe, and Survey.
Though I’m also a web developer for Sponge, in addition to a bunch of other roles I’ve landed myself
(including advising a server migrating away from a nearly decade old codebase to Sponge). I’ve
recently been working on a website for some of my friends who are fundraising for charity.

I’ve never really made any money from any of the OSS development I’ve done, amounting to a total of
$30 from a BountySource I did as a one-off. Please don’t take that as a complaint though, I would be
developing software OSS or otherwise - I see it as a hobby, I find it fun. Which is why I’m not longer
the right person to maintain Waterfall - I no longer have need to, or find it fun - in fact merging
upstream changes is a time-consuming, monotonous task :(

Though this may all sound like I’ve hated maintaining Waterfall, which certainly isn’t the case - it's
just how I’ve felt as of late. Frankly, the wonderful community has kept me around for as long as I have.
It’s been really nice to talk to people that I may have fallen out-of-contact with, were it not for
Waterfall.

Maintaining Waterfall has been an honour, and I’m very proud that we’ve become the go-to for modded and
regarded as an analogue to Paper.

And with that, my notifications are going to significantly reduce :D And finally, I’d like to thank
@electronicboy for committing to maintaining Waterfall! Legend :)
2018-08-16 23:06:26 +01:00
.github Update stale-bot config 2018-07-21 15:32:29 +01:00
BungeeCord@9ea82e9541 Merge Upstream 2018-08-16 22:44:14 +01:00
BungeeCord-Patches Merge Upstream 2018-08-16 22:44:14 +01:00
fire-pit Revert to BungeeCord behaviour for the 'not direct byte buf' business 2017-10-23 19:53:51 +01:00
scripts Ensure that we checkout the submodules before patching(Fixes #262) 2018-07-24 16:57:08 +01:00
.gitattributes Add pom for extra convienience 2016-11-26 20:59:15 +00:00
.gitignore Use Log4J2 for logging and TerminalConsoleAppender for console 2017-09-24 15:14:52 +02:00
.gitmodules Turn waterfall into a patch-based fork like Spigot and Paper (WIP) 2016-05-30 14:51:51 -06:00
CONTRIBUTING.md Force Update 2016-07-16 22:01:56 -04:00
LICENSE.txt Turn waterfall into a patch-based fork like Spigot and Paper (WIP) 2016-05-30 14:51:51 -06:00
pom.xml Add pom for extra convienience 2016-11-26 20:59:15 +00:00
README.md Add waterfall command 2018-07-21 18:42:34 +01:00
waterfall Ensure that we checkout the submodules before patching(Fixes #262) 2018-07-24 16:57:08 +01:00

Waterfall Build Status

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.

How To (Server Admins)

Download a copy of Waterfall.jar from our buildserver here: Waterfall

Waterfall requires Java 8 or above.

How To (Compiling From Source)

To compile Waterfall, you need JDK8, git, bash, maven, and an internet connection.

Clone this repo, run ./waterfall b from bash, get jar from Waterfall-Proxy/bootstrap/target/

Join us

  • Feel free to open a PR! We accept contributions.
  • Join us on IRC (irc.spi.gt #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.