chore: Feature Requests towards Nextgen only

[1zun4]

This will be merged on 01/02/2025. After this date, all feature requests that are not for LiquidBounce Nextgen will be closed and new ones will NOT be accepted. Bug reports will still be allowed to be opened and worked on.

For a more detailed reason:

Starting in February, I will be rejecting all feature requests for Legacy.

Legacy is a far cry from what the name implies it should be. I can't and won't continue to compete with a client that is based on my work and distributed under the same name, and will now start adding more notices to Legacy itself about how it's planned to be abandoned.

I'm not going to immediately ask you to stop development, because I don't know what state LiquidBounce Legacy is in, which is probably not a good state - but continuing to add features to it at a rate that consistently breaks compatibility with every existing config, script, theme and all the reasons why people use LiquidBounce Legacy is not acceptable.

Another thing I've just noticed is that essentially LiquidBounce Legacy does not even include any way of knowing who developed it. There's no "Made by CCBlueX...", nor does the "Contributors" tab represent the actual contributors of Legacy (which is due to the fact that it pulls statistics from Nextgen instead).

I'm not 100% sure how I will add more notices to Legacy, but it has to be done, otherwise people will continue to think of Legacy as the LiquidBounce - even though it's not developed by us anymore.

For context: LiquidBounce Legacy was discontinued by our original development team in 2020. Since then it has only been developed by contributors and trusted project maintainers.

[vardenixxxas]

this is massive

[Coccocoahelper]

I believe that LiquidBounce Legacy should be put as a separate project, in a separate organization. Its ideals no longer match the CCBlueX organizations'.

[RtxOP]

You're forgetting people decide to download legacy out of their own volition even though nextgen is getting shoved down their throats. Take a moment to think about why that is. Could it be (god forbid) performance? Majority of users being on laptops? Latest versions of minecraft eating up ram? You're actively neglecting the majority while trying to hinder development. Proud of you man.

[vardenixxxas]

You're forgetting people decide to download legacy out of their own volition even though nextgen is getting shoved down their throats. Take a moment to think about why that is. Could it be (god forbid) performance? Majority of users being on laptops? Latest versions of minecraft eating up ram? You're actively neglecting the majority while trying to hinder development. Proud of you man.

Nextgen runs with less ram then legacy.

[1zun4]

You're forgetting people decide to download legacy out of their own volition even though nextgen is getting shoved down their throats. Take a moment to think about why that is. Could it be (god forbid) performance? Majority of users being on laptops? Latest versions of minecraft eating up ram? You're actively neglecting the majority while trying to hinder development. Proud of you man.

LiquidBounce Legacy was officially discontinued in 2020, but has continued through community contributions. This has had some consequences, mainly confusion about its development status and people still assuming that we, CCBlueX, continue to maintain this client. Do you really think that giving users half a decade to migrate to a new client is shoving it down their throat?

We're not immediately stopping development for Legacy; we're simply setting clear boundaries to ensure users understand its status. Bug fixes will still be addressed if critical enough, and users can continue to use Legacy if they wish.

Our goal is to finally make it clear to legacy users that the project is being phased out in a way that makes everyone happy, and to align our development efforts with the long-term vision of the project through Nextgen. We appreciate the passion and contributions of the community, but there can only be one client if we truly want to give everyone the best possible experience.

Both @mems01 and @EclipsesDev also see this as an opportunity to make b100 the last version of LiquidBounce Legacy, turning it into a stable client once and for all - where no sudden changes occur that break configs, themes, scripts as has been the case in recent versions with every update.

At the end of the day, we could have done this 5 years ago: It's LiquidBounce. It's just another update. Why make such a big deal out of it? We decided on this because with v0.1.0 it was still lacking major features that we couldn't develier in time, so we thought give users the decision. But now that I think about, we should have taken the step and never even made an difference between Nextgen and Legacy. Immedialty replacing the project would be the better option when we look at how users behave and act like we split the community apart. It was NOT split apart.

LiquidBounce Nextgen is a huge success and we have never seen so many people using LiquidBounce.

[1zun4]

