emergency world maintenace already...........

[Malacite]

YAY Second emergency maint, another 3 hours... 2 AM...

Yeah screw this, good night.

[Earwig]

They must have messed it up big time. What kind of coding errors would result in a 7 and a half hour maintenance?

[Ninurta2217]

It would also make sense that this could take a while to fix if it's some obscure logic error or something that someone made in an unrelated section of the code that found its way into 99,999 damage cures on undead mobs. It could be anything, and it's probably something really small like a + where a - should be or an 'OR' where and 'AND' should be.

If that were the case, a rollback would be more logical would it not? Rollback -> reupdate at a later time-> ??? -> profit.

[Selzak]

If that were the case, a rollback would be more logical would it not? Rollback -> reupdate at a later time-> ??? -> profit.

I suppose, but I'd like to think that they've found the bug by now. Probably just realized that they opened a lot of other potential problems when they sat down and took a look at it. Honestly I can't imagine what would take this long, but eh I doubt they're just trying to keep us from playing.

[Atomic_Skull]

If I had to guess why it's taking so long I'd say it's probably because of spaghetti code.

[wildsprite]

it would really be better if they implement the test server access for the players so this kinda thing doesn't happen, cause seriously, they waited till what? 2/3 days ago to tell us the update was happening on the 11th...., then after a 2 hour maintenance I get ready to play, me and friends are gathering and we get a 5.5 minute warning....seriously SE? c'mon this is silly and very disappointing

and on top of that it starts off as 4.5 hours...then at the last minute they change it to 7.5 hours? all I can say to this is
"Kitanashia sighs heavily at SE"

[geekgirl101]

Each time you add new bits of code to include new features it opens a new world of possible errors and conflicts. Sometimes it can go pretty bad, like there may be an old line of code somewhere that's hardcoding certain values and if that needs changing it can completely screw things up on a major scale. If the development crew has been shrunk down and certain people responsible for certain lines of code have moved on then it can be very hard to track down any conflicts in the code and work out a solution for it. Writing code is not as easy as you think, not every developer writes code the same way as each other so a different person having to work with someone elses' code to make his work may look at it and go "huh?!!!!" And if the other guy is not available then expect setbacks which could take days, weeks, or even months to fix while having to use "quick" workarounds which are not nearly as efficient and could cause future bugs and even more problems as more code gets added at a later date.

[Madine]

Each time you add new bits of code to include new features it opens a new world of possible errors and conflicts. Sometimes it can go pretty bad, like there may be an old line of code somewhere that's hardcoding certain values and if that needs changing it can completely screw things up on a major scale. If the development crew has been shrunk down and certain people responsible for certain lines of code have moved on then it can be very hard to track down any conflicts in the code and work out a solution for it. Writing code is not as easy as you think, not every developer writes code the same way as each other so a different person having to work with someone elses' code to make his work may look at it and go "huh?!!!!" And if the other guy is not available then expect setbacks which could take days, weeks, or even months to fix while having to use "quick" workarounds which are not nearly as efficient and could cause future bugs and even more problems as more code gets added at a later date.

Pretty much this. There's a reason software engineers jest about adding two bugs for every bug they remove. That reason is *not* incompetence.

[wildsprite]

I agree, but if it is that big of a problem I agree with what someone else in this thread said why not rollback to before the update then fix the problem and give us the update in a few days or something like that

[Neisan_Quetz]

Does sounds like a communication/Previous person did not leave proper notes issue.