Players’ opinions of Mortal Kombat 1 are still controversial, and now there’s an additional issue to worry about.
Currently, the relevance of Mortal Kombat 1 stems from the issues it presents rather than its positive reception. Prior to its widespread distribution, early access players provided critical feedback regarding its playability and numerous bugs, resulting in a chaotic and unsatisfactory gaming experience. While console players primarily express frustration over occasional bugs, Nintendo Switch players have encountered the most severe consequences.
Despite their tardiness, NetherRealm acknowledged their failure to adequately assess the game prior to its release and pledged future updates for all versions of Mortal Kombat 1.
These updates encompass graphical enhancements for the Nintendo Switch and the resolution of bugs that render the game unplayable during matches, such as characters becoming trapped or glitching outside the designated arena.
Two weeks following its launch, players have now discovered a significant bug that significantly alters gameplay and unfairly disadvantages the second player in a match. This bug affects both single and multiplayer modes, which is particularly surprising. The bug manifests as a bias towards the Player 1 character or the player who joined the game first in multiplayer scenarios.
To provide further elaboration on the active bug, it enables player 1 to successfully execute combos without any issues, whereas player 2 is unable to perform the combo at all. This problem persists across all versions and ports of Mortal Kombat 1 and has been documented as a list of bugs to be addressed on the game’s official website.
This particular bug may be attributed to granting an advantage to the first player who initiates the match or creates the room, as inputs must first pass through player 1.
As previously mentioned, this bug also affects multiplayer functionality. Therefore, it is strongly recommended to refrain from engaging in multiplayer activities until a patch that rectifies the bug is released.
Although the exact release date is uncertain, as it has been officially acknowledged as a future fix, it is expected to become available in the near future.