v2 api script scripts not identified in liquidbounce.
-
Hello, I have a problem, surely you can help me, I have no programming idea.
Well, the problem I have is that the scripts that contain /// api_version = 2 are not identified, they are simply not identified in liquidbounce, they are in the "scripts" folder but they are not identified in liquidbounce, this happened when my core was updated automatically to version 3.12, with core 3.11 or 3.1 if it worked for me.
Does anyone know why this is? -
Hello, I have a problem, surely you can help me, I have no programming idea.
Well, the problem I have is that the scripts that contain /// api_version = 2 are not identified, they are simply not identified in liquidbounce, they are in the "scripts" folder but they are not identified in liquidbounce, this happened when my core was updated automatically to version 3.12, with core 3.11 or 3.1 if it worked for me.
Does anyone know why this is?I think something is broken in core, I can't get core scripts to work .-.
-
Don't see any reason of that happening, everything is working fine for me.
Send logs, what am I supposed to do without any info.
-
@CzechHek Now that I realize it, Inventory Manager does work for me, but scripts like ScaffoldFix or PacketCounter don't.
@robertitohack That isn't caused by Core or any update of it. All scripts that modify packets or use LB utils have to be changed with cross-version builds. I won't do that since it would drop support for official stable build B72. And also they won't finish the cross-version since it wasn't a good idea and they will rather develop fabric version of LB. It's extremely buggy as well so I see no reason to use it. And to top it off, there isn't any documentation for cross-version scripts so why would I even bother fixing them.
Go back to last non cross-version b73, b72 or some custom non cross-version LB.
-
@robertitohack That isn't caused by Core or any update of it. All scripts that modify packets or use LB utils have to be changed with cross-version builds. I won't do that since it would drop support for official stable build B72. And also they won't finish the cross-version since it wasn't a good idea and they will rather develop fabric version of LB. It's extremely buggy as well so I see no reason to use it. And to top it off, there isn't any documentation for cross-version scripts so why would I even bother fixing them.
Go back to last non cross-version b73, b72 or some custom non cross-version LB.
Ok. Please enter a longer post. Posts should contain at least 8 character(s).
-
@robertitohack That isn't caused by Core or any update of it. All scripts that modify packets or use LB utils have to be changed with cross-version builds. I won't do that since it would drop support for official stable build B72. And also they won't finish the cross-version since it wasn't a good idea and they will rather develop fabric version of LB. It's extremely buggy as well so I see no reason to use it. And to top it off, there isn't any documentation for cross-version scripts so why would I even bother fixing them.
Go back to last non cross-version b73, b72 or some custom non cross-version LB.
@CzechHek said in v2 api script scripts not identified in liquidbounce.:
And also they won't finish the cross-version since it wasn't a good idea and they will rather develop fabric version of LB. It's extremely buggy as well so I see no reason to use it.
Wtf Fabric version, WHAT THE FUCK????? How can someone have such terrible ideas like that
-
@robertitohack @hahayes
Your problem wasn't caused by Cross-Version, could have said that you aren't using it.
KrUtOy sent me log containing the exact cause of this problem and I managed to sort it out, it will get fixed via auto update.Explaining:
-
@robertitohack @hahayes
Your problem wasn't caused by Cross-Version, could have said that you aren't using it.
KrUtOy sent me log containing the exact cause of this problem and I managed to sort it out, it will get fixed via auto update.Explaining:
-
@robertitohack @hahayes
Your problem wasn't caused by Cross-Version, could have said that you aren't using it.
KrUtOy sent me log containing the exact cause of this problem and I managed to sort it out, it will get fixed via auto update.Explaining:
@CzechHek Thanks, it's solved.
