Janmm14
Janmm14
*/aac debug
Problem seems to be that there are two velocities applied nearly at the same time. @konsolas has already planned to improve such situations in a future update.
The problem is this: ``` [22Mar2021 11:19:51.370] [Render thread/INFO] [CHAT] 9544 TreizeKushrenada move: velocity 0.0000,-0.0784,0.0000 [22Mar2021 11:19:51.907] [Render thread/INFO] [CHAT] 0080 TreizeKushrenada move: velocity 1.1791,0.4000,0.2223 [22Mar2021 11:19:51.915] [Render thread/INFO] [CHAT]...
@Rawxdealz Please write that comment in the new issue I created for you.
tickbase and backtrack both alter percieved latency to simulate client recieving packets later at certain times. what he describes as teleport is the client faking to have like 250ms latency...
faking lag in client tick thread leads to changed percieved latency from server pov.
The current behaviour is intended. AAC 5 has no general violation center anymore. When the analysis runs, it gets current score of each check. It does not save last score...
@Slimerblue22 That does not exist, it was an idea I just came up with.
https://github.com/konsolas/ConditionalCommands/pull/15
already exists, built in the move check