Larian Studios Forums Divinity - Original Sin Divinity Original Sin - Mods Anyone figured out a way to edit .lsf-files, yet?

As per the title, really.

.lsf seems to be the new .lsb, I'll look into it when I have a lil bit more time.

Isn't that MainLSF.pak there to prevent people from modifying characters? I just renamed whole pak and game still worked fine.. not sure though about in long run. I wish there was animations for all models so you could use any of them as player character.

In the original anyway, it's still probably true for the EE, even NPC to NPC type have certain animations missing. For example not a single female NPC has the mining animation.

[quote=SniperHF][quote=Nii]I wish there was animations for all models so you could use any of them as player character. [/quote]

In the original anyway, it's still probably true for the EE, even NPC to NPC type have certain animations missing. For example not a single female NPC has the mining animation. [/quote]

Most annoying is that with models like Astartes or Female orc, you can't move or throw items, so it pretty much makes it hard to have those as main character when you have to do that stuff a lot.

I don't think so. If they wanted to prevent mods they'd have encrypted the .PAK files or removed the ability to override files in .PAK-s (by copying them to the Data folder).
I think data is just organized differently in the EE.

Yup. I actually tried to see if Moose's editor still worked, since it could read the raw of .lsb:s, but it couldn't read .lsf:s.



No idea, honestly, but more to the point, why would they even want that? Preventing people from mucking with the characters or even the game itself has to be one of the most counter-productive things you can do as a developer these days.

Update: Read and write support for .LSF files was added to the latest EE tools (beta, naturally)(https://dl.dropboxusercontent.com/u/32263228/dos/gr2/ExportTool.zip).

There is not editor UI yet, but you can edit almost everything if you export the .LSF into .LSX (XML) format, edit it with notepad or something, then reimport it and resave as .LSF.

Some observations:
The v13 package format and the LSF files seem to be "write-optimized", ie. they are structured in such a way that the writer will be able to continuously stream data without having to seek in the output stream or do costly offset recalculations which were needed for the v10 packages and .LSB. This was probably the main reason for creating these formats.
In the case of PAK, the headers were moved to the very end of the file (so they're effectively "footers").
LSF uses multiple separate streams that are written to simultaneously and are concatenated into one large compressed blob in the final pass.

Can I use this tool to modify the save file? By using this tool,I tried to extract the globals.lsf from the save file(.lsv),and converted globals.lsf to globals.lsb,and did some editing and resave it as globals.lsf and repacked it to .lsv,but it doesn't work.I also tried to convert globals.lsf to .lsx file,but I got errors while running the tool.
So what's wrong with my operations？please tell me.thanks :thankyou: .

[quote=Norbyte]Update: Read and write support for .LSF files was added to the latest EE tools (beta, naturally)(https://dl.dropboxusercontent.com/u/32263228/dos/gr2/ExportTool.zip).

There is not editor UI yet, but you can edit almost everything if you export the .LSF into .LSX (XML) format, edit it with notepad or something, then reimport it and resave as .LSF. [/quote]

Thanks for the great work Norbyte.
But I also encountered problem like StrStn.
When I extract MainLSF.pak and load some .LSF files under Mods\Main\Localization,
EE tools import it without problem but can't export to .LSX file.

Error dialog that popped up is below.
[img]http://i.imgur.com/aNLqhWK.png[/img]

Both issues should be (hopefully) fixed. Can you redownload and test please?

It's working!
Thank you Norbyte.