Larian Studios Forums Divinity - Original Sin Divinity Original Sin - Mods EE pak extractor

So. I have the same problem.

Well ...
What did you change in English.pak exactly?
How did you recompress the package? (What options did you use, was the input path the same as the output path during decompression?)
If you're sure that you did everything correctly, can you upload a copy of the broken .pak somewhere for inspection?

I edited the file is not English, so I do translation into another language. and I want to leave English as any other edits. But when unpacking any localization file when you start the game it switched to English only. If you replace the default file pak everything is working properly. But even if you edit a purely English localization, the game strangely does not accept the changes. It will display a standard text. WHERE IT TAKES?
Unpacking and packing files made in standard mode.
Here repacked file
I do not know whether I'm doing right or not. Just want to ask how to do it right?

You should repack the directory where you unpacked the original .PAK to; otherwise the relative paths inside the .PAK will be incorrect.

Let's take an example:
Extracting Russian.pak to C:\stuff\ will get you:
PAK Localization\Russian\Fonts\fonts.lsx --> Filesystem C:\stuff\Localization\Russian\Fonts\fonts.lsx
PAK Localization\Russian\russian.xml --> Filesystem C:\stuff\Localization\Russian\russian.xml
[etc.]

When you later repack C:\stuff, the prefix of the paths will be stripped, so you'll get:
Filesystem C:\stuff\Localization\Russian\Fonts\fonts.lsx -> PAK Localization\Russian\Fonts\fonts.lsx
Filesystem C:\stuff\Localization\Russian\russian.xml --> PAK Localization\Russian\russian.xml

... however, when you only repack a *subdirectory*, eg. C:\stuff\Localization\Russian, you get:
Filesystem C:\stuff\Localization\Russian\Fonts\fonts.lsx -> PAK Fonts\fonts.lsx
Filesystem C:\stuff\Localization\Russian\russian.xml --> PAK russian.xml

Notice how the relative paths in the PAK are different; the new package has "Fonts\fonts.lsx" instead of the correct "Localization\Russian\Fonts\fonts.lsx", this is why your package doesn't work.

Thank you for the explanation. Everything works.

Updated the extractor again.
Changelist for 1.1 -> 1.3:
- Add LSF write support
- Fix TranslatedString serialization for LSF
- Fix conversion of GR2 models that use 16-bit vertex indices
- Add support for v7, v9 and v10 package formats

Link?

The usual, https://s3.eu-central-1.amazonaws.com/nb-stor/dos/ExportTool-v1.7.2.zip

1000x Thanks Norbyte!! Working great, just did the movement speed increase mod :)

Awesome tool, been using it to change up some dialog options, but it looks like the LSX->LSF writing seems break when it encounters a <children> element in the LSX xml tree. Any <node> elements within the <children> tags are being added to the parent's DOM level, and breaks dialog completely :(

You can reproduce this with any of the LSF files in Mods\Main\Story\Keywords from within MainLSF.pak

The particular file I was tinkering with was JAH_Default.lsf, if it helps.

What I did was converted the file from LSF->LSX, LSX->LSF, and then LSF->LSX again, comparing the original LSX to the "processed" LSX.

Any way you could add support for the children tags so that it'll output properly?

LSX loading is now fixed in v1.3.1

Thanks again for all the work Norbyte

You ever, erm, find the time or need for some extra work..well..i don't suppose we'd mind if you brouth the save game editor up to date as well ^^

Nice, thanks Norbyte. That fixed it!

http://i.imgur.com/wzt04vL.png

Well I'll take a look at it, but no guarantees...

Norbyte, I'm using v1.3.1 and I had two questions.

1. Is there a way that the program can output a readable file? As in, line breaks? Example shown in the picture:

2. Is it possible to have a batch way to convert lsf files to lsx? I really want to get a look at changing some things but having to convert one file at a time when there are hundreds of them is unrealistic.

No matter the answer, thank you for your program and time!

MrWoof, You can use notepad++ with the XML tools plugin. (you need to add the plugin).
Just press CTRL+ALT+SHIFT B and it will show it with all of the line breaks.

OMG thank you!

Hey Norbyte, after today's patch (11/10) I'm unable to fully unpack Main.pak. A ways in, this message box appears: I'm guessing something on their end changed? Thanks for taking a look!

Both Main.pak and Materials.pak (the files patched yesterday) extract successfully for me.
Can you "Verify local files" on Steam to make sure that your Main.pak is OK?

Thanks, that seems to have worked. I probably screwed something up previously with it. Sorry about that! Thanks for the reply!