those are just the files used for unpacking the archive(s), the majority of the tools you need for data compression/decompression can be found here, under the "stickied" / "pinned" posts.

@Game Repacker
this is XTOOL THREAD :mad::mad::mad:
there is guide threads on the site how to compress games..

I know
 

I know that but usage?

Anyone noticed xtool and unreal.dll plugin are broken for Street Fighter V since xtool 0.3.9 + unrealplugin R3?
Don't know about other games, I own SF5 and did personal repack with 0.3.9 + unreal.dll R3, .pak files are decrypted normally.
Tried to use it on 0.3.21 + unreal.dll R5 -> nothing is decrypted at all

Btw, yes, I used -d1. Maybe I overlooked something, but if that's true can you please explain to me what am I doing wrong.

For sample I used small 20mb pakchunk50-WindowsNoEditor.pak

With xtool.exe 0.3.9 + unreal.dll R3 - WORKING, decrypted, inflated
With xtool.exe 0.3.21 + unreal.dll R5 - NOT WORKING, nothing is decrypted (m1 is not needed in latest unreal.dll version)
Used -mxtool+srep:m2f:l512+lolz arc.exe pack command on both.

If you have specific questions then ask them. Otherwise, I quote from the first post of this thread: "Read the documentation to find out how it works and how to use it."

Does using the "LZ4" codec require a specific library version? I'm currently trying to pack the Sony "PlayStation 3" exclusive, "Demon's Souls" (which has LZ4 streams). Attempting to use xtool 2020 results in this output as soon as the temp file has been generated. Utilising xtool 2019 only inflates the input by ~1kb. I'm not able to find any prior examples of the codec being used so I'm not quite sure whats going on.

Has anyone encountered this error before? I've had it happen with a handful of game-data files, curiously I was able to pack this title ("DOOM", the 2016 reboot of the series) previously, when using the default scanning range (I think 16mb), but I'm redoing it since some files failed to decompress properly.

maybe it's an issue with the -t100p-1? :confused:

Here's the documentation. It took weeks to write this as I'm very busy.

I'm still unavailable for two more months but the documentation should give insights as to how to fully utilize xtool and how to create plugins.

Thank you very much @Razor12911 👍

@Razor12911
Thanks for the documentation. Brought me a few steps further (I didn't even know that xtool has mermaid/leviathan support until I read your documentation lol).
But what I don't understand right now is what to do if there is no signature (or repeating pattern) before an oodle header or if the pattern is different before many headers.

Currently I'm dealing with mermaid (8C 0A) and there is no visible pattern before the header, just always different random bytes.

---

In a different test I was looking for kraken header (8C 06). There seems to be a repeating pattern, namely 6 bytes (00 00 00 00 01 00) + 1 or 2 random byte. The 9th byte is always X (58).

https://i.imgur.com/qEKZ9IK.png

Maybe I have to work with Conditions, but unfortunatelly you forgot to explain them somehow in the documentation :D

LZMA Codec for TTW2. It possible?)

Attachment 30469

:(

yes, read documentation and make plugin :rolleyes:

@Razor12911
Sorry, I already found it (I just forgot to edit my post) and I made some steps forward (on my sample I made +3% ratio compared to xtool without configutation, I will see if there are more) :)

Update available

Changes

- updated search support (speed improvements)
- updated command line parser
- added partial universal scanner for lzo1x streams
- added universal scanner for lz4f streams
- fixed issue with configuration files failing to execute without conditions

Notes

The previous update is still up, in case if there are issues with this one as I'm rusty af at the moment. (I haven't coded in months)
The lzo1x codec uses LZO1X-999 (level 1-9) and should only be used if you have no alternatives for precompression such as no plugins as this thing can be slow at times.