Saiba Cryptomancer
Hello, I was playing in the Arena Open, and the client failed to stop at end of turn for a Flash spell in hand. As a result, I was unable to cast the flash spell as planned (and as I should have naturally been able to), and was forced into an unfavorable position, one that seems to have lost me the match considering the board state. When playing with a 5000 gem ( or approx $25) entry fee, and with $2000 on the line, this is an unacceptable client fail, and I would like to be reimbursed for my entry into the event. I will include screenshots from the 17lands.com replay. In Screen1, You'll be able to see I had the 2 mana open (1 island and 1 plain), and in Screen2, you'll see that the spell I intended to cast is uncast because the client auto-skipped over my end-step despite the flash spell. Thanks.
Upon investigation, this appears to be a bug rather than a priority issue. I’m very experienced playing on the Magic Arena client. The card in question was the flash creature, Saiba Cryptomancer. Arena does not require players to enter full control at end of turn to cast flash creature spells, rather the client automatically holds priority (assuming the player has open mana to cast the spell).
Initially, I believed the issue might have been caused by an incorrect coding flag on Saiba Cryptomancer, where the game was treating it like a defensive instant spell, and thus skipped priority at the end of turn because no spells where on the stack. However, I recreated a very similar scenario (outside of the event), and the client DID hold end-of-turn priority to cast Saiba Cryptomancer, unlike during the event.
Returning to the initial situation, being that I had 2 open mana (1 blue, 1 white) and there were no cards restricting cast timing (nor any cost increases), the client should have automatically held priority for me to cast Saiba Cryptomancer, and it did not. This suggests that there is a bug in the manner by which the client is calculating the interactions/priority of this specific board state.