Why forks don't merge their changes with legacy liquidbounce and dont helping in developement?
-
@Gabriel Yeah, the UI doesn't look dated but it doesn't look "modern" to say the least.
Also on the config side there's just a few things missing which would be a great help, for example Vulcan speed which could be easily taken from LB+R or fdp. I also have no alts to use anymore to make configs and with thealtening being dead and easymc support being removed there's not much I can do. -
-
@Gabriel I am agree with snowball effect. In addition I can say I caught myself on what I am more interesting for any project fork, instead original project. Maybe it is one of reason, why forks 'more active' than original liquidbounce.
-
@cxtspnzwzd People also think that LiquidBounce is discontinued, which is totally false.
-
I don't expect people not to think that the client is discontinued when b73 took almost 2 years to release because of a severe screw-up. With that being said there are some who don't even know that b73 got updated, they probably don't even know the client's version is 10 numbers ahead lol
-
C cxtspnzwzd marked this topic as a question on
-
After all those recently rejected pull requests with "skidded" code, I came to the conclusion that this is the main cause of inactivity when compared with other forks.
Perhaps such code should be tolerated, if it gets modified to work within LB or even if it works better than original?
-
I would happily merge any pull request under these rules:
A person actually came up with this bypass
The code is ORIGINALLY from a LiquidBounce fork and then it may have been used by paid clients / clients that don't share the same license as LiquidBounce.And as we speak, this lad uploaded a new pull request:
https://github.com/CCBlueX/LiquidBounce/pull/1339/files
How can I now know if this is really not stolen and he actually came up with this? Secondly and no disrespect towards him, but it has been repeatedly shown he doesn't really know how to code or have some sort of idea how to put something in a module and make it work. By the bad indentation I can tell he simply pasted the code from some client that as of now I don't know if it's from a LiquidBounce fork.
closed added new crit mode. #1339
-
@mems How would you feel about me trying to merge something like this?
https://www.bilibili.com/video/BV1JL411C7dh/?spm_id_from=333.788.recommend_more_video.0
(I'm not Chinese It's just the only video if it I could find.)It's from KevinClient Reborn and im 99% sure no other client has this that I've found so far. Pretty sure I could make some improvements to it aswell due to the glide aspect of it being pretty inefficient.
-
Just make sure it's under the second rule I stated:
The code is ORIGINALLY from a LiquidBounce fork and then it may have been used by paid clients / clients that don't share the same license as LiquidBounce.
If the guy who made it stole it from a non-LiquidBounce fork, then sorry but no. If not, then feel free to make one.
-
real most hardest to find bypass
mc.thePlayer.motionY = mc.thePlayer.ticksExisted % 2 == 0 ? -0.2 : -0.1; -
@Plumer-Man yeah, i made a script out of it to try and it was terrible
-
@mems Actually, FDPClient made the original AAC5 Fly, and had it's own AAC5 velocity values that do the same thing that Rise's later AAC5 Fly did. Also, Rise severely skidded from LiquidBounce (at least 5.90-5.100), with proof being here (I found it myself). It's just that some clients are too big to fail, so the developers resort to skidding, though I haven't seen skidded code in 6.0 yet.
