New Shadows over Reno?
-
So when Shadows over Reno's hosting shut down, there was talk of relaunching it elsewhere. Does anyone happen to have any info on what the status of that is, or where former players might be hanging out?
-
They managed to transfer everything. New site is
-
Awesome, thank you
-
Did they go down already?
-
@taika Not so far as I know.
(There's no updates wiki-side because my computer exploded, and I couldn't work on it until, well, this coming week, since the replacement finally arrived and is finally plugged in with a working keyboard.)
-
@taika Nah, in fact they just lifted their soft RP status recently and stuff is happening.
-
Hrm. The reno.kydance.net 2018 isn't working for me.
-
@taika said in New Shadows over Reno?:
Hrm. The reno.kydance.net 2018 isn't working for me.
Are you by chance using Mukluk?
I've been told it doesn't work and haven't yet gotten a chance to dig into it (I only recently dug out my ancient tablet that dies after 15 minutes or less of use...).
-
No, I'm on DuckClient. Which can be fickle, but usually due to resizing the window.
-
OK, so I had no issues on Mukluk via Xfinity wifi using default UTF-8 encoding on an Android tablet (that runs only 4.4.2).
I'm checking Duck client now.
Saying the quiet parts out loud since 1996.
-
@auspice said in New Shadows over Reno?:
OK, so I had no issues on Mukluk via Xfinity wifi using default UTF-8 encoding on an Android tablet (that runs only 4.4.2).
I'm checking Duck client now.
No issues with Duck Client either. @Taika what host are you on? Can you do a traceroute to kydance.net?
-
I'm on Xfinity. Let me try to run a traceroute.
-
Looks like it is dying 5 steps away from me.
-
@taika said in New Shadows over Reno?:
Looks like it is dying 5 steps away from me.
What's it dying on?
-
Hmm, according to the ad you put up, it might be dying on a bad Port number.
ETA: Used a different traceroute this time so I can show you.
Hop number: 1Connected to: stih8400la-mip.va.neustar.com ( 10.91.16.251 ) Roundtrip times: 0.106 ms
0.248 ms
0.245 ms
Hop number: 2Roundtrip times: Timed out. Hop number: 3Connected to: stihnrtr2-vlan4.va.neustar.com ( 209.173.53.230 ) Roundtrip times: 3.462 ms
4.305 ms
3.416 ms
Country: united statesHop number: 4Connected to: 5-1-29.ear3.Washington1.Level3.net ( 4.16.71.137 ) Roundtrip times: 4.362 ms
4.598 ms
4.331 ms
Country: united statesHop number: 5Roundtrip times: Timed out. Hop number: 6Connected to: ae36.cr2-was1.ip4.gtt.net ( 173.205.53.253 ) Roundtrip times: 5.643 ms
4.62 ms
5.228 ms
Country: united statesHop number: 7Connected to: et-2-1-0.cr4-dal3.ip4.gtt.net ( 89.149.143.57 ) Roundtrip times: 39.095 ms
37.562 ms
37.776 ms
Country: irelandHop number: 8Connected to: ip4.gtt.net ( 173.205.38.102 ) Roundtrip times: 37.804 ms
37.974 ms
37.958 ms
Country: germanyHop number: 9Connected to: 45.79.12.7 ( 45.79.12.7 ) Roundtrip times: 37.079 ms
36.623 ms
36.71 ms
Country: united statesHop number: 10Connected to: kydance.net ( 23.239.25.183 ) Roundtrip times: 36.294 ms
38.836 ms
38.674 ms
Country: united states