Performance Comparison

Specifications:

OS: EndeavourOS Linux x86_64 
Host: B550 AORUS ELITE AX V2 
Kernel: 6.12.10-arch1-1 
Shell: zsh 5.9 
Resolution: 2560x1440 
CPU: AMD Ryzen 9 5900X (24) @ 4.951GHz 
GPU: AMD ATI Radeon RX 570
Memory: 32 GB

Settings

Resource Pack: Minecraft
Video Settings: 8 Chunks and FPS unlimited
HUD Settings: No Blur (because LiquidBounce Legacy does not offer any blur)

Test

LiquidBounce Legacy

LiquidBounce Nextgen

Conclusion

As you can see, the performance of both clients is essentially the same. LiquidBounce Legacy actually uses a lot more memory for some reason without even being in the game, which is probably due to the design of the font renderer.

However, I noticed that nextgen tries to draw the main menu as FAST as possible when there is no FPS limit applied, which is actually not so good - this needs to be fixed to a more reasonable limit. Luckily JCEF already has it's own FPS limit for menu which is bound to your monitor refresh rate which allows to save up performance on drawing. The bug has been addressed by 1884a4c and is now fixed.

Is it rigged?

It depends very much on your system which client might run better - in my case I have a very bad GPU paired with a high performance CPU which allows me to get the extra FPS boost in Nextgen which is more intensive on the CPU.

I also have a machine with exactly the same specs as my main machine, but with an AMD Ryzen 5 1400 instead. The performance is worse - but still in a range where I feel it's perfectly fine to play, and this is the hardware on which I started developing LiquidBounce Nextgen. :)

People have also done the test themselves and come to similar conclusions:

