[10:17 PM] ʐ̈ MANNNNNNN: Okay, I think I solved the diagonals issue
[10:17 PM] ʐ̈ MANNNNNNN: When two directions are held down and both are blocked, the horizontal direction is always picked, regardless of current direction
^ example, if you hold left and up, in LL you end up moving in the facing direction, apparently in CC2 you'll always move in the horizontal direction
[10:26 PM] Patashu: so on the frame of the desync, the replawy is holding LU
[10:26 PM] Patashu: (after holding U on the previous frame)
[10:26 PM] Patashu: you can see melinda goes from U to L and Cerise doesn't
[10:26 PM] Patashu: then when melinda makes an L move the desync is complete
[10:27 PM] Patashu: me and eevee always thought it was because 'the replay releases L one tic too early', but actually it's because LL and CC2 treat diagonal inputs differently
[10:17 PM] ʐ̈ MANNNNNNN: Okay, I think I solved the diagonals issue [10:17 PM] ʐ̈ MANNNNNNN: When two directions are held down and both are blocked, the horizontal direction is always picked, regardless of current direction
^ example, if you hold left and up, in LL you end up moving in the facing direction, apparently in CC2 you'll always move in the horizontal direction
contrast: https://cdn.discordapp.com/attachments/771512221560995850/916288562192855110/gamimg.gif
and it does appear to explain the desync:
https://cdn.discordapp.com/attachments/771512221560995850/916289202470129714/unknown.png
[10:26 PM] Patashu: so on the frame of the desync, the replawy is holding LU [10:26 PM] Patashu: (after holding U on the previous frame) [10:26 PM] Patashu: you can see melinda goes from U to L and Cerise doesn't [10:26 PM] Patashu: then when melinda makes an L move the desync is complete [10:27 PM] Patashu: me and eevee always thought it was because 'the replay releases L one tic too early', but actually it's because LL and CC2 treat diagonal inputs differently