8 Frames in 16ms: Rollback Networking in Mortal Kombat and Injustice 2

What people said

c4wrd · 2025-03 · Recommendation

For those who aren't in the video game development field and like technical content, I cannot recommend watching GDC's content enough (even better, attending!). Although this blog post isn't as detailed as I've seen them do in the past, I appreciate that game developers have the opportunity to share their wins like this externally. If you enjoy watching technical content and video games, the following videos are greatly entertaining deep dives into ludicrously technically complicated bugs or performance optimizations done to deliver the gaming experience that I myself take for granted. - I Shot You First: Networking the Gameplay of Halo: Reach: [LINK] - 8 Frames in 16ms: Rollback Networking in Mortal Kombat and Injustice 2: [VIDEO] - It IS Rocket Science! The Physics of Rocket League Detailed: [LINK] - [LINK]

Read the original HN comment ↗

Oberdiah · 2023-10 · Recommendation

Specifically "Deterministic Rollback", as the clients don't wait for the server's response before displaying the change locally. For an in-depth explanation, see this excellent GDC talk on its implementation in Mortal Kombat and Injustice 2: [VIDEO]

Read the original HN comment ↗

dilap · 2021-10 · Recommendation

I guess it depends on how high a level you're looking at it from. Both lockstep and rollback are variants of the general approach of "shared deterministic simulation" where you're mostly just sending inputs. ("Mostly" 'cuz on reconnect or desync or whatever you'll probably want to send full state.) I really enjoyed this GDC talk on rollback networking: [VIDEO] (From 2019.)

Read the original HN comment ↗