Closed superblaubeere27 closed 10 months ago
You can fix it by using sync() before you wait for the first time. This is not optimally tho
You can fix it by using sync() before you wait for the first time. This is not optimally tho
I already have a real fix for it, dw. The bug is caused by the ordering of the constructor and fields not being ideal.
LiquidBounce Branch
Nextgen
LiquidBounce Build/Version
latest
Operating System
macOS, Linux, Windows 7, Windows 8, Windows 8.1, Windows 10, Windows 11
Minecraft Version
1.20.X
Describe the bug
If a subroutine waits for n ticks on the first execution, it will only wait until the next tick.
Steps to reproduce
This unit test found the bug:
Client Log
Screenshots
No response