MovementUtils.INSTANCE.strafe(0.2)
You may have to input more arguments which are optional in Kotlin, best way is to decompile LB and see how kotlin translated MovementUtils.
MovementUtils.INSTANCE.strafe(0.2)
You may have to input more arguments which are optional in Kotlin, best way is to decompile LB and see how kotlin translated MovementUtils.
@MrScripter what
@moon No, you should join Guilded. LB development is beyond this world, imagine someone helping someone else code something till 8 am. Totally normal.
@Pulubble It shouldn't even work in theory, because support for api v1 scripts has been fully deprecated.
@moon https://github.com/CCBlueX/LiquidBounce/pull/1347
Is this good enough?
@rufus said in Russian translation:
@WDIlsb russian on top from with love VietNam
@rufus That's a bold thing to say these days.
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?
@Gabriel nah, just execute the same commands as with intellij installation and then open the folder with eclipse
@RiceUser Well Core along with any script that uses LB utils doesn't support versions after my kotlin ports of LB from like b76+.
@rthrthwtrhg
Ports to kotlin + removal of unnecessary @JvmStatic means that you have to access LB utils and fields with kotlin getters and static .INSTANCE.
In this case MoveUtils.INSTANCE.strafe(), but its arguments have also changed, you have to put a few booleans as well, look at MovementUtils source.
ScriptAPI should get its own built-in utils to simplify stuff.
@Gabriel onDisable doesn't have any MoveEvent data wtf?!
and Math.radians is undefined
@kawaiinekololis
Well in that case, it should also be mentioned that removal of @JvmStatic and kotlin ports have made some utils in old scripts broken and hard to work with when you don't know how kotlin getters and setters work. Perhaps scriptapi should have its own util references to avoid this?
@BypassFDP https://forums.ccbluex.net/topic/269/add-custom-categories-to-the-liquid-bounce-mod-menu-custom/
(core library source code)
since everything is in kotlin now, you most likely have to do moduleManager.INSTANCE.getModule()
commandManager.INSTANCE....
however this may be subject to change in the future because the documentation doesn't show this and it's not good
@isnotpuppy Probably because of the kotlin ports, however this wasn't expected since:
I will look into this.
@Gabriel Should taking code from forks of your GNU v3 repo be considered as skidding tho?
@cxtspnzwzd It's not that easy to add something into original LB because of its required coding standards, major changes wouldn't also get approved because there isn't any active development on the legacy branch. Many pull request take long to accept or jut get rejected.
@cxtspnzwzd The code of LB was pretty messy when I look back and I have been therefore cleaning it up this year which greatly improved it in my opinion. However, all of these forks have the old LB as their base with some much worse skidded code applied to them. It wouldn't be so easy to just copy and paste because of merge conflicts, different naming schemes and coding conventions.
@Gabriel said in Remember me?:
@CzechHek I started using LB when Hypixel fly still worked on both Jartex and Pika.
5 block expand, faster than sprint scaffold on CubeCraft, with 7 reach, flagless vclipping and hclipping and several infinite flights >>>>