I got more information! This actually occurs with the standard template if you set up a basic system with network emulation on. This doesn’t appear to be due to conflicting information.
From what I can tell. When the client says it first, it updates it immediately (as it should with client prediction). But the now outdated information is still being sent from the server, also normal. The issue only arises due to the outdated information (outdated being used lightly due to the server being the authority) forcing the client back to the state it was just in, since the way the server sees it, it’s moving too fast and therefor resets it. Then the information reaches the server, and it says “OH WAIT! You were right! Let me reset you back to where you were.”
Long story short, I need a node that runs clientside that disables correction for a brief moment until the server retrieves the data, or a way to ensure that the server acknowledges a potential sprint immediately before it gains the aforementioned data.
If someone knows how to go about this, I’d appreciate it if someone could tell me!