BungeeCord fork that aims to improve performance and stability.
Go to file
Shane Freeder 85f0a0c69a Capture some script failure states better
Ensures that failures of primarily applying patches during builds
should be passed up, this will need a better look over at some point
2020-11-09 01:35:40 +00:00
.github Update stale-bot config 2018-07-21 15:32:29 +01:00
BungeeCord@9c078b78c3 Updated Upstream (BungeeCord) 2020-11-09 01:29:11 +00:00
BungeeCord-Patches Updated Upstream (BungeeCord) (#579) 2020-11-09 00:29:41 +00:00
scripts Capture some script failure states better 2020-11-09 01:35:40 +00: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 fix critical formatting error 2019-03-17 14:29:47 -07: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 [CI-SKIP] Add plugin developers section in README.md (#556) 2020-09-17 17:22:25 +01:00
pom.xml Add pom for extra convienience 2016-11-26 20:59:15 +00:00
waterfall Capture some script failure states better 2020-11-09 01:35:40 +00:00

README.md

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 (Plugin Developers)


<repository>
    <id>papermc</id>
    <url>https://papermc.io/repo/repository/maven-public/</url>
</repository>
  • Artifact information:
<dependency>
    <groupId>io.github.waterfallmc</groupId>
    <artifactId>waterfall-api</artifactId>
    <version>1.16-R0.4-SNAPSHOT</version>
    <scope>provided</scope>
</dependency>

Or alternatively, with Gradle:

  • Repository:
repositories {
    maven {
        url 'https://papermc.io/repo/repository/maven-public/'
    }
}
  • Artifact:
dependencies {
    compileOnly 'io.github.waterfallmc:waterfall-api:1.16-R0.4-SNAPSHOT'
}

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

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.