What Does Rollback Mean In Fighting Games

What Does Rollback Mean in Fighting Games?

Ever played an online fighting game and felt like your punches were landing a little late, or that your character was teleporting around the screen? That’s often due to something called “lag.” Lag happens when there’s a delay between your button press and when it shows up in the game. Rollback netcode is a special way that fighting games handle this lag to make online matches feel much smoother. Instead of waiting for all the information to travel back and forth, rollback makes predictions about what’s going to happen and corrects them if it guessed wrong. Let’s get into the details of how this works and why it’s so important for modern fighting games.

The Challenge: Lag in Online Gaming

Before we dive into rollback, it’s important to understand the problem it’s designed to solve: latency, also known as lag. Imagine you’re trying to play a game with a friend who lives far away. Every time you press a button, that signal has to travel all the way to their computer, and then their computer has to send back what happened in the game. This back-and-forth takes time, and that time is what we call lag. Even with fast internet, this delay can be enough to make online games feel unresponsive and choppy. It makes timing difficult and can ruin the fun of a match, specially in fast-paced games like fighting games.

Input Delay: A Major Headache

A big problem caused by lag is input delay. This is the delay between when you press a button and when the game actually performs the action. With lag, you can press a button to punch but see the punch happen on screen a fraction of a second later. This delay affects player’s timing and precision, making it difficult to pull off combos and react to opponents. In fighting games, which demand precise timing, even a small input delay can make a big difference between winning and losing. So minimizing this input delay is very important.

• Input delay makes combos harder to pull off.
• It becomes difficult to react to your opponent’s moves.
• The game feels less responsive.

The Old Way: Delay-Based Netcode

To understand how rollback is better, we need to look at how online games used to handle lag, which was with something called delay-based netcode. This type of netcode tries to make sure that both players see the exact same thing at the same time. It does this by making each player wait until all the information from the other player has arrived before updating the game. Basically, if you press a button, the game would wait to see what the other player is doing, and then move both characters at the same time.

Why Delay-Based is Flawed

While this approach keeps everyone in sync, it also adds a lot of input delay, depending on your connection. If your internet connection is not good, this delay could be significant, making the game feel slow, unresponsive and frustrating. Imagine pressing a punch button and waiting a whole second for it to happen. It’s impossible to play like this. That’s the problem with delay-based netcode: the worse the connection, the more the delay, and the worse the experience.

• Adds significant input delay.
• Makes the game feel sluggish and unresponsive.
• The amount of delay changes based on connection quality.

Rollback Netcode: A Smarter Approach

Rollback netcode is a much more sophisticated way of dealing with lag. It does this by taking a leap of faith, which sounds a bit strange, but in technical terms, it is a predictive approach, rather than a wait-and-see strategy. It doesn’t wait for information to travel back and forth to the player, instead, the game tries to guess what you and your opponent are going to do and shows you the results immediately. If the guess is correct, you would experience the game like you are playing offline. However, when it makes a mistake, it ‘rolls back’ the game to the correct state. This quick correction keeps the game feeling fast and responsive, with minimal input delay, as compared to delay-based.

How Rollback Works Step-by-Step

Let’s break down how rollback works step-by-step.

1. Prediction: When you press a button, the game predicts what your opponent is going to do and shows you what is likely to happen, assuming there is no lag.
2. Execution: The game shows you the results of your action immediately. Your character moves, throws a punch, or performs any action you initiated.
3. Confirmation: Meanwhile, the game is sending your input to your opponent and receiving their input. This information is not instant, it takes time to travel.
4. Rollback (if necessary): If the game’s prediction is wrong, it quickly and smoothly rolls back to the previous correct state and shows the actual outcome.
5. Seamless Correction: This rollback happens so fast that you probably won’t notice it. The game tries its best to make the correction look like it was always meant to happen.

The Magic of Prediction

The key to rollback is the predictive element. It relies on an algorithm that analyzes previous inputs to make a reasonable prediction of future actions. For example, if your opponent keeps blocking low, the game might predict they will block low again. These predictions are usually correct, making the gameplay feel like an offline experience.

Visualizing Rollback

Imagine a scenario where you throw a punch at the exact same time your opponent throws a kick. With delay-based netcode, both players would wait for each other’s actions, the punch would happen, then the kick would happen, even though they were supposed to happen at the same time.
With rollback, the game might show the punch connect immediately on your screen, based on the prediction. If your opponent’s kick actually hit you first, the game will quickly rewind slightly and show the correct outcome of the kick hitting before your punch. This adjustment looks like a quick correction, instead of a choppy and sluggish change of the game.

Let’s say two players A and B, Player A throws a punch and player B blocks at almost same time,

• Delay-based netcode: Player A punches, the game waits for player B to block and then it shows that B has successfully blocked the punch on the screen of both the players. This would lead to slow response from the game.
• Rollback netcode: Player A punches, the game predicts that the punch will hit the opponent. it immediately displays the punch. If player B blocks, the game rolls back by a fraction of second and shows the block, this all happens so fast that the player usually won’t notice.

Benefits of Rollback Netcode

Rollback has many benefits for online fighting games. It’s becoming the standard for a reason.

Reduced Input Delay

The most obvious benefit is the reduction in input delay. You’ll find your actions happen almost instantly, which makes the game feel responsive, as if you were playing offline. This is crucial for the precise timing required in fighting games.

Smoother Gameplay

The prediction system, with its quick rollbacks, makes online matches feel much smoother. The game looks and feels less choppy, which enhances the entire experience of the gameplay.

Better Overall Experience

Because it reduces input delay and makes gameplay smoother, rollback leads to a better overall experience for players. You can have fun playing online without the frustration of lag ruining your matches.

Increased Competitiveness

With reduced input delay, players can react more quickly and precisely. This makes online matches more competitive and skill-based, rather than just a test of who has the best connection.

Less Frustration

Lag and input delay can be very frustrating. Rollback helps to reduce frustration, letting players focus on the game instead of fighting with their internet connection.

Challenges of Rollback

Even though it offers many advantages, there are some challenges with rollback netcode.

Complexity

Developing rollback is complex and requires a lot of technical skill. It’s harder to implement than delay-based netcode. Games must be designed with this type of netcode from the very beginning.

Occasional Visual Artifacts

Sometimes, you might see a slight visual glitch when the game rolls back. This is usually a small movement of the character that corrects itself quickly. This is a very small drawback as compared to the whole gameplay experience.

Demands on System

Rollback netcode can place more demands on a computer system than delay-based netcode. This means that it may not work well on older systems with limited capabilities. However, most of the modern systems can handle the load without any issues.

Rollback vs. Delay-Based: A Quick Comparison

Here’s a quick comparison to summarize the differences between rollback and delay-based netcode:

Why Rollback is the Future of Fighting Games

Rollback netcode has become more common in fighting games because it has been shown that it makes online matches a much better experience. Modern fighting games need responsive and smooth online play to compete in the market. While it can be a more complicated solution to implement, the end result of the gameplay makes it worth the effort. It lets gamers play with each other without the restrictions of location and with a smoother online play experience. If you’re going to play any fighting game online, having rollback netcode is very essential. If games don’t use it, they’re considered old and bad, even if they are a fun game.

When you play a fighting game online, you should look for one that has implemented rollback netcode, this will ensure you have a fun, competitive and smooth experience.

In summary, rollback netcode is a crucial advancement for online fighting games. It makes online play feel much more responsive and smoother, letting players enjoy matches without lag and frustration. While there are some technical challenges, the benefits of rollback make it a superior solution to delay-based netcode. This will remain the standard for online play and ensures a better experience for all.