UOGamers Community

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

  • To obtain new Razor updates, please reinstall Razor from our new website.

UO Gamers, we invite you to smash all records.

Status
Not open for further replies.
I think that was the point... they log what happens and then find where the code failed. That way they can fix it and try again. When the code can handle more clients than OSI can, Ryan and the other coders try and sell it to OSI. ;-)
 

Tiens-hybrid

Wanderer
ONE MORE TRY WE DOING THIS DAMNIT, RYAN YOU GET THIS SHARD UP AND WE WILL BEAT THIS RECORD FOR YOU, EVERYONE LETS DO OUR DAMNED BESt...sorry bout the caps, just wanted to make sure it was... well explicit
 

KingAl037

Sorceror
wow that was a different type of lag that time before it crash..it wasnt the usual stuck for 20 secs move for 5 secs..it was like move as much as you want..just rly rly slooooooooooow
 
R

Ryan

Guest
Well the official verdict is as follows:

2031 at time of CRASH (second downtime).

The first downtime was a server restart :)
 

Tiens-hybrid

Wanderer
Its called REALITY! :p No this is called lag divided by players, the other type of lag 20 seconds 5 seconds lag is just crappy connex lag
 
Status
Not open for further replies.
Top