There will be modules for 1.9+ pvp/exploits, right? we will (probably) somewhat recreate the physics of each Minecraft version that will be supported by the client which will then prevent people from getting flagged that way.Īpart from that I'm not really aware of any other cons, but feel free to enlighten me what other cons there might be. We'll try to maximize the pros over the cons, so e.g. Well, that has some cons and pros tbh but, I wish that happens! I have a dull feeling that no one will use lb and no one will want to do scripts anymore, because you don't want to get used to the 1.16 scripting language, because all other clients except Liquidbounce will run on the 1.8. And the 1.16 code is very different from the 1.8. Whereby the scripts will not be compatible anymore. I guess that there will be some bypasses in January. Porting Liquidbounce to 1.16.3, adapting it to 1.8 and adding 1.8 features will be very difficult and take a long time. You will do that as well, but that also means that it will take even longer until bypasses updates for Liquidbounce will be released. It is clear that a fabric viaversion will make sure that you can join the 1.8, but many features that were added with the versions have to be fixed. Let's hope that no problem appears.įurthermore lb is on the 1.16. Fabric will probably have its problems too. But the "crossversion" took much more effort. In the beginning we were told that this was a great idea. Especially because we don't know if this 1.16 Fabric is not as stupid as the "crossversion". Before there will be no updates for another 4 months, because the version will be changed again, it would be better to calculate the current version. It's just that Liquidbounds is totally outdated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |