ZOS, maybe it's the situation when we, players, can claim for an event increase proportionate to the time the servers were on maintenance? Because as far as I'm concerned, these 8+ hours I couldnt log in to the game was exactly the time I can afford to spend for game today.
ZOS_GinaBruno wrote: »For anyone running into the connection timed out error, could you please post your UserID and if you're on NA or EU? Thanks.
DieAlteHexe wrote: »Got to admit, for simple database maintenance with no patch, this is unusually long. Based on original posting, servers were supposed to be back up sometime around 6 AM EDT. It is now after 9 AM EDT.
The amount of maintenance downtime recently is starting to get really annoying.
My hope is that as they were proceeding with the maint they either found something that was problematic in addition to whatever they originally were dealing with and are trying to get it sorted OR they are testing the bejabbers out of it to try to avoid further problems and major riots over the weekend.
Or, after the week so far, they all fell asleep.
A more possible situation is: they have introduced Summerset code server side and it caused what we "software techs" call a "regression bug".
This usually can lead to any sort of tiny to huge issue with the game. We "see" our client hanging / disconnecting but in reality it's the server having issues.
When this happens you must:
- Find the bug. Somtimes this is easy and smooth. Sometimes it's close to impossible.
- Estimate if you can fix it in an acceptable (Terms Of Service) time or not.
- If you can, then you just fix it (aka "hotfix").
- If you cannot, then you have to roll-back the code and - sometimes - the database changes you did. This is never easy. Some versioning tools (GIT) make it somewhat "human", when you cannot use it it's hell. You might have to restore from backup and then re-apply database new rows (aka, what items we players have obtained since then etc) by hand or with tools.
If this is the scenario, then the ESO developers started gradually implementing / injecting Summerset code into the servers. Somehow a severe and hidden regression bug surfaced. They tried "simple maintenance" at first, to see if this was just a database issue or something "more". Found out it's "more".
They tried to hotfix it the past day(s) and did not succeed.
As last resort (it's always painful, risky and time consuming) they decided the regression could not be found / fixed in a timely manner and have undone the Summerset server side changes.
If the "rewind" works well, we'll be able to play at "Dragon Bones quality" again, until they fix the bug and then will try re-introduce the (hopefully fixed) Summerset code again in a next maintenance.
ZOS_GinaBruno wrote: »For anyone running into the connection timed out error, could you please post your UserID and if you're on NA or EU? Thanks.
Edit: Also, please let us know if you're on Steam or not.
Update: It appears to be an issue when launching the game via Steam. Using the eso64.exe bypasses the issue.
Update: It appears to be an issue when launching the game via Steam. Using the eso64.exe bypasses the issue.
ZOS_GinaBruno wrote: »For anyone running into the connection timed out error, could you please post your UserID and if you're on NA or EU? Thanks.
Edit: Also, please let us know if you're on Steam or not.
ZOS_GinaBruno wrote: »Ok, thanks everyone. We're looking into it now - it appears to be affecting those on Steam only.
EU PC 2000+ CP professional mudballer and pie thrower"Sheggorath, you are the Skooma Cat, for what is crazier than a cat on skooma?" - Fadomai