Announcement Announcing the end of life of Waterfall

Announcing the end of life of Waterfall​

As many of you might have noticed, Waterfall hasn't received much love from our team and the great contributor community in the past years. We have also seen less and less traffic in the support channels on Discord. Additionally, Mojang is making huge investments into the core engine of the game which results in big and complicated changes to the inner workings of the game. While these changes are very welcome and we have been pushing for some of them for years, they also mean that there is a bunch of work ahead of us for adapting our projects to these changes.
We don't think we can find enough people from our team and contributors to put that work into Waterfall anymore, we want to focus our efforts on our flagship projects Paper and Velocity. We also don't feel comfortable putting out something that doesn't live up to our standards in terms of the testing that went into it.
That's why we decided that we want to officially announce the end of life of Waterfall.

What is changing?​

Starting today, big red angry banners will appear on the Waterfall sub-pages of our documentation site and our website. These are pointing here and act as a way to inform everybody of what is going on.
Other than that, there will be no direct change. All documentation will still be accessible, you will still be able to download all versions of Waterfall as usual.
What will change is that you will see even more sporadic updates. You also shouldn't count on updates to new Minecraft versions, although we aren't ruling that out at this time.

What should I do?​

Migrate to Velocity! All the knowledge the people who originally worked on Waterfall gained has been put into Velocity, a proxy solution that was built from the ground up with performance, stability and security in mind. You can learn how to get started with Velocity on our documentation site.
You can find plugins compatible with Velocity on Hangar, our new plugin repository.
If you encounter any issues while migrating to Velocity, feel free to post on the forums or our Discord, we are happy to help!

Please join our discord community if you have any concerns about this announcement.
 

Announcing the end of life of Waterfall​

As many of you might have noticed, Waterfall hasn't received much love from our team and the great contributor community in the past years. We have also seen less and less traffic in the support channels on Discord. Additionally, Mojang is making huge investments into the core engine of the game which results in big and complicated changes to the inner workings of the game. While these changes are very welcome and we have been pushing for some of them for years, they also mean that there is a bunch of work ahead of us for adapting our projects to these changes.
We don't think we can find enough people from our team and contributors to put that work into Waterfall anymore, we want to focus our efforts on our flagship projects Paper and Velocity. We also don't feel comfortable putting out something that doesn't live up to our standards in terms of the testing that went into it.
That's why we decided that we want to officially announce the end of life of Waterfall.

What is changing?​

Starting today, big red angry banners will appear on the Waterfall sub-pages of our documentation site and our website. These are pointing here and act as a way to inform everybody of what is going on.
Other than that, there will be no direct change. All documentation will still be accessible, you will still be able to download all versions of Waterfall as usual.
What will change is that you will see even more sporadic updates. You also shouldn't count on updates to new Minecraft versions, although we aren't ruling that out at this time.

What should I do?​

Migrate to Velocity! All the knowledge the people who originally worked on Waterfall gained has been put into Velocity, a proxy solution that was built from the ground up with performance, stability and security in mind. You can learn how to get started with Velocity on our documentation site.
You can find plugins compatible with Velocity on Hangar, our new plugin repository.
If you encounter any issues while migrating to Velocity, feel free to post on the forums or our Discord, we are happy to help!

Please join our discord community if you have any concerns about this announcement.
I made a point of logging into the forum that I hadn't used in a while to say that:

Waterfall is really good!
 
Please, can you revive it? This is very important for my server! My server has been keen to use Waterfall, it is really very useful and convenient, the contribution to everyone is not small!why!:cry:
 
Waterfall won't be revived as there is no interest by developers to actively work on it. It is recommended to migrate to Velocity, which is more actively developed.
 
Please, can you revive it? This is very important for my server! My server has been keen to use Waterfall, it is really very useful and convenient, the contribution to everyone is not small!why!:cry:
I switched very easily from Waterfall to Velocity almost a year ago and I can say that it is 100% worth it. There are no downsides to switching. Yes, you can argue that there are a few plugins that you have currently that might not work on Velocity, but there are many alternatives that do work on both, just do a little search. In fact, when I switched I actually found even better plugins that I did not know about.
 
