Release LiquidBounce b73 already.
-
Never thought I'd make this kind of topic, but here I am.
It's been a few months since the latest version was released and since then things were good, we had updates before b72 was released. So probably the majority of people in this community expected b73 to come sooner or a bit later than they expected, but we now are in a situation where we think about releasing custom builds of LiquidBounce after seeing that an upcoming update messed the whole client up. Props to the dude who spent his time working on a thing called
cross-version, even though it turned out to be a bad outcome. I know that staff who are probably reading the title of this topic will say something like:fixing/updating modules + render stuff is not easy, I know that it is hard as I've also experienced what it looks like to be left with bugs, etc to fix, but come on. It's been awhilesince we got the latest version and I know that I can download a b73 version on the nightly builds box, but hey, make it official, for the sake of New Years. Whatever it is, pull requests, issues, bypasses to add, all that stuff which are currently on the TODO list, just throw them on the next version (b74). I know there are bugs to fix, but lately, the majority of them (render/module issues) arefixed. There is almost nothing to worry about except for a few other module bugs such as XRay or performanceissues.Feel free to state your opinions on this, if you're interested in reading a huge ass message and replying. Just wanted to make it so the developers of LiquidBounce would catch their breaths and finally focus on the upcoming update, 1.16.4 LiquidBounce, aka nextgen.
-
-
Never thought I'd make this kind of topic, but here I am.
It's been a few months since the latest version was released and since then things were good, we had updates before b72 was released. So probably the majority of people in this community expected b73 to come sooner or a bit later than they expected, but we now are in a situation where we think about releasing custom builds of LiquidBounce after seeing that an upcoming update messed the whole client up. Props to the dude who spent his time working on a thing called
cross-version, even though it turned out to be a bad outcome. I know that staff who are probably reading the title of this topic will say something like:fixing/updating modules + render stuff is not easy, I know that it is hard as I've also experienced what it looks like to be left with bugs, etc to fix, but come on. It's been awhilesince we got the latest version and I know that I can download a b73 version on the nightly builds box, but hey, make it official, for the sake of New Years. Whatever it is, pull requests, issues, bypasses to add, all that stuff which are currently on the TODO list, just throw them on the next version (b74). I know there are bugs to fix, but lately, the majority of them (render/module issues) arefixed. There is almost nothing to worry about except for a few other module bugs such as XRay or performanceissues.Feel free to state your opinions on this, if you're interested in reading a huge ass message and replying. Just wanted to make it so the developers of LiquidBounce would catch their breaths and finally focus on the upcoming update, 1.16.4 LiquidBounce, aka nextgen.
@mems Nope. Marco/Senk Ju just should delete this bloody mess and upload old b73 src back, instead of fixing this bloody mess. (7276ffa as far as i remember) Cross-version 1.8.9 is 1.12.2 Minecraft with wrapped OpenGL and gameengine. If they did not wrap it, just change MC version and remove 1.9+ blocks & mechanics, we could have no issues.
-
For example, if you will wrap OpenGL 3 in MC 1.12.2 you will have alot of issues
-
@mems I think, Verdana font is pretty normal & not bulky (I've this font in arraylist in my own client)
-
@idk-my-name said in Release LiquidBounce b73 already.:
@mems Nope. Marco/Senk Ju just should delete this bloody mess and upload old b73 src back, instead of fixing this bloody mess. (7276ffa as far as i remember) Cross-version 1.8.9 is 1.12.2 Minecraft with wrapped OpenGL and gameengine. If they did not wrap it, just change MC version and remove 1.9+ blocks & mechanics, we could have no issues.
I've thought of that too, and I actually think that it's a good idea, then we can add our good stuff and keep this shit going.
-
We are not going to release b73 as a offical version, it will stay as development build forever.
We are not going to release any new updates until we're ready to publish our nextgen version of LiquidBounce.I feel like there is no reason to publish the b73 as a offical version. Of course there are many new features and just a few left over bugs which are easy to fix and we could just solve the compability problems with the wrapped classes and scripts, but I'm not really sure about it.
-
We are not going to release b73 as a offical version, it will stay as development build forever.
We are not going to release any new updates until we're ready to publish our nextgen version of LiquidBounce.I feel like there is no reason to publish the b73 as a offical version. Of course there are many new features and just a few left over bugs which are easy to fix and we could just solve the compability problems with the wrapped classes and scripts, but I'm not really sure about it.
@kawaiinekololis, have you ever thought of reverting those commits? (when cross version happened)
-
We are not going to release b73 as a offical version, it will stay as development build forever.
We are not going to release any new updates until we're ready to publish our nextgen version of LiquidBounce.I feel like there is no reason to publish the b73 as a offical version. Of course there are many new features and just a few left over bugs which are easy to fix and we could just solve the compability problems with the wrapped classes and scripts, but I'm not really sure about it.
@kawaiinekololis said in Release LiquidBounce b73 already.:
We are not going to release b73 as a offical version, it will stay as development build forever.
We are not going to release any new updates until we're ready to publish our nextgen version of LiquidBounce.I feel like there is no reason to publish the b73 as a offical version. Of course there are many new features and just a few left over bugs which are easy to fix and we could just solve the compability problems with the wrapped classes and scripts, but I'm not really sure about it.
So then are you guys goin to the 1.x.x update style?
-
We are not going to release b73 as a offical version, it will stay as development build forever.
We are not going to release any new updates until we're ready to publish our nextgen version of LiquidBounce.I feel like there is no reason to publish the b73 as a offical version. Of course there are many new features and just a few left over bugs which are easy to fix and we could just solve the compability problems with the wrapped classes and scripts, but I'm not really sure about it.
@kawaiinekololis said in Release LiquidBounce b73 already.:
We are not going to release b73 as a offical version, it will stay as development build forever.
We are not going to release any new updates until we're ready to publish our nextgen version of LiquidBounce.I feel like there is no reason to publish the b73 as a offical version. Of course there are many new features and just a few left over bugs which are easy to fix and we could just solve the compability problems with the wrapped classes and scripts, but I'm not really sure about it.
Revert it back to before cross version????
-
@kawaiinekololis said in Release LiquidBounce b73 already.:
We are not going to release b73 as a offical version, it will stay as development build forever.
We are not going to release any new updates until we're ready to publish our nextgen version of LiquidBounce.I feel like there is no reason to publish the b73 as a offical version. Of course there are many new features and just a few left over bugs which are easy to fix and we could just solve the compability problems with the wrapped classes and scripts, but I'm not really sure about it.
Revert it back to before cross version????
-
There is no point in reverting as we are currently rewriting LiquidBounce anyway. The next release will be based on that recode.
@senk-ju, how long will it take for the next gen LiquidBounce to be released?
-
@senk-ju, how long will it take for the next gen LiquidBounce to be released?
-
@ohno if the developers work hard for it every day or just once in a while?
-
@ohno if the developers work hard for it every day or just once in a while?
