ZOS_ChipHilseberg wrote: »Hey folks,
In the most recent patch we fixed an exploit that allowed addons to run arbitrary protected code. This exploit could have been used to create a lot of harm, so it was critical that we fix it as soon as possible. Unfortunately, there were some unofficial localization addons that were casualties of this fix as they were using the same exploit in a benign way. It was important to us that the hard work done on these addons was not lost, however, so we implemented a new method of doing unofficial localization at the same time that the exploit was fixed. When this new code is live, addon authors will be able to supply a file named <languageCode>_ingame.str (instead of the previous .lua version) and fill it with lines of the form [<stringCode>] = "<string>" to provide localization in a secure way. This new method is presently going through QA and will be made available as soon as we are confident in it. Sorry for the lack of messaging about this in the notes.
As an additional note, we now need to add the languages to the game as unofficial languages so they can be used with the secure system. Presently we have added Russian, Italian, Spanish, and Portuguese. Which other languages are there unofficial translations for so we can make sure they are available when this new code launches?
I agree with Savaş and want to add, that this is unfair toward all players, who don't know English or French or German languages. I have been working on RuESO (Russian unofficial localization) for more than 1,5 years. And now I'm very sad, that all my work was wiped out because of one small incremental patch. And I'm sad for all Spanish, Italian, Brazilian, Russian and Turkish players, who can't play ESOTU anymore.
Greetings.
I'm the community lead of Bethesda Türk in Turkey. I'm working on Turkish translation of The Elder Scrolls Online: Tamriel Unlimited as an Add-On for now. There are also other teams too. For now there are five languages (Spanish, Italian, Portuguese BR, Russian and Turkish) are in progress. Note this, we are all united for that. Chinese people want to begin too.
We are sure that doesn't violence any agreement because of this is working as an Add-On, like I said. And we will publish our works as one big project named "Unofficial Language Packs" in these days. Of course we want to become official in-game. But we are not done and this is not the time for this. I'm writing this because of last 2.2.5 update. Our works does not working now.
Our projects already can't work properly because of launcher's language. We were changing -SET Language.2 "en"- in UserSettings and play without launcher. This is another problem. But now it is not working too. We tried everything but there is no solution. We believe that you changed something on .exe file. Some of us worked for 1 or 2 years! Is that all these efforts are for nothing? I don't believe that ZOS don't want additional languages. I mean, why not? We want a hotfix for unofficial languages works fine and we need it. Could you do it at least?
Thank you in advance.
Savaş Coruh, Founder of BethesdaTurk.com
I am Leju, I'm the administrator and the translation programmer to PT-BR Immediately after the update tried several things so that nothing worked he does not respect the set Language, including also already sent a request to them, seriously it will be one hell of shot in their feet because many players bought the game after the translations!
I have been working for some time in translation and made me very depremido it was preparing to update the translation refers to the last Update and see that happen too discouraged to continue the project!
All what we need is just allow us to use other locales, don't lock it only for en, fr and de!
But now (after 2.2.5) client reject all other locales except oficial (en, fr and de), so we can't make client to load data for other languages.
Italian translator reporting for duty.
Actually I'm translating all alone the entire game and got pretty results for italian, 4% on the total made by one (actively working with only spare time from work and family) person.
I could talk hours about the love, passion and dedication of me and the other translators, but I'm a fan of KISS formula:
Please unlock other locales, we are not doing anything bad! It's all for the best (and more selling I'd say) of your game.
By the way I also translated ALL the patch notes by now in Italian ( http://www.esoitalia.it/category/patch/ )
UltimaJoe777 wrote: »
Since it is not frowned upon by Zenimax for PC Players to use add-ons
Are we really talking about addons here?
Sounds to me that whatever you guys are trying to do, it's breaking the terms of agreement.
Are we really talking about addons here?
Sounds to me that whatever you guys are trying to do, it's breaking the terms of agreement.
@Olivierko it need huge attention because it hurts alot of players here
and no, you wrong about breaking the terms of agreement
@UltimaJoe777 sorry but looks like you know nothingabout addons, and ecpecially about this case with translations
It can be done without any program. Just change locale string (in UserSettings.txt):Are we really talking about addons here?
Sounds to me that whatever you guys are trying to do, it's breaking the terms of agreement.
@Olivierko it need huge attention because it hurts alot of players here
and no, you wrong about breaking the terms of agreement
Please elaborate how the translations are added, considering that there is no native support within the API for modifying translations, I did just assume that you're running a program that alters files in runtime, which in turn is illegal.
SET Language.2 "ru" (for ex.)
Put addons file into Addons folder,
and start game from eso.exe - done!
If they knew they were doing this, why not a heads up to the communities of translators? Why nothing in the patch notes?
Why do we have to "whine" to get information on a problem that concerns thousands and thousands of people who probably bought the game thanks to those translations?
I think the "whining" is very well deserved here. And way more than that.
If it's just an "error" while validating settings though, why nothing to calm down people down like "whoops sorry we look into it".