REMATCH: Netcode 2.0 heads to beta soon – Sloclap admits Season 5 problems

Published 3 min read
REMATCH Season 5 – Following Up on Your Feedback
Image: Sloclap · Image source

Sloclap is responding to the bumpy release of REMATCH Season 5. In a new developer blog, the studio explains that, without the usual beta test, more bugs than intended made their way into the update. At the same time, the next major technical step is just around the corner: the first beta test for Netcode 2.0 is planned for the first half of October 2026.

The game’s lasting foundations – 5-v-5, third-person controls, platforms and the season model – are covered in our new REMATCH game profile.

Netcode 2.0 rebuilds server communication

According to Sloclap, Netcode 2.0 is not a small patch but a complete overhaul of server-side processing and of communication between server and clients. The aim is more stable and more legible game situations, more consistent sequences and significantly fewer rollbacks.

Fast duels between players, as well as contact between player and ball, may therefore feel different. Sloclap therefore wants to run beta tests first, and announces a more detailed technical developer blog on the new netcode for later this week.

Season 5 went out without a beta, and that had consequences

Normally, the team tests larger updates in advance. With Season 5, this was not possible this time, because several game versions are managed in parallel and the Netcode 2.0 tests are being prepared at the same time. The result: more bugs than planned and additional confusion about which gameplay changes were intended.

Regarding the reworked goalkeeping, Sloclap admits to problems with freely assignable inputs in particular. Some bindings were not adequately taken into account in the update. Future larger system changes should therefore plan for more robust remapping solutions and be explained earlier.

Dribbling bugs collide with deliberately set limits

When it comes to dribbling, the studio is now also drawing a clearer line between bugs and design. The exhausted dribbling state is to remain and, according to the team, forms a basis for further balance work. At the same time, changes to ball control have caused new bugs, including situations in which Defense Mode and Dash do not take over the ball correctly.

Another trick that players had used is deliberately being removed: players could get around the intended limit of two quick dribbles by reactivating the dribbling stance. Sloclap describes this as a bug and does not want to keep such workarounds in place permanently. Instead, new dribbles are to be created in future, and selected techniques will return as official mechanics.

Source: Sloclap – Season 5: Following Up on Your Feedback.

Write a comment
Your name and comment are public. The email address is optional and will not be published.