Collection of public (or not) forks / custom builds of LiquidBounce. Please, before using it, check by yourself for any malware inside it. Suggest any custom build in my dm or Issues of this repository.
| aeon | ||
| AtField | ||
| Burnsense | ||
| ChenlunBounce | ||
| ChrismasAce | ||
| Cloudsense | ||
| CrazyBounce | ||
| Ctrl | ||
| DayZay | ||
| dusksense | ||
| Hreith | ||
| Leak | ||
| LiKingSense | ||
| LiquidAlpha | ||
| LiquidPlus-Modified | ||
| LiquidWing | ||
| MoralClient | ||
| NightX | ||
| Noteless | ||
| Other | ||
| PasacZ | ||
| RedBone | ||
| RedStar | ||
| Relaxed | ||
| Sweet | ||
| TomK | ||
| Wake | ||
| Warrior | ||
| Water | ||
| XiaodaBounce | ||
| .gitattributes | ||
| README.md | ||
Bounce-Killer
Eliminate publicly distributed and illegally sold versions of LiquidBounce without source code.
Any LiquidBounce fork/modified version that does not comply with open-source agreement will get cracked / its source leaked.
Most importantly,
Please notice that the original LiquidBounce project is publicized and licensed under GPLv3, which does NOT allow anyone to sell/distribute softwares without disclosing their source.
Original LiquidBounce GitHub repository: https://github.com/CCBlueX/LiquidBounce
GNU General Public License version 3: https://www.gnu.org/licenses/gpl-3.0.en.html
EN: Why did we create this repository?
- Many "developers" do not abide by the open-source license, making no contribution when using the results of others. To this end, we will deal with their procedures.
- According to the original LiquidBounce (GPLv3), the developers required people to disclose their modified products' source when using their code.
- As far as I am concerned, only FDPClient , LiquidBouncePlus and LiquidBouncePlusReborn has truly complied with the license.
- Most people sell private LiquidBounce versions with built-in verification without disclosing source to their users, which is a serious violation of the original intention of the source.
- Our goal is to crack these builds/versions or perform other actions to prevent them from continuing their violations.
EN: How to contact with us?
- Join Telegram Group: https://t.me/SkiderKiller
CN: 为什么创建这个项目
- 许多开发人员不遵守开源协议。在使用他人成果时不做出任何贡献。为此我们将对他们的程序作出处理。
- 针对LiquidBounce这个开源项目(GPLv3)，原开发者要求在使用他们的代码时必须对自己的修改产物进行开源。
- 纵观整个方块人二次开发的LiquidBounce，仅有FDPClient,LiquidBouncePlus以及LiquidBouncePlusReborn真正做到了遵守开源协议。
- 目前大部分人对二次开发的LiquidBounce加入验证系统，进行售卖，但并未开源，这严重违反了开源者的初衷。
- 现在我们将对这些客户端进行破解或执行一些阻止其违规行为的操作。
CN: 如何联系我们?
- 加入电报群组(需要VPN): https://t.me/SkiderKiller
It is worth mentioning that we will always give our respects to LiquidBounce and its contributors, therefore using every possible methods to achieve our goals.
Related info | 相关事项
- If you have any leaked/damaged source code leaks, you can submit issues for us to repair them.
如果你需要部分“重要源代码”，可以提交Issues促使我们进行源代码修复
- If you found any closed source LiquidBounce builds, you can also submit issues to remind us to crack them.
如果发现其他闭源二次开发的LiquidBounce，可提交Issues提醒我们进行处理
- Any third-party patchers/softwares used in this project don't contain any harmful/malicious code.
本项目中任何用于破解的第三方补丁、第三方软件不含有任何危害电脑安全的代码。
- Please use Java version 8 (1.8.0_201) and above if possible.
如果可能的话，请使用Java第8版（1.8.0_201）及以上版本。