Please, can you revive it? This is very important for my server! My server has been keen to use Waterfall, it is really very useful and convenient, the contribution to everyone is not small!why!:cry:
I switched from Waterfall to Velocity, and the whole process took less than 10 minutes.
It's really too easy
Most of the plugins I use, such as LuckPerms, miniMOTD, TAB, etc., have versions adapted to Velocity.
 
I've posted warnings about this already on Discord, etc, however, I'm having a corneal transplant on the 6th (tomorrow, as I forgot to finish this post, in lieu of the blog I wanted to start to address this situation (and ramble on about other things)) and will likely not be around when 1.21 is released, which generally means that as the sole person who has been dealing with waterfall for the past few years on our side, I am not going to be around to setup the build system to pump out a build, or to be able to merge PRs, etc.

A large part of the reality is that this project has been in a state of limbo for a while, I was and am somewhat planning to create a blog post regarding this at some point, and, with a lack of community support, there's just little ability from us to work on the large things that I wanted to work on. Before I got really ill a few years ago, I worked on disabling entity metadata rewriting for the server, which allowed some reductions in the work the proxy needs to do, but, also, allowed for a bit more support for forge mods, this was, however, a headache in which I spent further weeks of work to get the thing to work in an environment where plugins dip into and screw with internals instead of API.

There have been many projects over the past few years I've wanted to touch on, but are generally thwarted because I cannot get the community support in this, as supporting Bungee itself is generally more lucrative. So I do not have the pull needed to steer this project in the direction it needs to go, which, generally places a huge damper on any large project I come up with that would make a difference, vs just bodge fixes.

My illness in 2019 had a pretty huge hit on my life, one that I'm still recovering from, being diagnosed with Keratoconus after losing usable vision in my left eye was just yet another hit. The surgery for a corneal transplant is a huge step in the right direction for getting stuff back on track, followed by some stuff I'm hoping will align over the next few months that will hopefully lead to me returning to a full-time role in due course.

I joined the PaperMC team eons ago as it was fun, and even though I get no real compensation for working on this project, I figured, I loved the community, I loved programming, and it was something to do which might look nice on my CV. Many years later, I'm still here, my role within the org has tilted more towards leadership as we've grown. Working on projects like Paper and Velocity is fun because I still get to toss out bits of code here and there, run the debugging sessions I loved to treat as puzzles (even if the scope of the issues might lead to early balding), I get to work with a team in which we can collab on ideas and pull off some pretty impressive feats, projects like the new bootstrapping API, the command API, in which while 90%+ of the effort belongs to the people who wrote and tested the code, I was able to aid and make decisions which I hope helped in allowing us and the consumers of the API we add to pull off some impressive things over the years.

The reality, however, for Waterfall, is a lot different. Pretty much any project starts with a "Can we pull this off with virtually 0 community support", because the reality is that for Waterfall, a lot of devs are not willing to break support with Bungeecord, and there's just little desire for them to work with us to add waterfall specific API to reduce their reliance on the internals I want to touch, because, well, the internals work and are unlikely to change in bungeecord. Many of the people I worked with and discussed Waterfall-related stuff related stuff ended up moving over to Velocity for the same reasons I once had an entire cry session to Tux over the position I felt I was in with Waterfall in terms of being unable to sail the ship. Issues like https://github.com/PaperMC/waterfall/issues/318 have long been a thorn in the neck, I already have a few ideas of how we could patch this, but, the testing cycle we'd need with plugins to see if we can even pull any of those fixes off is a huge motivational and time cost, and that's before we get into the potential wallet cost if I have to start diagnosing compatibility issues with commercial license plugins. Being unable to work on anything "real", just kinda demotivates me from the hours I'd need to spend on making this project able to survive within the projects moving infrastructure and fixing the smaller issues I've come across over the years which wouldn't involve potentially breaking plugins.