|
On March 25 2011 04:58 Kishuu wrote:I can understand why girlscout left us in oblivion. No one reads his fucking thread. Goddamn this is so annoying.
Agreed. It doesn't take much common sense to open thread and go to the last page posted to read about most recent activity.
|
Well finally finished downloading the EU client! No need for this anymore! so long suckers!! j/k
|
Is that day finally here? Am I actually forced to now play this game in its horrible Spanish translation just to play on the LA server?
Fuck this, I'm buying Shogun 2. At least Creative Assembly doesn't lock people into retarded zones and then forces translations on them.
|
Lucky for me I have a Us account, my LA account will be dead until I can play it with an english client.
|
Oh please PLEASE don't let this program develop die. I'm willing to pay out money! Not only do I not want to play SC2 in Spanish, I'm not even sure I could! And I don't even have the bandwidth to download that 8+GB's again.
Please tell me there is hope! I'm also a programmer and I'm willing to help out with development. I just have NO FREAKING idea how Girlscout Cookie even figured out how to do this, I thought he worked for Blizzard. LOL.
|
On March 25 2011 08:18 tbcarver wrote: Please tell me there is hope! I'm also a programmer and I'm willing to help out with development. I just have NO FREAKING idea how Girlscout Cookie even figured out how to do this, I thought he worked for Blizzard. LOL.
Fire up notepad (or wordpad or whatever you use). Open the relocalize.bat with said editor. Now you see 100% every step he did. He basically opens the Blizz MPQ files and moves stuff around / renames them. Dont know what exactly he does in those steps, since I dont have any shell scripting knowledge.
|
On March 25 2011 08:38 Zocat wrote:Show nested quote +On March 25 2011 08:18 tbcarver wrote: Please tell me there is hope! I'm also a programmer and I'm willing to help out with development. I just have NO FREAKING idea how Girlscout Cookie even figured out how to do this, I thought he worked for Blizzard. LOL. Fire up notepad (or wordpad or whatever you use). Open the relocalize.bat with said editor. Now you see 100% every step he did. He basically opens the Blizz MPQ files and moves stuff around / renames them. Dont know what exactly he does in those steps, since I dont have any shell scripting knowledge.
LOL cute Even if you had scripting knowledge you wouldn't know what he's doing because this is all related to blizzards install and localization, which he has inside info about. The easy part is knowing how to write script, the hard part is knowing what the hell to do with that skill. Its not about what step he did its about why he did that step.
|
95% done downloading the enUS client...and it has come down to a halt. FU blizzard downloader =(
|
Belgium9937 Posts
Guys, lets figure out how to undo the changes the GSCRelocalizer makes.
I myself have the EU client, and used the program to relocalize to NA.
I have a EU client now, and removing all the enUS files has made the updating fail at 98% instead of the earlier 85% or whatever it was. There's probably one more file somewhere that needs to be deleted or modified, if we can figure that one out, we can at least play on our original servers without having to wait for GirlScoutCookie to return.
There's people that already mentioned getting it back to work after deleting all the files from the relocalized locale from their Program FIles/Starcraft II/ subfolders.
edit: included quote
On March 23 2011 02:39 pedrotrv wrote: You don't need to reinstall the whole game again. Relocalize the client back to the original location, and delete all files left of the relocalized language.
EG I play in LA server with the NA client. I play in the PT-br language. When I know there is a patch, I localize the client back to NA, then delete all the PT-br files (just search the directory for the files). No need to install the whole game again.
If you don't want to do this, just keep a backup game install in a external drive.
|
On March 25 2011 09:47 RaGe wrote: I have a EU client now, and removing all the enUS files has made the updating fail at 98% instead of the earlier 85% or whatever it was. There's probably one more file somewhere that needs to be deleted or modified, if we can figure that one out, we can at least play on our original servers without having to wait for GirlScoutCookie to return.
I'm confused are you saying you have the EU client installed and now you are going to just play on the EU servers instead of the NA servers with some different account, and therefore don't need to relocalize to NA and just want it back to the default EU?
If this is the case then I would ask, have you already patched to 1.3? If you patched already and now are trying to remove the relocalization I think its too late. I think you needed to remove the relocalization before you patched. Here is what worked for me 2 times, although I have tried this technique several times.
- before patching the client to the new version, relocalize back to the original source language. ie.I relocalized from a enUS install to esMX. Therefore, I relocalized it back from esMX to enUS - next delete any files from the install directory that have the localized name. ie. I deleted all the files that had the word esMX in the file name. - next let SC2 patch to the new version
This is where you could, theoretically play on your language's geographic area. And this is where I would normally try the new relocalizer for the new patch.
If this doesn't work, just delete the SC2 install folder and reinstall. I would have started there anyways if I had a version I could actually play.
Tyler
|
On March 25 2011 10:05 tbcarver wrote: - before patching the client to the new version, relocalize back to the original source language. ie.I relocalized from a enUS install to esMX. Therefore, I relocalized it back from esMX to enUS - next delete any files from the install directory that have the localized name. ie. I deleted all the files that had the word esMX in the file name. - next let SC2 patch to the new version
Afaik you dont have to relocalize it back. The "Switch between installed locales" should be enough (switch to the source language). I could patch my Korean client then (I also didnt delete any files). But I cannot test since I dont have a Korean account. (And after that testing the relocalizer with the 1.3version fucked up my install. And I currently only have 200kB/s since I'm not at home QQ).
So as tbcarver mentioned you need to do this before you try to patch a relocalized client / relocalize a 1.3 client (if you get a patch error it's probably too late). If not - a clean reinstall might be the only solution (it's definitely the best).
|
And god I hate myself, because that supid Korean Install took like 3hours to patch (had the idea earlier), but here's a solution:
- Clearn Korean 1.3 Install. - ..\StarCraft II Kr\Support\GSCRelocalizer-v0.11 (use the one from Girlscoutcookie in the op) - Open the relocalize.bat (wordpad, notepad, IDE) (Dont run it!) - Edit line 412 to: FOR %%V IN (15405 16561 16605 16755 16939 17326 18092) DO ( (Before it was (for those guys who dont have lines & need to do search) FOR %%V IN (15405 16561 16605 16755 16939 17326) DO (
Relocalize as before. Aka start the program, select 1 (Relocalize a locale), source koKR 134, target enGB 127.
Dont know if it works for other language versions, but afaik it should (and if it doesnt, wait for Girlscoutcookie)
|
I didn't want to wait so a downloaded LA full client and NA full client. xD Don't want more to depend on this Relocalizer.
|
I want to play this game in my native Korean.
I live in America, and have the American Client. To do all this makes me a bit miffed.
|
Downloaded the full game as well, was getting sick of having to reinstall the game when the patching somehow went ballistic.
Girlscoutcookie, I WILL NEVER FORGET YOU. Thanks for supporting me all the way through 1.2!
|
Sweden33719 Posts
Zocat, you just saved NaDa (and also me) a ton of work ~_~ Ty!
|
@Zocat Thanks so much for putting everything together like this.
I don't know jack shit about MPQ but that fix alone may probably fix the entire relocalizer program. I'll test some stuff out tomorrow. If it really does I will post here a repack. If it is not the only thing I'll spend some hours trying to fix it for everyone in the community. It's not like I lost faith in GSC but if this does the trick it will be awesome.
|
|
I was going to sleep but I got a LOT excited about this and I can confirm it works as well. I'll give some background on why I'm saying it works...
I got relocalizer 0.10 and ran a text check on the .bat comparing 0.10 to 0.11 ... turns out that only that same line was changed.
So I changed the line here with the address zotac provided and it worked just fine. I don't know how zotac got hold of that address but it really works.We got 3 good feedbacks from it in different locales. Mine is US to ptBR and it worked. I did a new zip for those computer illiterates that don't wanna mess with the files. I maybe over extended myself and called it .12 zotac / cute guy temp fix. [don't hate on me gsc .-. I love you <3] The instructions are the same from the older ones. Don't blame me if it doesn't work I just used this very same file and it worked. There you go:
[url blocked]
|
found the problem about the last 2% erroring, after you delete anything named enXX or w/e region you relocalized to, you also have to delete Battle.net.MPQ and Battle.net-patch.MPQ and replace them with the patch 1.3 clean ones. I dont know where to get clean ones though, and battle.net wont download them for me. Could anyone help out with that?
|
|
|
|