I should also point out that this is an RX 570 GPU. You might be fooled by my overpowered CPU, but at the end of the day it's still a GPU that only costs around 70 Euros.
If you look at the [Steam Hardware Survey] (https://store.steampowered.com/hwsurvey) you can see that the majority of people have a more powerful GPU than the one I used for this comparison.

[RtxOP]

You're forgetting people decide to download legacy out of their own volition even though nextgen is getting shoved down their throats. Take a moment to think about why that is. Could it be (god forbid) performance? Majority of users being on laptops? Latest versions of minecraft eating up ram? You're actively neglecting the majority while trying to hinder development. Proud of you man.

LiquidBounce Legacy was officially discontinued in 2020, but has continued through community contributions. This has had some consequences, mainly confusion about its development status and people still assuming that we, CCBlueX, continue to maintain this client. Do you really think that giving users half a decade to migrate to a new client is shoving it down their throat?

We're not immediately stopping development for Legacy; we're simply setting clear boundaries to ensure users understand its status. Bug fixes will still be addressed if critical enough, and users can continue to use Legacy if they wish.

Our goal is to finally make it clear to legacy users that the project is being phased out in a way that makes everyone happy, and to align our development efforts with the long-term vision of the project through Nextgen. We appreciate the passion and contributions of the community, but there can only be one client if we truly want to give everyone the best possible experience.

Both @mems01 and @EclipsesDev also see this as an opportunity to make b100 the last version of LiquidBounce Legacy, turning it into a stable client once and for all - where no sudden changes occur that break configs, themes, scripts as has been the case in recent versions with every update.

At the end of the day, we could have done this 5 years ago: It's LiquidBounce. It's just another update. Why make such a big deal out of it? We decided on this because with v0.1.0 it was still lacking major features that we couldn't develier in time, so we thought give users the decision. But now that I think about, we should have taken the step and never even made an difference between Nextgen and Legacy. Immedialty replacing the project would be the better option when we look at how users behave and act like we split the community apart. It was NOT split apart.

LiquidBounce Nextgen is a huge success and we have never seen so many people using LiquidBounce.

Legacy runs way better on my PC. And I can understand your push for nextgen because you have financial incentives for developing this client - you're not doing it out of goodwill. The better the brand image, the more people download it, the more money you make. That's why your reasoning didn't make sense to me because it wasn't the actual reason. Configs and themes breaking? Configs and themes from years ago shouldn't work now anyway; they're useless. The themes never looked good because of the abomination you cooked, and it's actually starting to look better now. So, old themes working is, as I said, useless. The configs breaking is because of major changes that I think won't be happening every update. You having to resort to scummy tactics to remove competition from your own client that is being maintained by the community is nothing short of circus theatrics. If you're gonna do something don't lie out of your ass next time.

[localpthebest]

You're forgetting people decide to download legacy out of their own volition even though nextgen is getting shoved down their throats. Take a moment to think about why that is. Could it be (god forbid) performance? Majority of users being on laptops? Latest versions of minecraft eating up ram? You're actively neglecting the majority while trying to hinder development. Proud of you man.

LiquidBounce Legacy was officially discontinued in 2020, but has continued through community contributions. This has had some consequences, mainly confusion about its development status and people still assuming that we, CCBlueX, continue to maintain this client. Do you really think that giving users half a decade to migrate to a new client is shoving it down their throat?
We're not immediately stopping development for Legacy; we're simply setting clear boundaries to ensure users understand its status. Bug fixes will still be addressed if critical enough, and users can continue to use Legacy if they wish.
Our goal is to finally make it clear to legacy users that the project is being phased out in a way that makes everyone happy, and to align our development efforts with the long-term vision of the project through Nextgen. We appreciate the passion and contributions of the community, but there can only be one client if we truly want to give everyone the best possible experience.
Both @mems01 and @EclipsesDev also see this as an opportunity to make b100 the last version of LiquidBounce Legacy, turning it into a stable client once and for all - where no sudden changes occur that break configs, themes, scripts as has been the case in recent versions with every update.
At the end of the day, we could have done this 5 years ago: It's LiquidBounce. It's just another update. Why make such a big deal out of it? We decided on this because with v0.1.0 it was still lacking major features that we couldn't develier in time, so we thought give users the decision. But now that I think about, we should have taken the step and never even made an difference between Nextgen and Legacy. Immedialty replacing the project would be the better option when we look at how users behave and act like we split the community apart. It was NOT split apart.
LiquidBounce Nextgen is a huge success and we have never seen so many people using LiquidBounce.

Legacy runs way better on my PC. And I can understand your push for nextgen because you have financial incentives for developing this client - you're not doing it out of goodwill. The better the brand image, the more people download it, the more money you make. That's why your reasoning didn't make sense to me because it wasn't the actual reason. Configs and themes breaking? Configs and themes from years ago shouldn't work now anyway; they're useless. The themes never looked good because of the abomination you cooked, and it's actually starting to look better now. So, old themes working is, as I said, useless. The configs breaking is because of major changes that I think won't be happening every update. You having to resort to scummy tactics to remove competition from your own client that is being maintained by the community is nothing short of circus theatrics. If you're gonna do something don't lie out of your ass next time.

he makes money from ads on all downloads including legacy how tf is removing one of his money sources a financial incentive??

also how tf is it a good thing that themes break thats not intended and theres no way to twist that as a positive

[Coccocoahelper]

Performance Comparison

Specifications:

OS: EndeavourOS Linux x86_64 
Host: B550 AORUS ELITE AX V2 
Kernel: 6.12.10-arch1-1 
Shell: zsh 5.9 
Resolution: 2560x1440 
CPU: AMD Ryzen 9 5900X (24) @ 4.951GHz 
GPU: AMD ATI Radeon RX 570
Memory: 32 GB

Settings

Resource Pack: Minecraft
Video Settings: 8 Chunks and FPS unlimited
HUD Settings: No Blur (because LiquidBounce Legacy does not offer any blur)

Test

LiquidBounce Legacy

LiquidBounce Nextgen

Conclusion

As you can see, the performance of both clients is essentially the same. LiquidBounce Legacy actually uses a lot more memory for some reason without even being in the game, which is probably due to the design of the font renderer.

However, I noticed that nextgen tries to draw the main menu as FAST as possible when there is no FPS limit applied, which is actually not so good - this needs to be fixed to a more reasonable limit. Luckily JCEF already has it's own FPS limit for menu which is bound to your monitor refresh rate which allows to save up performance on drawing. The bug has been addressed by 1884a4c and is now fixed.

Is it rigged?

It depends very much on your system which client might run better - in my case I have a very bad GPU paired with a high performance CPU which allows me to get the extra FPS boost in Nextgen which is more intensive on the CPU.

I also have a machine with exactly the same specs as my main machine, but with an AMD Ryzen 5 1400 instead. The performance is worse - but still in a range where I feel it's perfectly fine to play, and this is the hardware on which I started developing LiquidBounce Nextgen. :)

People have also done the test themselves and come to similar conclusions:

I should also point out that this is an RX 570 GPU. You might be fooled by my overpowered CPU, but at the end of the day it's still a GPU that only costs around 70 Euros. If you look at the [Steam Hardware Survey] (https://store.steampowered.com/hwsurvey) you can see that the majority of people have a more powerful GPU than the one I used for this comparison.

You should try this on a VM, with 2 cores, each 2.6Ghz, and a severely underpowered GPU.

[RtxOP]

You're forgetting people decide to download legacy out of their own volition even though nextgen is getting shoved down their throats. Take a moment to think about why that is. Could it be (god forbid) performance? Majority of users being on laptops? Latest versions of minecraft eating up ram? You're actively neglecting the majority while trying to hinder development. Proud of you man.

LiquidBounce Legacy was officially discontinued in 2020, but has continued through community contributions. This has had some consequences, mainly confusion about its development status and people still assuming that we, CCBlueX, continue to maintain this client. Do you really think that giving users half a decade to migrate to a new client is shoving it down their throat?
We're not immediately stopping development for Legacy; we're simply setting clear boundaries to ensure users understand its status. Bug fixes will still be addressed if critical enough, and users can continue to use Legacy if they wish.
Our goal is to finally make it clear to legacy users that the project is being phased out in a way that makes everyone happy, and to align our development efforts with the long-term vision of the project through Nextgen. We appreciate the passion and contributions of the community, but there can only be one client if we truly want to give everyone the best possible experience.
Both @mems01 and @EclipsesDev also see this as an opportunity to make b100 the last version of LiquidBounce Legacy, turning it into a stable client once and for all - where no sudden changes occur that break configs, themes, scripts as has been the case in recent versions with every update.
At the end of the day, we could have done this 5 years ago: It's LiquidBounce. It's just another update. Why make such a big deal out of it? We decided on this because with v0.1.0 it was still lacking major features that we couldn't develier in time, so we thought give users the decision. But now that I think about, we should have taken the step and never even made an difference between Nextgen and Legacy. Immedialty replacing the project would be the better option when we look at how users behave and act like we split the community apart. It was NOT split apart.
LiquidBounce Nextgen is a huge success and we have never seen so many people using LiquidBounce.

Legacy runs way better on my PC. And I can understand your push for nextgen because you have financial incentives for developing this client - you're not doing it out of goodwill. The better the brand image, the more people download it, the more money you make. That's why your reasoning didn't make sense to me because it wasn't the actual reason. Configs and themes breaking? Configs and themes from years ago shouldn't work now anyway; they're useless. The themes never looked good because of the abomination you cooked, and it's actually starting to look better now. So, old themes working is, as I said, useless. The configs breaking is because of major changes that I think won't be happening every update. You having to resort to scummy tactics to remove competition from your own client that is being maintained by the community is nothing short of circus theatrics. If you're gonna do something don't lie out of your ass next time.

he makes money from ads on all downloads including legacy how tf is removing one of his money sources a financial incentive??

also how tf is it a good thing that themes break thats not intended and theres no way to twist that as a positive

He plans to create an ecosystem around nextgen. There's an ominous branch named marketplace I wonder what that does. And the themes didn't look good at all so a revamp was and still is needed.

[1zun4]

Legacy runs way better on my PC. And I can understand your push for nextgen because you have financial incentives for developing this client - you're not doing it out of goodwill. The better the brand image, the more people download it, the more money you make. That's why your reasoning didn't make sense to me because it wasn't the actual reason. Configs and themes breaking? Configs and themes from years ago shouldn't work now anyway; they're useless. The themes never looked good because of the abomination you cooked, and it's actually starting to look better now. So, old themes working is, as I said, useless. The configs breaking is because of major changes that I think won't be happening every update. You having to resort to scummy tactics to remove competition from your own client that is being maintained by the community is nothing short of circus theatrics. If you're gonna do something don't lie out of your ass next time.

The claim that we are stopping LiquidBounce Legacy for financial incentives is incorrect. In fact, we make money from Legacy without doing any work on it, so there’s no financial gain in discontinuing it. Our goal is to provide the best possible experience for users, and Legacy does not align with what we want LiquidBounce to be moving forward.

He plans to create an ecosystem around nextgen. There's an ominous branch named marketplace I wonder what that does. And the themes didn't look good at all so a revamp was and still is needed.

Yes, we are working on creating an ecosystem around Nextgen to make the client more user-friendly and appealing. However, there seems to be a misunderstanding about our intentions. The marketplace is not planned to include any payment options. Its purpose is simply to provide a centralized hub where users can easily access and auto-update configs, themes, scripts, color schemes, and more.

You can take a look at the implementation of it here: #5226 - which is not completed, but a demo of what we want it to be.
We have decided on the name "Marketplace" internally as we do not have a more fitting name to describe it. We could also call it "Resources" - which is probably going to be our official naming of it.

[ccetl]

You're forgetting people decide to download legacy out of their own volition even though nextgen is getting shoved down their throats. Take a moment to think about why that is. Could it be (god forbid) performance? Majority of users being on laptops? Latest versions of minecraft eating up ram? You're actively neglecting the majority while trying to hinder development. Proud of you man.

LiquidBounce is open source. Just fork it and continue updating legacy if you wish to do so.

[RtxOP]

Legacy runs way better on my PC. And I can understand your push for nextgen because you have financial incentives for developing this client - you're not doing it out of goodwill. The better the brand image, the more people download it, the more money you make. That's why your reasoning didn't make sense to me because it wasn't the actual reason. Configs and themes breaking? Configs and themes from years ago shouldn't work now anyway; they're useless. The themes never looked good because of the abomination you cooked, and it's actually starting to look better now. So, old themes working is, as I said, useless. The configs breaking is because of major changes that I think won't be happening every update. You having to resort to scummy tactics to remove competition from your own client that is being maintained by the community is nothing short of circus theatrics. If you're gonna do something don't lie out of your ass next time.

The claim that we are stopping LiquidBounce Legacy for financial incentives is incorrect. In fact, we make money from Legacy without doing any work on it, so there’s no financial gain in discontinuing it. Our goal is to provide the best possible experience for users, and Legacy does not align with what we want LiquidBounce to be moving forward.

He plans to create an ecosystem around nextgen. There's an ominous branch named marketplace I wonder what that does. And the themes didn't look good at all so a revamp was and still is needed.

Yes, we are working on creating an ecosystem around Nextgen to make the client more user-friendly and appealing. However, there seems to be a misunderstanding about our intentions. The marketplace is not planned to include any payment options. Its purpose is simply to provide a centralized hub where users can easily access and auto-update configs, themes, scripts, color schemes, and more.

You can take a look at the implementation of it here: #5226 - which is not completed, but a demo of what we want it to be. We have decided on the name "Marketplace" internally as we do not have a more fitting name to describe it. We could also call it "Resources" - which is probably going to be our official naming of it.

What a kind hearted Samaritan!

[Coccocoahelper]

Legacy runs way better on my PC. And I can understand your push for nextgen because you have financial incentives for developing this client - you're not doing it out of goodwill. The better the brand image, the more people download it, the more money you make. That's why your reasoning didn't make sense to me because it wasn't the actual reason. Configs and themes breaking? Configs and themes from years ago shouldn't work now anyway; they're useless. The themes never looked good because of the abomination you cooked, and it's actually starting to look better now. So, old themes working is, as I said, useless. The configs breaking is because of major changes that I think won't be happening every update. You having to resort to scummy tactics to remove competition from your own client that is being maintained by the community is nothing short of circus theatrics. If you're gonna do something don't lie out of your ass next time.

The claim that we are stopping LiquidBounce Legacy for financial incentives is incorrect. In fact, we make money from Legacy without doing any work on it, so there’s no financial gain in discontinuing it. Our goal is to provide the best possible experience for users, and Legacy does not align with what we want LiquidBounce to be moving forward.

He plans to create an ecosystem around nextgen. There's an ominous branch named marketplace I wonder what that does. And the themes didn't look good at all so a revamp was and still is needed.

Yes, we are working on creating an ecosystem around Nextgen to make the client more user-friendly and appealing. However, there seems to be a misunderstanding about our intentions. The marketplace is not planned to include any payment options. Its purpose is simply to provide a centralized hub where users can easily access and auto-update configs, themes, scripts, color schemes, and more.

You can take a look at the implementation of it here: #5226 - which is not completed, but a demo of what we want it to be. We have decided on the name "Marketplace" internally as we do not have a more fitting name to describe it. We could also call it "Resources" - which is probably going to be our official naming of it.

You haven't answered about the fact that, with Nextgen, you need AT LEAST 3 cores (1 of them reserved for the system, the other for Java, the other for Chromium), but with Legacy, you only need 2 (1 for the system, the other for Java).

[1zun4]

What a kind hearted Samaritan!

We've been making LiquidBounce free for everyone for 8 years with active support, paying designers and developers to make features for LiquidBounce, while supporting open source standards and being FREE to use. If you don't like what we're doing, please don't use any of my other work, including legacy - find another organization with those kinds of standards.

[1zun4]

You haven't answered about the fact that, with Nextgen, you need AT LEAST 3 cores (1 of them reserved for the system, the other for Java, the other for Chromium), but with Legacy, you only need 2 (1 for the system, the other for Java).

Hyper-Threading has been a thing since 2002.

[opZywl]

save legacy the LEGEND can’t stop

[localpthebest]

Legacy runs way better on my PC. And I can understand your push for nextgen because you have financial incentives for developing this client - you're not doing it out of goodwill. The better the brand image, the more people download it, the more money you make. That's why your reasoning didn't make sense to me because it wasn't the actual reason. Configs and themes breaking? Configs and themes from years ago shouldn't work now anyway; they're useless. The themes never looked good because of the abomination you cooked, and it's actually starting to look better now. So, old themes working is, as I said, useless. The configs breaking is because of major changes that I think won't be happening every update. You having to resort to scummy tactics to remove competition from your own client that is being maintained by the community is nothing short of circus theatrics. If you're gonna do something don't lie out of your ass next time.

The claim that we are stopping LiquidBounce Legacy for financial incentives is incorrect. In fact, we make money from Legacy without doing any work on it, so there’s no financial gain in discontinuing it. Our goal is to provide the best possible experience for users, and Legacy does not align with what we want LiquidBounce to be moving forward.

He plans to create an ecosystem around nextgen. There's an ominous branch named marketplace I wonder what that does. And the themes didn't look good at all so a revamp was and still is needed.

Yes, we are working on creating an ecosystem around Nextgen to make the client more user-friendly and appealing. However, there seems to be a misunderstanding about our intentions. The marketplace is not planned to include any payment options. Its purpose is simply to provide a centralized hub where users can easily access and auto-update configs, themes, scripts, color schemes, and more.
You can take a look at the implementation of it here: #5226 - which is not completed, but a demo of what we want it to be. We have decided on the name "Marketplace" internally as we do not have a more fitting name to describe it. We could also call it "Resources" - which is probably going to be our official naming of it.

You haven't answered about the fact that, with Nextgen, you need AT LEAST 3 cores (1 of them reserved for the system, the other for Java, the other for Chromium), but with Legacy, you only need 2 (1 for the system, the other for Java).

thats not how that works tasks dont max out ur core 100% of the time and cores get assigned to shit as need u could fully run either clients with a single core (depending on how fast that single core is ofc)