After browsing similar topics, I found an interesting thread that pretty much confirmed by suspicions. The game code / logic seems to always be waiting for a reply from the server to render animations.
Ex. You play a land, it freezes mid screen and doesn't resolve. The game wont resolve the action until it receives confirmation from the server. Any number of reasons could be causing the issue and it could be the host / server or either player.
As a player, the best thing you can try to do is play on a clean hard line without a lot of other traffic, to try to rule out latency on your end but, my suspicion still lies with the host, MTG:A servers and, game logic.
What I don't understand is why there isn't an in game solution to reconnect. If the server detects connection issues, the client side should notify, save match and, attempt reconnect.
After browsing similar topics, I found an interesting thread that pretty much confirmed by suspicions. The game code / logic seems to always be waiting for a reply from the server to render animations.
Ex. You play a land, it freezes mid screen and doesn't resolve. The game wont resolve the action until it receives confirmation from the server. Any number of reasons could be causing the issue and it could be the host / server or either player.
As a player, the best thing you can try to do is play on a clean hard line without a lot of other traffic, to try to rule out latency on your end but, my suspicion still lies with the host, MTG:A servers and, game logic.
What I don't understand is why there isn't an in game solution to reconnect. If the server detects connection issues, the client side should notify, save match and, attempt reconnect.