Rematch has just rolled out its latest update, version 1.20.004, bringing a range of improvements aimed at enhancing the overall gameplay experience. Here are the official patch notes for the Rematch 1.20.004 update.
Rematch 1.20.004 Update Patch Notes
Save Files:
- (Steam only) Better handling of the save files to avoid potential crashes and remapping issues for Beta 2 players.
Notes :
- This will reset settings for all players (including keybinds, sensitivity, display settings, etc.)
- This will reset the Workshops’ progress and medals
- Players will go through the “first launch” options even if they have already gone through it once.
- This will NOT affect customization, inventory and profile progression (XP, ranking points, currency and Captain Pass tokens). This data will be properly retrieved as soon as players log in to Sloclap Online Services.
Matchmaking:
We have tweaked our matchmaking algorithm to reduce the waiting time to find a match, both in Casual and Ranked queues. This will be more noticeable at higher ranks. High and top ranked players should see a significant decrease in queue times. Solving matchmaking issues is very much a balancing act between match quality and queue times, and we want to make sure we move forward carefully. We will continue to monitor the situation and rely on player feedback to improve Rematch’s matchmaking.
Store:
- Fixed price display in Korean.
Rematch is a game with a lot of complex interactions between mechanics and even the smallest change can have a big impact on how the game is played. At the same time, we must be able to answer serious issues in gameplay in a timely manner. Our objective is to refine this balancing act between the pacing of fixes, and the stability of the game and its mechanics. We admire the way players have come up with new emergent mechanics and advanced techs, some of which add a healthy amount of depth to the game, but some of these unintended mechanics cause more harm than good, and we think they should be removed from the game. We will post a new devblog about these emergent mechanics and our intentions about how we, as developers, wish to deal with them.
