@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.
