Plz make a huge update all weeks w8 to change a lot of thing cuz we are figure all days rebooting and cant play a full gate lvl...
if u have a testing server plz make ur little updates there... we cant play with all time rebooting. i will stop playing cuz of that.
all days rebooting is not good -.-
Thu, 11/03/2011 - 05:07
Thu, 11/03/2011 - 09:47
#2
Server reboots are a trivial
Server reboots are a trivial inconvenience for players that are undertaken to improve overall service. Suck it up.
Thu, 11/03/2011 - 14:29
#3
Server reboots are a trivial
Server reboots are a trivial inconvenience for players
For those that have schedules that conflict with the reboot time, it is far from being trivial. Kicking all players out of the game is also bad for player retention, since many players don't come back after the reboot.
That said, fixing the problems with the server software so that they don't need to be rebooted so often can often be a very hard problem, so I'm not surprised that the bugs haven't been fixed yet. OOO used to reboot the servers only a few times per week, but rebooting daily fixed some of the lag problems people were having. I suspect OOO will always be rebooting at least one every week or two, even if they worked very hard on it.
Fri, 11/04/2011 - 03:02
#4
Idk a game that reboot a lot
Idk a game that reboot a lot like spiral knights. I think that is the 1rst thing that need to be fixed or improve.
Fri, 11/04/2011 - 03:19
#5
I'm fairly certain that the
I'm fairly certain that the reboot takes all of five minutes. With that in mind, you should plan around that instead of trying to power through gates before a reboot. As it stands, it's two hours before they have a scheduled reboot. Instead of complaining about an inconsequential issue (I really consider it the lesser of two evils, with the other side of the scale being the lack of maintenance, and all the natural goodies that come with that implication), you could perhaps spend this time trying to clear the gate that you would otherwise be unable to finish?
Just my two cents, take it for what it's worth.
Fri, 11/04/2011 - 17:14
#6
this is a serious problem not
this is a serious problem not a bad complain. if spiral want to be a great game with a lot of ppl online they need to make something bout that.
almost all server and client files is on our computer (i know that works in server side) maybe we have a lot of files on client side.
OOO can maybe splint the server like they do on language choice and make the update moment on diferent server sides on diferent moments... remember that u have ppl playing arround the world.
Sat, 11/05/2011 - 11:08
#7
OOO could also have multiple
OOO could also have multiple servers and add a reboot flag to a server that disallows for new connects.
When someone logs in, returns to Haven, moves from one area of Haven to another or changes Instance and the server has the flag, that person would be directed to a server without that flag.
After a long timeout and some messages people who just idle in the same area would be auto relocated to the next unflagged server.
The server would then wait until the last player left, automatically reboot and clear that flag.
When it come up again, the next server would be flagged.
That way OOO can reboot servers and nobody would ever know.
It's just, that this cannot be done with all updates, because, like I mentioned before, I understand that an update may require all servers to be shut down at the same time, because when servers of different versions communicate with each other or access the same database and one version expects the protocol or data structures to be different, this could cause lots of trouble.
Sat, 11/05/2011 - 11:46
#8
Your suggestion Desouler
Would require a seriously large number of servers. And if OOO spend their money on doing that, then it's going to take longer to for them to set-up servers in other countries. Nevertheless, the servers are going to be rebooted whether you want them to or not. It is needed. If your gaming sessions conflict with the reboots, then just try playing at another time. No need for OOO to do such a massive change just because of a sinlge player.
Sat, 11/05/2011 - 13:55
#9
@Ghret: Why do you assume OOO
@Ghret: Why do you assume OOO hasn't already a large enough number of servers?
Actually, OOO could combine that with setting up servers in different countries: During a reboot, a server in Canada could also get users from the USA, for example. So the USA can reboot first and after that users from Canada are slowly relocated to a server in the USA. So the server in Canada can be rebooted, too, and so it can be done with the entire world. Muahahaha.
Don't panic.
Mon, 11/07/2011 - 03:33
#10
Daily Reboot is at 8am
Daily Reboot is at 7am eastern, 4am pacific. If you live outside those time zones you will have to look up the time for your zone because honestly I don't know it and am not doing the homework to find it out. The answer is simple, find out the time for the server reboot for your time zone and not be doing anything in game at that time.
No matter what time they do it they will be interfering with some players' game play, so from the looks of it they opted for the start of their home office's day.
~Gwen
[edit] Had the times wrong, originally had 8am and 5am, its 7am and 4am.
Sat, 11/05/2011 - 22:35
#11
@Gwen Given they're in SF, I
@Gwen Given they're in SF, I kind of doubt their office day begins at 5am. And, given they're in SF, I also doubt their office day begins at 8am either. ;)
@Desouler Doing a rolling reboot is theoretically possible, but brings up some issues of its own. The SK game world, while heavily instanced, is not fragmented.
Suppose, for example, that your friend is in the clockworks during a rolling reboot. He's having some trouble and wants to invite you down to help him, but you're offline so he sends you an IM outside of the game asking you to connect and join. You connect, but now you're in the post-reboot fragment while your friend is in the pre-reboot fragment.
It's also something that's a lot easier to implement from the start rather than trying to patch it back into the game afterwards. I think the dev time would be better spent reducing the requirement for reboots and implementing new features.
Theres a daily reboot, AFAIK, independently of game updates.
There are different reasons for reboots: Some software can't run for a long time without using up more and more resources. This may be a result of faulty garbage collections or other bad code. Sometimes people running a server can't influence this much, because of some decision that forces them use a 3rd party software, which has these problems. For example an OS that crashes when run too long. Sometimes it's a security decision (e.g. OS patches require the OS to restart for loading a new kernel; forcefully disconnect everyone to prevent crackers form having a stable connection over a long period of time; etc.). ... and I think these reasons legitimate reboots to some degree.
Since the daily reboot occurs at a fixed time of day, I think it's just bad luck for you to experience it so often. Maybe it helps, if you play at a different time. The extra reboots for some updates don't seem to launch at a fixed time of day, tho.
Maybe it would also help, if OOO had different servers, made them reboot at different times and the players could choose a server that reboots at a time they like best. However, I understand that an update may require all servers to be shut down at the same time, because when servers of different versions communicate with each other or access the same database and one version expects the protocol or data structures to be different, this could cause lots of trouble. It would mean extra work to make part of the stuff backwards compatible, but it would have to be backwards compatible just for a short time, anyways; so this is probably not worth the effort. Therefore asynchronous reboots of servers would probably just be good for non-update reboots.