Original Post — Direct link
So I was playing my second game of the event when all of a sudden a window popped up with the penalty etc.
I haven't played in a while so it couldn't be some old punishment I've yet to redeem but I also didn't leave while the match was playing.
Now I'm wondering what happened. Is this a glitch or something?
over 3 years ago - UbiKoreanBBQ - Direct link
Hey there PvtDjMarsman! Sorry to hear this happened! Can you let me know if you cancelled out of any matchmaking queues prior to joining the Sugar Fright Event match that gave you the sanction?
over 3 years ago - UbiKoreanBBQ - Direct link
I see, thank you for explaining! The team has been looking into mid-match sanctions and the causes behind them. Can you let me know if the abandonment sanction you received mid-match forced you out of the match?


UncleFaxz, I'm so sorry you lost MMR as a result of this ban. Did you also leave any matchmaking queues prior to the game that you received the sanction in?
over 3 years ago - Ubi-Viral - Direct link
Originally Posted by PvtDjMarsman
I'm sorry for the late reply! Good to know it's being looked into hahaha.

The sanction luckily didn't quit my match. I could still play. The actual 'ban' came after the match.
Thank you for getting back to us and confirming this.

Did you also leave any matchmaking queues prior to the game that you received the sanction in?
over 3 years ago - Ubi-Viral - Direct link
Originally Posted by PvtDjMarsman
-played a game of the event (no prior games)
-finished that game
-went automatically to the searching que for a new match
-quit that one because it took a while (so yes, I, I guess I did leave a matchmaking queue hahaha)
-searched for a new match again
-found new match
-got sanctioned in the middle of the round
It could be due to leaving the matchmaking que, how long were you in it for?
over 3 years ago - Ubi-Viral - Direct link
Originally Posted by PvtDjMarsman
I was in the que for about 3 minutes. And because this sometimes happen in the normal gamemodes aswell and restarting seems to fix this I did just that hahaha
The only thing I can think of is that it had found a match just before you left the que.