Sprinting replication issue

[Apple43YT (aden)]

Hey guys, thanks for reading.

I have a sprinting system set up on a branch which is triggered by my Left Alt key. Along that, I made a supporting system which will stop your character from sprinting again when you stop moving, regardless of whether you’re walking or sprinting. I also set up a little bit of replication to allow clients to sprint as well.

My problem is that my server character only has to press Alt once while moving, but my client character has to press it twice while moving. Any ideas to fix this replication issue?

Below are my blueprints. Thanks for reading!

[Rev0verDrive]

You are using CMC so you have to abide by CMC rules.

Input → Apply new speed to your controlled character, then RPC server to apply new speed to its copy of the character.

Here’s a recent post where I note sprinting mechanics.

Need help with Client Replication I think

All that jitter is caused by client fighting server correction. The server is the authority. Whatever it says is true… is true. So as HOST your inputted actions are the authority. But as a connected client they are not. Skeletal mesh movement (animation) is state driven. You do something in the character class, it sets a state. The animation class uses those states to determine mesh movement. Based on your post and the vid you’re not setting states properly and you’re not sending the server RP…

[Apple43YT (aden)]

Did some digging for a few hours and found a tutorial. Also cleaned up my other blueprints.

Fully replicated sprint BP down here

[Rev0verDrive]

That’s not correct. There’s no need for multicast. It’s literally bandwidth wasteful.

This is about as easy as it gets.

[Shind1]

This solution is really good, but there is a problem, although the server receives information, it will not send it to other clients without Multicast, or is it just me?

[Rev0verDrive]

Just you.

Max Walk Speed is a replicated variable in the Character Movement Component. Thus the replication system will pass the values down. More so it sets the “Velocity” of simulated proxies.

No need to multicast/RPC anything from the server for this specific scenario.