Shadow_Fox

It is a visual glitch but I’m still having the team look into it.

It is a visual glitch. But I am reporting it to the team to look into.

You should be reissued a reentry ticket through the mail in the next 24-48 hours.

Correct, the situation over RMT, bots, the queues and all the underlying issues or additional porblems tied to these big three is not a simple problem. The team is aware, prioritizing, working hard and constantly trying new things. But so is the problem. Its an ongoing battle that we take seriously and absolutely hate that it has to happen.

We absolutely do care about the queues, sadly though its not fixed with a quick restart. This is a priority of the team and will be investigated and worked on.

NAE will be going down for maintenance at 2pm PST for 2 hours. This is to fix the current dungeon/matchmaking issue.

It’s a visual glitch.

Yup, banner should be going up too!

Oh, good call, LOL, thats just my personal fault I guess. I’m in CA with the office and we always default to PST. I’ll keep that in mind for future posts. Sorry about that!

Letting the team know to do that too, thank you for letting me know!

Oh! Letting the dev know to get that up too. Let me know when that shows?

Yes! Thank you so much for letting me know! Sweet!

Thank you!!

I took the feedback from yesterday’s emergency restart very seriously and pushed hard to give everyone atleast an hour of heads up.

The team is creating the message now and should be showing up shortly. Could you let me know if you see it in 15min?

NAE will be going down for maintenance at 2pm PST for 2 hours. This is to fix the current dungeon/matchmaking issue.

NAE will be going down for maintenance at 2pm PST for 2 hours. This is to fix the current dungeon/matchmaking issue.

Some of this conversation is connected with the current matchmaking issues, please comment there and watch there for any updates. Thank you!

This is connected with the current matchmaking issues, please comment there and watch there for any updates. Thank you!

The team is sending in QA now to test the extent of the issue.