CatsPnewed/Forkbounce.Archive
CatsPnewed/Forkbounce.Archive
6
5
Fork 3
Code Issues 5 Pull requests Projects Releases Wiki Activity

Merge pull request #9 from WYSI-Foundation/main

Browse source 
Update Readme file for better understanding.
This commit is contained in:
RareCO 2022-05-26 08:38:31 +08:00 committed by GitHub
commit dac813d1c1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 27 additions and 35 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

62
README.md
View file

@ -1,41 +1,33 @@
# Bounce-Killer
Any liquidbounce secondary modification client that does not comply with the open source agreement will face cracking / open source.
# Related Information
Please notice that the liquidbounce project opened source under GPLv3 license.The license doesnt allow anyone to sell their products(even obfuscated) without opening sources.
>The origin liquidbounce source link(Github): https://github.com/CCBlueX/LiquidBounce
# 为什么创建这个项目
# Why build this project
>很多国人开发者并不遵守开源协议。在使用他人成果时不做出任何贡献。为此我们将对他们的程序作出处理。
# 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
> Many Chinese 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.
## EN: Why did we create this repository?
- Many Chinese "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 and LiquidBouncePlus has truly complied with the license.
- Most people sell private LiquidBounce builds 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.
>针对LiquidBounce这个开源项目(GPLv3)，原开发者要求在使用他们代码的时候必须对自己的修改产物进行开源。
## CN: 为什么创建这个项目
- 很多国人开发者并不遵守开源协议。在使用他人成果时不做出任何贡献。为此我们将对他们的程序作出处理。
- 针对LiquidBounce这个开源项目(GPLv3)，原开发者要求在使用他们代码的时候必须对自己的修改产物进行开源。
- 纵观整个方块人二开Bounce，仅有FDPClient&LiquidBouncePlus做到了真正遵守协议
- 大部分人加上验证进行售卖，但并未向用户开源，这严重违反了开源者的初衷。
- 现在我们将对这些客户端进行破解或其他阻止其继续违规行为的操作。
> For the open source project liquidbource (GPLv3), the original developers required to open source their modified products when using their code.
>纵观整个方块人二开Bounce，仅有FDP Client&LiquidBouncePlus做到了真正遵守协议
> As far as I am concerned, only FDP client & liquidbounceplus has truly complied with the license.
>大部分人加上验证进行售卖，但并未向用户开源，这严重违反了开源者的初衷。
> Most people sell with verification, but they don't open source to users, which is a serious violation of the original intention of the source.
>现在我们将对这些客户端进行破解或其他阻止其继续违规行为的操作。
> Now we will crack these clients or other operations to prevent them from continuing their violations.
# 值得注意的是 一切手段
# It is worth noticing that we will use all means
# 相关事项(Related matters)
>如果你需要部分“重要源代码”可以提交Issues使我们进行源代码修复
> If you need some "important source code", you can submit issues for us to repair the source code.
>如果发现其他闭源二开LiquidBounce也可以提交Issues提醒我们进行处理
> If you find other closed source secondary development programs, you can also submit issues to remind us to crack them.
### It is worth mentioning that we will by all means give our respects to LiquidBounce and its contributors.
## 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.
>本项目中任何第三方补丁，第三方软件用于破解的不含任何危害电脑安全代码。
> Any third-party patchers and third-party software in this project arent contain any code endangering computer security.