SDream Profile Blog Joined November 2010 Brazil 896 Posts Last Edited: 2012-08-01 13:00:11 #1



Chris Sigaty wrote this in a SC2 blog recently: In our last blog post, we outlined several upcoming online features we’re working on, including clans and groups, global play, resume from replay, multiplayer replay viewing, unranked matchmaking, and language packs. Since then, we've seen some speculation on whether the features would be exclusive to Heart of the Swarm or available to Wings of Liberty players. We want to clarify that all of these features will be available to BOTH Wings of Liberty and Heart of the Swarm owners. You will not be required to purchase Heart of the Swarm to get the benefits of these features.



Therefore, he aknowledged that WoL will have language packs in the future as a feature.



I question though, why not today?



This isn't a random question in any way. Today the patch 1.5 went live (on NA region at least) and at the same time several bugs came along, but I'd like to point you into a special one. Check this thread



This bug and the way we can fix it just tell us that it is possible to easily switch the language we wanted so fast with this new stream technology, it is there, it's just waiting for Blizzard to allow us to use it. (if you try using a language that is not "allowed" for you, you will get a error requiring you to change your language...).



Right now we can actually use this bug to have all the sounds in the language we want.



At variables.txt we have these 2 lines:



localeidassets=xxXX

localeiddata=xxXX



localeiddata changes both your writing language (every text) AND it also changes your gateway (NA, LA, KR, EU etc). That means that if you have a LA key, you can't change it to enUS, because that is a NA key. It is not allowed. However, you can change the localeidassets to any language and there won't be a problem (at least for me it's running well so far).



For example, you have a LA key that can only use spanish and portuguese languages, but you can bypass their system and have the entire campaign and multiplayer sounds in English with this:



localeidassets=enUS

localeiddata=ptBR



Now you have your game in brazilian portuguese, however, your sounds are in English. In the campaign you have subtitles! It's a feature so many players asked since realize, now possible thanks to a bug. This bug might get fixed any time unfortunetelly.



The thing is, what is Blizzard holding this feature for? We could have it today, right now, why not?



Well, at least enjoy your half relocalizator for now



Edit: Official information about the bug and how to fix it:

http://eu.battle.net/support/en/article/starcraft-ii-language-issues



Has anyone tested it with korean (koKR) yet? If that one works I guess every language will work, which means you can play with English sounds in the korean server as well, though I guess people is more worried about the texts and not the sounds =/ Therefore, he aknowledged that WoL will have language packs in the future as a feature.I question though, why not today?This isn't a random question in any way. Today the patch 1.5 went live (on NA region at least) and at the same time several bugs came along, but I'd like to point you into a special one. Check this thread here This bug and the way we can fix it just tell us that it is possible to easily switch the language we wanted so fast with this new stream technology, it is there, it's just waiting for Blizzard to allow us to use it. (if you try using a language that is not "allowed" for you, you will get a error requiring you to change your language...).Right now we can actually use this bug to have all the sounds in the language we want.At variables.txt we have these 2 lines:localeidassets=xxXXlocaleiddata=xxXXlocaleiddata changes both your writing language (every text) AND it also changes your gateway (NA, LA, KR, EU etc). That means that if you have a LA key, you can't change it to enUS, because that is a NA key. It is not allowed. However, you can change the localeidassets to any language and there won't be a problem (at least for me it's running well so far).For example, you have a LA key that can only use spanish and portuguese languages, but you can bypass their system and have the entire campaign and multiplayer sounds in English with this:localeidassets=enUSlocaleiddata=ptBRNow you have your game in brazilian portuguese, however, your sounds are in English. In the campaign you have subtitles! It's a feature so many players asked since realize, now possible thanks to a bug. This bug might get fixed any time unfortunetelly.The thing is, what is Blizzard holding this feature for? We could have it today, right now, why not?Well, at least enjoy your half relocalizator for nowEdit: Official information about the bug and how to fix it:Has anyone tested it with korean (koKR) yet? If that one works I guess every language will work, which means you can play with English sounds in the korean server as well, though I guess people is more worried about the texts and not the sounds =/