Thanks for the report; this is a weird one. A couple engineers were looking into the logs here, and it looks some server disruptions we were having during this time were likely responsible. Just prior to this, did you happen to cancel and re-queue for matchmaking, or wait a longer-than-usual time in matchmaking? Knowing that would help point to how this might happen.
Incidentally, before this I had left the game open (inactive) for a relatively long time (probably not more than a couple hours), and then the first time I tried to queue into a game I got an error saying I needed to re-authenticate, kicked me to the home screen after I selected reconnect but I assumed the queue was cancelled successfully.
Edit: Also thanks for the reply, I hope it can be resolved :D as a developer, imagining the pain of solving a network bug like this one seems to have been sounds very annoying.
Thanks for the followup; that's the kind of scenario we suspected might be involved. It seems like, due to the server communications issues we were having, you ended up paired into 2 matches at the same time. Thanks again for the report, and we'll keep digging in to how this could happen.
I assume from your response you already have them, but I do have the logs available if you need them, let me know.
Is it possible I would receive any kind of compensation for it? As a new-ish f2p player (aside from the starter $5 bundle) the 5k gold for a draft does hurt me a bit. Should I submit a ticket?
Submitting a bug report with those logs would be helpful; we have the server logs, but there's additional info in your client logs. And definitely submit a ticket for reimbursement for something like this.
devtrackers.gg