Zendikar Rising Patch Update – Current Issues (Resolved)
The latest Zendikar Rising Game update patch (click here for the patch notes) went live almost 12 hours ago, and in one of the most troubled set launches in MTG Arena history, the development team is working hard to fix the issues as we speak. As the game stabilizes, you may still experience some connection issues during this time. Below is the post from the official forums to keep us up to date:
UPDATED: SEPTEMBER 21 AT 11:30 AM P.T.
LATENCY/NETWORKING ISSUES – RESOLVED
Update: We deployed a client update Friday, Sept 18 at Noon PT to further address some of these issues. Patch notes are available, here. We’re continuing to monitor the situation.
We deployed several updates to alleviate some of the issues related to latency and/or network errors (blackscreens, stuck on “waiting for the server”, disconnects, etc.). While this appears to have improved throughout the course of the day, we will continue to monitor the situation overnight and make additional changes if necessary.
DEBUG CONSOLE – RESOLVED
Update: We deployed a client update Friday, Sept 18 at Noon PT to correct this issue. Patch notes are available, here. We’re continuing to monitor the situation.
Some players have inadvertently ended up on the “Debug Console” (a blue window with their screen name across the top, and various match configuration options such as timers, decks, battlefields, etc.). Players who are in this state do not have access to any of these tools. Regardless, this is not indented behavior and we’re working to ensure do not end up on this console.
Players who experience this can restart their client to get out of this state.
ZENDIKAR BATTLEFIELD AND MOUSE DETECTION – RESOLVED
Update: We deployed a client update Friday, Sept 18 at Noon PT to fix this issue. Patch notes are available, here. We’re continuing to monitor the situation.
Under certain circumstances, players may be unable to target/”mouse over zoom” lands and/or planeswalkers on the opponent’s side of the battlefield. This is a high priority bug for us, and we are currently testing a fix.
Please contact Wizards of the Coast directly if you have any issues with the game: