DamageParticle 1.2 Upgrade

Konoha Scarlet

Update log: Fixed ConcurrentModificationException when iterating particles, changed the traversal type. Meanwhile reduce the time usage of traversal. Now the particles move more fluently.

Download:

Usage:
Place file 1 and 2 into /LiquidBounce-1.8/scripts,
place file 3 into /LiquidBounce-1.8/scripts/lib

Turn to my GitHub to get more interesting scripts!

23 hours

do i just make a /lib folder in the scripts folder or do i need smting else, i have the core.lib simply put in the scripts folder

CzechHek

@konoha-scarlet Firstly, I think that RenderUtils could be implemented into Core but since autoupdating website is dead people would have to update manually and that could be problematic.

Secondly, Java.type("net.minecraft.entity.EntityLivingBase") is automatically imported with Core, just replace it with EntityLivingBase. This makes it not search all classes for EntityLivingBase and modifying it for Nashorn every tick.

Konoha Scarlet

@czechhek said in DamageParticle 1.2 Upgrade:

replace

Well actually I found some bugs about Minecraft Java classes when using Core.lib. When I was trying to import some class directly, it will throw Exceptions like this:

java.lang.RuntimeException: javax.script.ScriptException: TypeError: function type() { [native code] } is not a constructor function in <eval> at line number 9

(even nothing in line 9 of the script file)
As a result, I used Java.type("class").
Moreover, about the auto update, I suggest that you can directly use GitHub. When the script loads, get the update info and check whether it need to be updated. If so, let it updates the file and reloads.
Hope it's useful.

CzechHek

@konoha-scarlet Yes but that would also need people to update manually and secondly, LB is so trash at this point, everyone is using some different build and to top it off there is this bullshit cross-version that seems cool but absolutely unsupportable. And then there is the nextgen coming up but it really isn't so idk.

Maybe if I get a bit bored I'll update it and do smth on Core repo.

Aftery

well a better option would be to fix liquidbounce itself instead of just core
however imho trying to make scripts liquidbounce in 2021 is a pretty terrible idea, waiting for nextgen is implausible, you wont be able to support the numerous obfuscated pastes and quite frankly unless you're trying to play on some aac3 server its not worth the effort, but even then there are still better options which doesnt cut your framerate in half

Konoha Scarlet

@czechhek NextGen has sooooooo many bugs and it's hard to use, btw I don't want to use 1.17 with Fabric to play in 1.8 servers, that's a crisis to low performance computer like what I'm using to run VisualStudio, Eclipse, IDEA, Office, Photoshop and Premiere. Literally my small laptop is overwhelmed and I have no money to get a new one.

mems

@konoha-scarlet said in DamageParticle 1.2 Upgrade:

@czechhek NextGen has sooooooo many bugs and it's hard to use, btw I don't want to use 1.17 with Fabric to play in 1.8 servers, that's a crisis to low performance computer like what I'm using to run VisualStudio, Eclipse, IDEA, Office, Photoshop and Premiere. Literally my small laptop is overwhelmed and I have no money to get a new one.

Could you tell me what type of bugs does the client have?

END3R1355

@aftery said in DamageParticle 1.2 Upgrade:

trying to make scripts liquidbounce in 2021 is a pretty terrible idea

Nextgen might discontinue the support for old scripts

waiting for nextgen is implausible

its in nightly rn

unless you're trying to play on some aac3 server its not worth the effort

yep

there are still better options which doesnt cut your framerate in half

yes

CzechHek

@e-nder1355 said in DamageParticle 1.2 Upgrade:

Nextgen might discontinue the support for old scripts

nextgen will be utterly non-compatible: 1.17x1.8, GraalJSxNashorn

its in nightly rn

there are literally no commits in several months, no script api, no graaljs, no themes, bugs, etc.