FIX For EU Server Issue

Clarkieson

Pibbles wrote: »

*****BACKUP YOUR ESO FOLDER BEFORE YOU START WORKING ON THIS ISSUE*****
*****ESO FOLDER IS C:\Program Files (x86)\Zenimax Online\The Elder Scrolls Online\game\client*****

I'd welcome ZOS comments on the below fix.

I have fixed the EU server selection issue on my two PCs. The issue arises due to flaky code in the AppSettings.txt and Platforms.xml files. These files talk about DepotID 4000, which I have worked out is US, we EU-ers are DepotID4001.

Go to your client folder at C:\Program Files (x86)\Zenimax Online\The Elder Scrolls Online\game\client (by default) and backup he AppSettings.txt and Platforms.xml files before you do anything.

Then edit AppSettings.txt as per below:

SET DepotId "4001"
SET DepotEditable "2"
SET ChannelName "live"

Save this file.

Now edit Platforms.xml (I used Wordpad but you can use any text editor) as per below:

<?xml version='1.0' encoding='utf-8'?>
<platforms><platform><name>Live-EU</name><login_service_url>https://live-eu-services.elderscrollsonline.com</login_service_url><realm_service_url>https://live-eu-services.elderscrollsonline.com</realm_service_url><default>true</default><sleepy_giant>true</sleepy_giant><python_services>true</python_services><default_realm_id>4001</default_realm_id><use_login_queue>true</use_login_queue></platform></platforms&gt;

Save this file.

This should now always default to logging into DepotID 4001 - the EU server.

My appsettings.txt is located here:
https://1drv.ms/t/s!AhaoZsGtfKSPh_8VU_TfzE6JVW4jRQ

And my Platforms.xml is located here:
https://1drv.ms/t/s!AhaoZsGtfKSPh_8VU_TfzE6JVW4jRQ

*****IF YOU HAVE ANY ISSUES AFTER THESE CHANGES, RESTORE THE TWO EDITED FILES, OR THE ENTIRE ESO FOLDER*****

So when OT drops on console and is broken, do you think there will be a similar fix somehow?

raglau

Clarkieson wrote: »

Pibbles wrote: »

*****BACKUP YOUR ESO FOLDER BEFORE YOU START WORKING ON THIS ISSUE*****
*****ESO FOLDER IS C:\Program Files (x86)\Zenimax Online\The Elder Scrolls Online\game\client*****

I'd welcome ZOS comments on the below fix.

*****IF YOU HAVE ANY ISSUES AFTER THESE CHANGES, RESTORE THE TWO EDITED FILES, OR THE ENTIRE ESO FOLDER*****

So when OT drops on console and is broken, do you think there will be a similar fix somehow?

In my view, ZOS will have learned from this error and will ensure the correctly configured files land on the consoles. This is just as well, because you can't go in and edit them like this on consoles. Can you even select the server on consoles? I do have it on XB1, but have not played it on there in ages, so can't remember.

As an aside to everyone, just before the ZOS official patch for this issue is sent, I do think it's worth restoring the two backup files (usersettings.ini and platforms.xml) we take when implementing my fix. Whilst logically ZOS might simply send down two brand new and correct files, they could also send a delta down, which would inject the correct code into the existing files. My fix is just a quick and dirty thing I flung together when I got home from work yesterday and got fed up with the faffing about with the EU server problem, so it changes those two files from a known (albeit broken) baseline to something that does the job in a simple way. It is conceivable that the ZOS fix could fail to apply correctly to what is now an unknown baseline set of game files, depending how they deploy their fix. It all depends how their patch engine works, which I do not know.

ZOS will publish a date for their fix for this, I guess it'll get wrapped up in the next maintenence, so just before that downtime starts, we can replace our files with the original, defective versions that we backed up. If anyone forgot to back them up or lost them, I can supply the originals from my game set.

Ceram

Works perfect. Thank you for the fix!

Enodoc

Clarkieson wrote: »

So when OT drops on console and is broken, do you think there will be a similar fix somehow?

This won't be an issue on console, as console server selection is, and always has been, done from the client.

[Deleted User]

The user and all related content has been deleted.

Wolfshead

Night_Watch wrote: »

ZOS_DaryaK wrote: »

More importantly, however, it may break the code fix that we will be implementing.

Could you please look into the thread;

https://forums.elderscrollsonline.com/en/discussion/295594/eso-pc-mac-launcher-issues-update-12/p1

I like the fact the ZoS did know about this iusses and instead of fix before it went live then just let it be in honest is not better to fix the problem before you send out on live ZoS?

If did want to fix problem before it went live why not push out hotfix right way honest why is that we on EU have wait for answer on when this problem will be fix atm I feel ZoS is just like blizzard to ignore EU plyerbase when it come fix problem it feel like ZoS see just blizzard do that EU playerbase is 2nd class citizen and that well fix the problem when the feel like it that is so FUBAR

xeNNNNN

Legedric wrote: »

FriedEggSandwich wrote: »

Or, just before you enter your password select 'Live' and hit apply and then select 'Live-EU' and hit apply. This also works.

Yes it does but you have to repeat it everytime you start the client.

Which is easy to do.

Players shouldnt have to do that though tbh.

Juponen

xeNNNNN wrote: »

Legedric wrote: »

FriedEggSandwich wrote: »

Or, just before you enter your password select 'Live' and hit apply and then select 'Live-EU' and hit apply. This also works.

Yes it does but you have to repeat it everytime you start the client.

Which is easy to do.

Players shouldnt have to do that though tbh.

TBH this fix saves time and nerves and changing the one value and one word back before the next patch is a lot less pain than juggling with server selection every time you lauch the game.

Enodoc

Wolfshead wrote: »

Night_Watch wrote: »

ZOS_DaryaK wrote: »

More importantly, however, it may break the code fix that we will be implementing.

Could you please look into the thread;
https://forums.elderscrollsonline.com/en/discussion/295594/eso-pc-mac-launcher-issues-update-12/p1

I like the fact the ZoS did know about this iusses and instead of fix before it went live then just let it be in honest is not better to fix the problem before you send out on live ZoS?

Why are you assuming that ZOS knew in advance that this was going to be an issue?

SHADOW2KK

Enodoc wrote: »

Wolfshead wrote: »

Night_Watch wrote: »

ZOS_DaryaK wrote: »

More importantly, however, it may break the code fix that we will be implementing.

Could you please look into the thread;
https://forums.elderscrollsonline.com/en/discussion/295594/eso-pc-mac-launcher-issues-update-12/p1

I like the fact the ZoS did know about this iusses and instead of fix before it went live then just let it be in honest is not better to fix the problem before you send out on live ZoS?

Why are you assuming that ZOS knew in advance that this was going to be an issue?

Why are you assuming they did not?

Regardless of whether they knew or not, its still rubbish treatment of the EU playerbase, a simple test would have shown them, I personally think they rushed it out, thinking oh its ok, we will get raged at, but we will just keep them at bay till monday or whenever they are doing something they should have done within hours of One Tamriel release.

Make excuses for them all you want sir, think a lot of people will agree they pretend to listen to feedback and do the exact opposite on a number of issues.

Then the utter debacle of the EU side of things launch of a long awaited update.

Yes there are workarounds and quickly into the game, but the fact remains, we should not have too, its their job, not ours.

And to wrap it up, any other game developer would have it fixed within hours, not leaving a lot of people out to dry, bearing in mind, the vast majority of the playerbase dont even come to the forums, I have lost count of the amount of times I have seen guildies or general chat in zone talking about addons, cos as we all know the routing path for addons have been changed, some do not have tech skills, so they are left hanging.

End of the day, One Tamriel is good for me anyways, a lot I like, but the launch was a disaster for many.

And ZoS knew, I have no doubt

[Deleted User]

The user and all related content has been deleted.

elvenmad

Enodoc wrote: »

Wolfshead wrote: »

Night_Watch wrote: »

ZOS_DaryaK wrote: »

More importantly, however, it may break the code fix that we will be implementing.

Could you please look into the thread;
https://forums.elderscrollsonline.com/en/discussion/295594/eso-pc-mac-launcher-issues-update-12/p1

I like the fact the ZoS did know about this iusses and instead of fix before it went live then just let it be in honest is not better to fix the problem before you send out on live ZoS?

Why are you assuming that ZOS knew in advance that this was going to be an issue?

It was, it was posted pre patch as being amongst other poss issues that there was a issue with launcher that would be fixed in a later patch, but I am guessing they did not realised just how big an issue it was and as everybody as said they quite obviously did not test it.

No excuse here, it simply was not tested

Arnorien16

GrumpyMuffin wrote: »

Maybe pull a person or two off the unwanted Crown Crates team and get them working on a fix for this. Bit depressing they can launch a hated gambling system with a high level of polish, but they cannot make a simple region option work on the launcher.

Maybe shows where the priorities lay

So you want people who specialize in Arts and Design to do scripting and coding? (Unless of course you believe that they are still coding the system that was already coded) Next you might ask painters to do the plumbing and electrical work. The main problem with this case was that the change was not tested/resolved like they should have along with the PTR. Give actual working useful feedback instead of snarky idiocy.

SHADOW2KK wrote: »

Enodoc wrote: »

Wolfshead wrote: »

Night_Watch wrote: »

ZOS_DaryaK wrote: »

More importantly, however, it may break the code fix that we will be implementing.

Could you please look into the thread;
https://forums.elderscrollsonline.com/en/discussion/295594/eso-pc-mac-launcher-issues-update-12/p1

I like the fact the ZoS did know about this iusses and instead of fix before it went live then just let it be in honest is not better to fix the problem before you send out on live ZoS?

Why are you assuming that ZOS knew in advance that this was going to be an issue?

Why are you assuming they did not?

......

And ZoS knew, I have no doubt

Yes they knew it ofc. They simply like to be shouted and complained at like every other sane person. Not to mention it is the entire ZoS team's fault, even the guys who worked hard to actually script 1T ... it was not just the failure of the team who was behind the launcher changes.

[Deleted User]

The user and all related content has been deleted.

SHADOW2KK

Arnorien16 wrote: »

GrumpyMuffin wrote: »

Maybe pull a person or two off the unwanted Crown Crates team and get them working on a fix for this. Bit depressing they can launch a hated gambling system with a high level of polish, but they cannot make a simple region option work on the launcher.

Maybe shows where the priorities lay

So you want people who specialize in Arts and Design to do scripting and coding? (Unless of course you believe that they are still coding the system that was already coded) Next you might ask painters to do the plumbing and electrical work. The main problem with this case was that the change was not tested/resolved like they should have along with the PTR. Give actual working useful feedback instead of snarky idiocy.

SHADOW2KK wrote: »

Enodoc wrote: »

Wolfshead wrote: »

Night_Watch wrote: »

ZOS_DaryaK wrote: »

More importantly, however, it may break the code fix that we will be implementing.

Could you please look into the thread;
https://forums.elderscrollsonline.com/en/discussion/295594/eso-pc-mac-launcher-issues-update-12/p1

I like the fact the ZoS did know about this iusses and instead of fix before it went live then just let it be in honest is not better to fix the problem before you send out on live ZoS?

Why are you assuming that ZOS knew in advance that this was going to be an issue?

Why are you assuming they did not?

......

And ZoS knew, I have no doubt

Yes they knew it ofc. They simply like to be shouted and complained at like every other sane person. Not to mention it is the entire ZoS team's fault, even the guys who worked hard to actually script 1T ... it was not just the failure of the team who was behind the launcher changes.

Oh wow, I did not know there were many departments in a game developer, who are responsible of sub tasks to make a whole game.

Thank you so much sir, for your most enlightening piece of information.

I must apologise, if there is a next time that a department in the entity named ZoS do something ***, and they inevitably will.

I will most definitely be sure to name the exact department responsible, and tag you in the mentioned post to ask for your approval ok

Just pure sarcastic semantics from your end, the ones responsible work for ZoS, so their image take a hit because of the lazy actions of a department within their umbrella.

CranCat

Legedric wrote: »

Darlon wrote: »

Seriously ??? If it is this easy, why don't we have a hot fix from ZOS for this yet @ZOS_GinaBruno ?

Because their developers are in school this week, so they will work on a fix during the weekend to get it deployed on monday (when they are back in school again).

LOL hilarious

Zaldan

anyone wondering why ZO$ haven't fixed this is simply priorities, this isn't even on their to do list lol

Zaldan

ZOS_DaryaK wrote: »

While we really appreciate the efforts of players helping other players, we must advise that the potential workaround suggested above has a couple of issues. Firstly, it will permanently lock you out of the NA server. More importantly, however, it may break the code fix that we will be implementing.

yeah but that isn't going to happen anytime soon so why worry

P3ZZL3

For those that are not sure about the coding and are not sure about changing the config and XML files, there's another relatively simple work around.

• Load up launcher. Select LiveNA (Click EU, then back to NA).
• Type in the wrong password and click "play". This causes a request in to the US server - which is rejected.
• Change selection back to EU.
• Log in using correct password.

*shrugs*

elvenmad

The fix of @Pibbles does work 100%

But there is a patch maintenance tomorow so to be on the safe side I would advise changing the 2 codes back before the maintenance finishes'

IMO if fixed correctly they should patch in new folders to completely overwrite the old ones to guarantee its fixed, but who know's

JR_Returns

When you develop software there are always going to be bugs, because it will run on many different system configurations and because users try to do the weirdest things.

However you should always fix the embarrassingly bad stuff before you before it goes public and this problem falls into that category.

To me this is a very American problem. In America the project deadline reigns supreme and can't be changed, even if you'll end up with a crock of s**t by sticking to the deadline. I expect they just ran out of time to do everything.

Rosveen

P3ZZL3 wrote: »

For those that are not sure about the coding and are not sure about changing the config and XML files, there's another relatively simple work around.

• Load up launcher. Select LiveNA (Click EU, then back to NA).
• Type in the wrong password and click "play". This causes a request in to the US server - which is rejected.
• Change selection back to EU.
• Log in using correct password.

*shrugs*

I don't even need to do that. I open the client, switch to NA, back to EU and log in. Works every time.

raglau

JR_Returns wrote: »

However you should always fix the embarrassingly bad stuff before you before it goes public and this problem falls into that category.

Yes, to me this one smacks of them not testing against a dual server test environment. I own an IT consultancy and we do a lot of solution and technology architecture for the big global firms out there, the FTSE 100 clients who invariably make all their services globally resilient with multiple servers in multiple datacentres. And I always say to people that in such an environment where there are multiple servers, whilst we cannot represent that 100% accurately in pre-production due to cost constraints, we should always develop and test against at least two servers, because that way you will catch 99.9% of things. Whereas if you develop and test against one server, you can get tunnel vision and forget the sudden complexities that do arise when you have to factor in multiple servers and locations.

Looking at what ZOS did here, it seems to me they very likely did test their code against a single server, gave it a tick in the box in good faith, then of course they released that into the wild with a second server and had an 'oh ***' moment, when they they realised they had made a schoolboy error and broken things for what, 40% of the player base or thereabouts.

Tonnopesce

I suggest to close this thread because it can destroy the game for a lot of unexperienced people who will try this.
Use the workaround till tomorrow patch and let the devs do theyr job.

elvenmad

Tonnopesce wrote: »

I suggest to close this thread because it can destroy the game for a lot of unexperienced people who will try this.
Use the workaround till tomorrow patch and let the devs do theyr job.

Yeah, lets get the 'fix' patch asap, then I can edit all the files again hopefully for the last time to fix the next set of issues and get back to what I'm paying for, playing the game.

Tonnopesce

elvenmad wrote: »

Tonnopesce wrote: »

I suggest to close this thread because it can destroy the game for a lot of unexperienced people who will try this.
Use the workaround till tomorrow patch and let the devs do theyr job.

Yeah, lets get the 'fix' patch asap, then I can edit all the files again hopefully for the last time to fix the next set of issues and get back to what I'm paying for, playing the game.

You can edit your file, if I try probably my PC will blow up...

athanasios

Worked 100% !! Thank you for this !

raglau

Looks like ZOS are going to formally fix this issue today, taken from another thread:

"We'll be fixing the issue where changing realms isn't immediately taking effect, ultimately logging you into the wrong server and making it appear as though your characters have been deleted. We'll also be fixing the issue where your default server selection keeps getting reset to NA upon each log in."

While the servers are down might be the time to put the old, defective, platforms.xml and usersettings.ini back in place, so the patcher can work with the default baseline. I don't think it should matter, but you know how sensitive it is, pretty much anything triggers the dreaded 'repair' request.

Titansteele

I think the general message here is this should have been resolved within 24 hours of the issues being raised.

That is a reasonable (generous) expectation based on the customer impact this has and knowing just how much work this would take to resolve.
Come on ZOS, someone should have been making this crystal clear internally that this is a high priority fix.

Malmai

ZOS_DaryaK wrote: »

While we really appreciate the efforts of players helping other players, we must advise that the potential workaround suggested above has a couple of issues. Firstly, it will permanently lock you out of the NA server. More importantly, however, it may break the code fix that we will be implementing.

He is not helping other players he is helping you (zos), its annoying and not been fixed for a while now...