MageQuit Dev Tracker

Wow, thank you for the insight, AllegedBanana! That is very helpful :)
Azure support got back to me and it sounds in line with what you are saying regarding ICMP.
There is a tool called PsPing that can circumvent that.

ScienceDiscoverer, the first thing Azure support requested was for you to try using PsPing to reach the MageQuit matchmaking server. Would you be willing to try this?
There are instructions for it here: http://www.azurespeed.com/Azure/PsPing

After installing that you would run "psping 40.121.22.148:8081"

From Azure support: Successful pspings from a source that can't access the matchmaking would tell us there's something happening above layer 4, and the Azure platform is ok.

Thanks again for your patience!

Brett

Alright! I have successfully opened a technical ticket with Azure Support. Now we wait...

That's my hope! I really appreciate your patience on this. How about if the fix takes longer than 2 weeks, you can refund it and I'll give you a key for your trouble :)
Currently I have a billing ticket open with Azure because I am unable up create a technical ticket even though they definitely billed me for it LOL. I will try again in the morning.
We'll get to the bottom of it!

Okay, this IS interesting. It appears to be an issue on the Azure side then, because clearly your request is reaching their servers. I'm attempting to pay them for technical support but it saying it's currently unavailable. I will keep trying and we will figure this out!!

Brett

Assuming that doesn't work, would you be able to run a command for me and report back what it returns?

tracert matchmaker.magequit.com

Okay, I expected everything mentioned except for that last part about it not working for your other provider as well.

I've loosened up the Azure firewall restrictions for the matchmaking VM just to see if that makes a difference at all for you. Please let me know if the responses are any different (or if Online magically works for you now).

If not, I'm going to open up a support ticket with the Azure team to see if something could be causing this on their end.

Thank you for your patience!!

Brett

Yes, it could also be that -- the ports aren't terribly unusual though. The matchmaker cycles between ports 80 and 8081 each version update. (I'm sure 80 isn't blocked as that's web default)

IP address is 40.121.22.148 or matchmaker.magequit.com

I'm curious what you get if you visit that address in your browser. I receive ERR_EMPTY_RESPONSE which is what the matchmaker is programmed to return when sent an unrecognized request (in this case a standard GET). I imagine your browser will not be able to resolve the address if it is indeed an issue with your ISP. If it is a DNS resolution issue, than you'd receive a different response for visiting the IP address vs the named address, but I doubt this is the case.

Who is your internet service provider if you don't mind me asking?

Hope this helps.

Brett

Hey!

We've only seen this happen a handful of times, and what we've narrowed it down to is either parental controls that block our matchmaker's IP (you would know if you had this), or, what's more likely, is that your internet service provider is unable to properly make a connection to our matchmaker. I believe this has only been an issue with Comcast/Xfinity, and it's very rare. You can attempt to hotspot your phone and connect to see if the matchmaker is available that way (I don't recommend playing like that, it would just be to verify that it has something to do with your ISP). How this has been fixed in the past is EVENTUALLY the ISP fixes its issue and it ends up working. It's a mystery to me how or why this happens, and how it miraculously fixes itself.

It probably won't help, but this guy had the same issue as you are describing: ... Read more

Just sent you a friend request, I will message you some info :)

You are welcome :) thanks for playing!

Brett

Hi Fustador!

I imagine that this is the same limitation that we have with the Steam Link only supporting 4 controllers since it relies on xinput to stream controller input and xinput has a 4 controller limit.
As far as I know, this is a limitation of Steam's input streaming service.

However, we haven't updated our controller library (Rewired) in several months and it's POSSIBLE that they've implemented some sort of workaround. That's something I've been meaning to test, so this gives me another reason to do so.

In the meantime, you can still play 5-10 players with Online mode (unfortunately this would require each player to have their own copy). You could also try getting weird with a hybrid approach. Have 2 copies of the game with remote play together, go to Online and have up to 3 additional players join each copy by pressing A. Your lobby would look like accountA, [1]accountA, [2]accountA, [3]accountA, accountB, [1]accountB, [2]accountB, [3]accou... Read more