Looks like we are in for a little bit of maintenance in the near future to fix something with the Kupofried ongoing event. SE did a bit of maintenance last week to fix the issue with mobs moving too quickly when they were in a fully rested state. Insert jokes about spaghetti code here. This might bring back the considerations I brought up in my late post about whether SE should or should not take down the servers in the case of a minor but important repair that might need to be done.
As much as I don't have a problem with it, the issue of King's is relevant for those that do camp them. It is important that the times of King's rotate through the day so that all time zones get a chance to claim the different King's. This actually can take quite a bit of time depending on when they previously spawned, so it is important to keep the servers up for extended periods of time. It may also raise the question of why there are still mobs that require this situation to exist, and that it is far past the time to consider doing away with 21-24 (or longer) spawns.
A site note: This is the beginning of the new format style even if the new format has not yet changed. Mr. QQ will be the column for information on technical issues, server issues and other minor SE issues.
Monday, May 18, 2009
Mr. QQ says "Emergency Maintenance for Kupofried? Oh Noes!"
Posted by
Ringthree
at
11:15 AM
Labels:
Events,
Mr. QQ Says,
Ringthree
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment