Multiverse and Debugging

Sun Feb 17, 2013 5:43 pm

Hi!
I've seen a few people having issues and unable to resolve the connection to the Multiverse. Perhaps in future versions we could have a "network test"?

Perhaps something like:

Network connectivity test and ip address(es) correct - e.g. if we have a 169 address or such. - contact router
Quick Ping to multiverse hexark
Attempt basic HTTP test on multiverse
Attempt to do basic communication between Transcendence <---> Multiverse
Attempt Authentication
Send all data

And perhaps dump the debugging output to Transcendence Debug console and or a text file?

just a thought.

Tue Feb 19, 2013 5:43 pm

I agree, that makes sense.

I suspect that the major problems are:

1. Firewalls/etc: I need to figure out what triggers a firewall to block an outbound HTTP request. Is it something about the process? Is it the destination URL (not common enough?) Or is it something in the HTTP headers (or content) that is screwing things up?

2. Proxies: One possibility is that Transcendence/Multiverse is not handling proxies correctly. If you're playing Transcendence at work or if a firewall has a proxy, perhaps there are problems.

As you said, logs of the traffic would help.