The first REMATCH Netcode 2.0 beta update, dated November 6, 2026, adds three input-delay profiles and network indicators. Players can choose whether to prioritize consistency or responsiveness.
The update applies to the beta, which can be launched through the Rematch Beta Test application in your Steam library. The patch notes also detail a fix for an issue following tackles and a known issue involving the goalkeeper.
Key points
- Three profiles offer delays of 33, 50 or 67 ms.
- Standard is selected by default at 50 ms.
- Icons indicate high latency, unstable ping and packet loss.
- The beta can be launched through Rematch Beta Test on Steam.
Input-delay profiles and fixes
The Network Consistency setting offers “Prioritize Consistency” at 67 ms, “Standard” at 50 ms and “Prioritize Reactivity” at 33 ms. Standard is the default choice. An on-screen indicator shows which profile is selected.
According to the team, Standard should provide good network conditions for players whose ping reaches or slightly exceeds 100 ms. This is an estimate and does not guarantee the same result for every connection.
The update also rearranges the order of ticks, with the stated aim of gaining one frame of input responsiveness. It includes a fix for an issue that could prevent a player from accelerating properly after making a tackle while stationary.
What the network indicators show during a match
New icons signal high latency, unstable ping or packet loss. They also appear near other players’ names, showing the type of network issue and which player is affected.
The trade-off between profiles comes down to the displayed delay: “Prioritize Reactivity” offers 33 ms, compared with 67 ms for “Prioritize Consistency”. Their names indicate whether responsiveness or consistency takes priority. The beta also adds an option to resize other players’ names.
Beta access and limitations
To try these changes, launch Rematch Beta Test from your Steam library if the application appears there. The notes do not specify the eligibility requirements for the beta.
A known issue can cause the ball to freeze after a goalkeeper catches it, before returning to the attacker’s feet. The team also plans to temporarily disable the Visual Logger during the weekend following the update, then re-enable it the following Monday. According to the developers, this debugging tool is enabled only in the beta and affects performance.
Netcode 2.0 remains in development, and the team is tentatively aiming for a December release, with no exact date announced. Beta participants can choose a delay profile and watch the connection indicators during matches.
See also the REMATCH game page, our article on REMATCH Season 6 and Netcode 2.0 and our article on the REMATCH Season 6 changes planned for October 23.
