Support:Myst Online: Uru Live
From MYSTlore
Important: This is a technical support article for a computer game in the Myst universe. Before reading, please understand that support is provided on a user-to-user basis, and unofficial. While we try our best to help (and prevent harm), we cannot be held responsible for any damages the given advice may cause.
For official support, please refer to these pages: Cyan Customer Support, Ubisoft Support Center, Uru Live Support Site.
This article refers to the Cyan-developed, GameTap-published Myst Online: Uru Live only. It does not specifically cover any other versions of Uru, such as Uru: Ages Beyond Myst, Myst Uru: Complete Chronicles or Untìl Uru. Nonetheless, due to similarities, some of the advice given here may apply to those other versions.
Contents |
[edit] Networking
MO:UL requires that you have a working, active Internet connection throughout the entirety of having it running. If you try and launch it while the Internet connection is unavailable or malfunctioning, you will receive an error message and be denied login. Likewise, if you're already playing and your Internet connection becomes unavailable or malfunctions, you will receive an error message and be forced to quit the application.
[edit] Hosts and Ports
If there is a router, packet filter, firewall or similar between your computer and the Internet, you may have to specifically set the device up as follows:
- The outgoing TCP port 14617 needs to be opened to the following hostnames: beta-auth.urulive.com, beta-file.urulive.com, and uruapp-cw01.ibs.aol.com through uruapp-cw21.ibs.aol.com (where the two digits after cw increment for 21 separate hosts).
- No UDP port needs to be opened.
- No incoming port needs to be opened.
[edit] Bandwidth
Your downstream bandwidth (the speed for packages that travel from the Internet to you, i.e. "incoming" ones) should be no lower than 384 kbit/s. This is particularly relevant when downloading new content. A faster downstream bandwidth can dramatically lower the download times. People below the above threshold frequently find the client stuck with a "0 seconds remaining" message after the very first loading screen, and unable to proceed. Whether this is a deliberate timeout on the server's end or a bug (and whether it will be remedied eventually) is thus far unknown.
Your upstream bandwidth (the speed for packages that travel from you to the Internet, i.e. "outgoing" ones) should be no lower than 128 kbit/s. This is particularly relevant for broadcasting your voice in voice chat. You can lower your requirements by not using voice chat.
[edit] Latency
The lower the latency, the better.
A latency around 200 ms to the aforementioned hostnames is acceptable. A latency above 300 ms can cause minor annoyances, and a latency above 400 ms is critical. You can use the ping command in your operating system to test the latency. Note that it can vary greatly, and that turning other applications off that might use your Internet connection (especially applications such as file sharing, voice chat, video chat or other online games) can greatly improve latency. For example, in Windows, do this:
- Click Start, then Run…
- In the dialog that comes up, type cmd and hit OK.
- A black window (a DOS/NT command shell) should open. Type in: ping beta-auth.urulive.com.
- Lines looking similar to these should appear:
Answer from 64.236.117.68: bytes=32 time=146 ms TTL=111 Answer from 64.236.117.68: bytes=32 time=145 ms TTL=111 Answer from 64.236.117.68: bytes=32 time=146 ms TTL=111 Answer from 64.236.117.68: bytes=32 time=146 ms TTL=111 (...) Minimum = 145ms, Maximum = 146ms, Average = 145ms
The values such as 146 ms is what we're interested in. More importantly, in the very last line, you should get an average value.

