LiquidBounce Forum

I might be a bit late to the party, but that’s not the point. Version 26.1.2 is actually already available, but for now it’s only a nightly build. I reckon the stable build will be released sometime towards the end of this month (that’s not certain, just my guess).

В ликвиде с новыми обновами сломался сброс спринта, не знаю с чем связано давно ждем фикс, но чет не выходит. Я писал для этого скрипт: https://forum.liquidbounce.net/topic/8624/sprint-reset-for-critical-hit
Если у тебя проблема со сбросом спринта он скорей всего его решит.
(Не могу гарантировать что он не баниться, я последний раз тестил на спукитайме там он работает, так что учитывай этот момент)
With the latest updates, the sprint reset feature in Liquid has broken. I don't know why, but we've been waiting for a fix for a while, but it's still not working. I wrote a script for this: https://forum.liquidbounce.net/topic/8624/sprint-reset-for-critical-hit
If you're having trouble resetting your sprint, this will likely fix it.
(I can't guarantee it won't get banned; I last tested it on spookytime, so keep that in mind.)

@kawaiinekololis
Yes, according to Minecraft mechanics, a critical hit is already possible on the 11th tick, which is around 0.92 cooldown. However, regardless of what value is set in Item Cooldown, the attack still happens only on the 12th tick (around 1.00 cooldown). This happens not only in Always Criticals, but also in Smart Criticals. In both cases the module waits for almost a full cooldown, even though a critical hit is already possible earlier. So as I mentioned before, a critical hit is already possible on the 11th tick, but the system still attacks only on the 12th tick, which wastes a small amount of time.

I also attached a video on GitHub showing this behavior in case the message is unclear.

Regarding Always Criticals Mode — as I mentioned above, this issue also affects Smart Criticals. In both cases, critical attacks happen only on the 12th tick. And yes, to some extent I agree that Smart mode is better, because the game is not always perfectly smooth. For example, even a simple knockback can interfere with performing a critical hit, which sometimes causes Always mode to lose DPS compared to Smart. However, as can be seen from the issue description and the examples shown on GitHub, Smart mode also does not work perfectly and sometimes misses critical hits.

Second version: SprintResetV2.js
It's essentially no different from the first, but the code is less "hacky" and smarter.

I'll try to be as brief as possible.
Item Cooldown isn't working correctly and is very confusing. Let's start from the beginning.

1. The processing is incorrect – the entire cooldown you want to set needs to be reduced by ~0.08 (if I calculated everything correctly). Why? I don't know; that's just how Minecraft ticks work. More specifically, when we set, for example, 1 - 1, it doesn't actually hit when the cooldown is at 100%, but rather gives permission to hit (as far as I understand). For example, I set the Item Cooldown to 0.88 (according to Minecraft's cooldown, it's actually 0.96, but I explained above why it needs to be reduced by 0.08). The server counts the hit as 0.99999994 (i.e., slightly less than the full cooldown). We didn't hit at 100% of the cooldown, but we hit at 0.96, but the damage doesn't change. (In fact, it does, but that's how the ticks work.
   A full charge is 8 damage.
   A charge of 0.99999994 is 7.999999046325684 damage.
   This is a netherite sword.)
   So, we hit at 0.96 of the charge, but we were counted as 100% damage, and we still saved 25 milliseconds.
   I think I explained it terribly

2. Item Cooldown doesn't work with Always Criticals mode.
   Why? Because Always always wants to hit at full charge. Although a critical hit is possible starting at 84.8% charge (Well, you can't hit exactly at 84.8%. Why? I don't know, that's how ticks work).
   But we can hit, for example, at 92%. And a critical hit is possible because 92 is greater than the 84.8% threshold. But no matter what value we set for Item Cooldown (in Killaura), it will always hit at 100% (or 99.999994%, to be precise). Why would it be simple to always hit at 100% cooldown? Right? Not quite, well, maybe in principle you can hit at 100%, but still, liquid bounces are about flexibility. In any case, hitting before 100% and after 84.8% can save time, which can, for example, increase DPS.

That's about all I wanted to say.

Everything seems to be working fine, but I'll update the script when I find time. Feedback would be appreciated.

Something like this:
"const script = registerScript({
name: "example",
version: "1.0.0",
authors: ["author"]
})"

Or

"script.registerModule({
name: "example",
category: "Combat",
description: "Empty"
}"

I'm not sure exactly what's missing, but I suspect the former.

I'm no expert at scripting. But it's literally written here. You're missing a crucial part of your script.

A fairly simple script that resets sprint by 2 ticks for critical strikes. I made it for personal use because "When Sprinting" in "Criticals" doesn't work or I don't understand how it works. At first, I didn't think of uploading it, but I saw a bug report on GitHub and thought, why not?

Important to use!!!

1. You must have a mode enabled in the "Sprint" module (I recommend Legit). This is necessary for sprint to return after resetting. You can't simply hold down Ctrl, otherwise, the script won't reset sprint.
2. Turn off "When Sprinting" in module "Criticals". Otherwise, the script will reset sprint even when you don't have KillAura enabled.

Perhaps the script is not ideal from a coding point of view, but it works in the game and I personally am happy with it.

P.S. I'm using a translator because I don't speak English fully. But I think the gist of it was conveyed correctly.

Download: SprintReset.js