Sus

.gitattributes

@@ -0,0 +1,2 @@
+# Ensuring github workflows eol for all platform is lf
+* eol=lf

.gitignore

@@ -1,4 +1,4 @@
-Travertine-Proxy
+FlameCord-Proxy
 
 # intellij
 *.iml
@@ -7,3 +7,5 @@ Travertine-Proxy
 .idea/
 out/
 
+.project
+.settings

.gitmodules

@@ -1,3 +1,4 @@
 [submodule "Waterfall"]
 	path = Waterfall
-	url = https://github.com/WaterfallMC/Waterfall.git
+
+	url = https://github.com/LinsaFTW/Waterfall.git

CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at our [Discord server](https://discord.gg/VmcKYCmQPn).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -1,33 +1,33 @@
-Contributing to Travertine
+Contributing to Mangocord
 ==========================
-WaterfallMC has a very lenient policy towards PRs, but would prefer that you try and adhere to the following guidelines.
+mangocord follows the parameters of the WaterfallMC project when making a Pull Request. WaterfallMC has a very lenient policy towards PRs, but would prefer that you try and adhere to the following guidelines.
 
 ## Understanding Patches
-Patches to Travertine are very simple, but center around the directory 'Travertine-Proxy'
+Patches to mangocord are very simple, but center around the directory 'flamecord-Proxy'
 
 Assuming you already have forked the repository:
 
 1. Pull the latest changes from the main repository
-2. Type `./travertine p` in git bash to apply the changes from upstream
-3. cd into `Travertine-Proxy` for proxy changes
+2. Type `./mangocord p` in git bash to apply the changes from upstream
+3. cd into `flamecord-Proxy` for proxy changes
 
 This directory is not a git repository in the traditional sense:
 
-- Every single commit in Travertine-Proxy is a patch. 
-- 'origin/master' points to a directory similar to Travertine-Proxy but for Travertine
-- Typing `git status` should show that we are 10 or 11 commits ahead of master, meaning we have 10 or 11 patches that Travertine, Waterfall, and Bungeecord don't
-  - If it says something like `212 commits ahead, 207 commits behind`, then type `git fetch` to update Travertine
+- Every single commit in mangocord-Proxy is a patch. 
+- 'origin/master' points to a directory similar to Waterfall-Proxy but for mangocord
+- Typing `git status` should show that we are 10 or 11 commits ahead of master, meaning we have 10 or 11 patches that mangocord, Waterfall, and Bungeecord don't
+  - If it says something like `212 commits ahead, 207 commits behind`, then type `git fetch` to update mangocord
 
 ## Adding Patches
-Adding patches to Travertine is very simple:
+Adding patches to mangocord is very simple:
 
-1. Modify `Travertine-Proxy` with the appropriate changes
+1. Modify `flamecord-Proxy` with the appropriate changes
 2. Type `git add .` to add your changes
 3. Run `git commit` with the desired patch message
-4. Run `./travertine rb` in the main directory to convert your commit into a new patch
+4. Run `./mangocord rb` in the main directory to convert your commit into a new patch
 5. PR your patches back to this repository
 
-Your commit will be converted into a patch that you can then PR into Travertine
+Your commit will be converted into a patch that you can then PR into mangocord
 
 ## Modifying Patches
 Modifying previous patches is a bit more complex:
@@ -38,7 +38,6 @@ This method works by temporarily resetting HEAD to the desired commit to edit us
 1. If you have changes you are working on type `git stash` to store them for later.
   - Later you can type `git stash pop` to get them back.
 2. Type `git rebase -i upstream/upstream`
-  - It should show something like [this](https://gist.github.com/Zbob750/e6bb220d3b734933c320).
 3. Replace `pick` with `edit` for the commit/patch you want to modify, and "save" the changes.
   - Only do this for one commit at a time.
 4. Make the changes you want to make to the patch.
@@ -47,7 +46,7 @@ This method works by temporarily resetting HEAD to the desired commit to edit us
   - **MAKE SURE TO ADD `--amend`** or else a new patch will be created.
   - You can also modify the commit message here.
 7. Type `git rebase --continue` to finish rebasing.
-8. Type `./travertine rb` in the main directory.
+8. Type `./mangocord rb` in the main directory.
   - This will modify the appropriate patches based on your commits.
 9. PR your modifications back to this project.
 
@@ -58,40 +57,40 @@ If you are simply editing a more recent commit or your change is small, simply m
 2. Make a temporary commit. You don't need to make a message for this.
 3. Type `git rebase -i upstream/upstream`, move (cut) your temporary commit and move it under the line of the patch you wish to modify.
 4. Change the `pick` with `f` (fixup) or `s` (squash) if you need to edit the commit message 
-5. Type `./travertine rb` in the main directory.
+5. Type `./mangocord rb` in the main directory.
   - This will modify the appropriate patches based on your commits.
 6. PR your modifications to github
 
 
 ## PR Policy
-We'll accept changes that make sense. You should be able to justify their existence, along with any maintenance costs that come with them. Remember, these changes will affect everyone who runs Travertine, not just you and your server.
+We'll accept changes that make sense. You should be able to justify their existence, along with any maintenance costs that come with them. Remember, these changes will affect everyone who runs mangocord, not just you and your server.
 While we will fix minor formatting issues, you should stick to the guide below when making and submitting changes.
 
 ## Formatting
-All modifications to non-Travertine files should be marked
-- Multi line changes start with `// Travertine start` and end with `// Travertine end`
-- You can put a messages with a change if it isn't obvious, like this: `// Travertine start - reason
+All modifications to non-mangocord files should be marked
+- Multi line changes start with `// mangocord start` and end with `// mangocord end`
+- You can put a messages with a change if it isn't obvious, like this: `// mangocord start - reason
   - Should generally be about the reason the change was made, what it was before, or what the change is
-  - Multi-line messages should start with `// Travertine start` and use `/* Multi line message here */` for the message itself
-- Single line changes should have `// Travertine` or `// Travertine - reason`
+  - Multi-line messages should start with `// mangocord start` and use `/* Multi line message here */` for the message itself
+- Single line changes should have `// mangocord` or `// mangocord - reason`
 - For example:
 ````java
-return getConfig().getNotStupid(); // Travertine - was return getConfig().getStupid();
+return getConfig().getNotStupid(); // mangocord - was return getConfig().getStupid();
 
-// Travertine start
+// mangocord start
 // con.disconnect( bungee.getTranslation( "lost_connection" ) );
 ServerInfo def = con.updateAndGetNextServer( server.getInfo() );
 ServerKickEvent event = bungee.getPluginManager().callEvent( new ServerKickEvent( con, server.getInfo(), TextComponent.fromLegacyText( bungee.getTranslation( "lost_connection" ) ), def, ServerKickEvent.State.CONNECTED, ServerKickEvent.Cause.LOST_CONNECTION ) );
 if ( event.isCancelled() && event.getCancelServer() != null )
 {
     server.setObsolete( true );
     con.connectNow( event.getCancelServer() );
-}
+}mangocord
 else
 {
     con.disconnect0( event.getKickReasonComponent() );
 }
-// Travertine end
+// mangocord end
 ````
 - We generally follow usual java style, or what is programmed into most IDEs and formatters by default
   - This is also known as oracle style

README.md

@@ -1,55 +1,2 @@
-FlameCord
-=========
-
-FlameCord is a patch for Travertine to fix possible exploits and add useful functionalities.
-
-FlameCord is compiled like Travertine does; Please follow the CONTRIBUTING.md file. If you need help you can always contact us on Discord.
-
-<a href="https://discord.gg/gF36AT3"><img src="https://discord.com/assets/4ff060e44afc171e9622fbe589c2c09e.png" width=10% height=10%><img/><a/> <a href="https://www.mc-market.org/resources/13492/"><img src="https://www.mc-market.org/styles/mcmarketv2/xenforo/logo.png" width=10% height=10%><img/><a/>
-
-Travertine [![Build Status](https://papermc.io/ci/job/Travertine/badge/icon)](https://papermc.io/ci/job/Travertine/)
-=========
-
-Travertine is Waterfall with additional protocols. Waterfall is a fork of the well-known [BungeeCord](https://github.com/SpigotMC/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.
-
-Travertine focuses on one main area:
-
-* **Additional Client Version Support**: Travertine aims to support client versions older then what is supported in upstream. This includes 1.7 support. Additionally Travertine may release Snapshot and PRE Client support patches as time permits.
-
-## Why fork Waterfall?
-
-Travertine has a goal of adding additional protocol versions.
-
-Travertine was forked because of the fact that Waterfall intends to only support protocol versions supported by upstream BungeeCord. 
-
-Travertine will track upstream Waterfall and merge changes as needed.
-
-## How to (Server Admins)
-
-Download a copy of Travertine.jar from our buildserver here: [Travertine](https://papermc.io/ci/job/Travertine/)
-
-Travertine requires **Java 8** or above.
-
-## How To (Compiling from source)
-
-To compile Travertine, you need JDK8, git, bash, maven, and an internet connection.
-
-Clone this repo, run `./travertine b` from *bash*, get jar from `Travertine-Proxy/bootstrap/target`
-
-## Join us
-
-* Feel free to open a PR! We accept contributions.
-* Join us on IRC (irc.spi.gt #paper, [webchat](http://irc.spi.gt/iris/?nick=&channels=paper)).
-* Visit our forums (https://papermc.io/forums).
-
-Special Thanks To
------------------
-![YourKit-Logo](https://yourkit.com/images/yklogo.png)
-
-[YourKit](https://yourkit.com/), makers of the outstanding Java profiler, supports open source projects of all kinds with their full-featured [Java](https://yourkit.com/features/) and [.NET](https://yourkit.com/dotnet/features/) application profilers. We thank them for granting Travertine an OSS license so that we can make our software the best it can be.
+## This repository has been moved to the repository at the link below. 
+This repository has been moved to [link to the new repository](https://github.com/LuciaNishimiya/MangoCord) due to the risk of the original project creator deleting it.

README.old

@@ -0,0 +1,57 @@
+
+<img src="https://mondongo.cf/cloud/up/Mangocord.png" />
+
+MangoCord is a fork of Waterfall and Flamecord that protects your Minecraft server from bot attacks and exploits with its advanced set of antibot filtering features. MangoCord also fixes bugs, improves performance and adds new functionalities to your server. MangoCord is the ultimate solution for a secure and fast Minecraft network
+
+## Links
+Free download MangoCord:<br>
+https://github.com/LuciaNishimiya/MangoCord/releases<br>
+https://builtbybit.com/resources/mangocord-mitigate-bots-exploits.27316/
+<br> <br>
+Discord Mango Studio:<br>
+https://discord.gg/PeS8h8eJZJ
+
+## Feactures
+* Our features are focused on the security of your Minecraft server preventing hacking with crash exploits, bots and other kind of dos attacks on the application layer.
+
+* **Bots**: We provides a powerful anti-bot solution programmed directly into the core of BungeeCord, with the ability to mitigate these attacks without hindering your server's performance.
+
+* **Anti-vpn/proxy**: Checks whether a connection is a proxy/VPN by utilizing web databases from over 10 webs, and additional websites can be added as well.
+
+* **Performance**: It reduces CPU usage and RAM usage by optimizing and reusing code, caching heavy getters, using libdeflate for faster compression/decompression of packets, and fixing memory leaks.
+
+* **GeyserMC compatibility**: MangoCord supports Geyser, a proxy that allows Bedrock Edition players to join Java Edition servers. It supports most Java features and cross-play between different platforms.
+
+* **Motd**: Incorporates customizable an advanced motd system that protects against null pink attacks
+
+* **Languages Supported**: Provides you with absolute flexibility by allowing you to fully customize all messages and texts of your server through the messages.yml configuration file.
+
+* **Exploit Fixes**: MangoCord specializes in providing better server security by fixing major exploits, performance flaws and bugs that Bungeecord already has, and that have not yet been fixed in WaterfallMC.
+
+
+MangoCord is a FlameCord and Waterfall fork that protects your server from bot attacks and exploits done to your Minecraft Server by minimizing the impact received by those with our advanced set of antibot filtering features. MangoCord improves your server performance and reduces your CPU usage by cutting the amount of processes required to process packets. MangoCord has free official and community support on our Discord server. https://discord.gg/PeS8h8eJZJ . Visit our detailed guide to MangoCord configuration to know more about it's features and how to configure them.
+
+
+## Why fork Waterfall?
+
+MangoCord  was forked out of a desire for greater protection to be afforded to a Bungeecord-based proxy, which Waterfall currently cannot offer.
+
+MangoCord  will track upstream Waterfall and merge changes as needed.
+
+## How to (Server Admins)
+
+Just drag an drop MangoCord .jar into your server folder and run it.
+
+You can customize many MangoCord  features in the flamecord.yml file.
+
+## How To (Compiling from source)
+
+To compile MangoCord, you need JDK8 or above, git, bash, maven, and an internet connection.
+
+Clone this repo, run `./mangocord b` from *bash*, get jar from `FlameCord-Proxy/bootstrap/target`
+
+Mangocord is compiled like Waterfall does; Please follow the [CONTRIBUTING.md](https://github.com/LuciaNishimiya/MangoCord/blob/main/CONTRIBUTING.md) file. If you need help you can always contact us on Discord.
+
+## Contribute
+
+* Feel free to open a PR! We accept contributions.