|
Only working one available on the 'net.
http://ra1ndog.wordpress.com/2009/05/28/sfad-extractor/
Extract it
Acquire the necessary lib's
Build the lib
Edit the source for the test file to point to your data directory
Build the test file
Run it
Check the project files for where things need to go.
EDIT:
To save you a bit of time and effort...
The audio if perfectly fine and usable. Nothing special here though.
None of the xml files that are unencrypted are of any special interest.
All of the juicy xml files are encrypted, and no one has broken the encryption yet (those of us who have obtained the xml information have done so by exporting from memory via hooks)
The only unencrypted images are simple alpha maps (white on black background)
The rest of the images, a mixture of TGA and BMP files, appear to have some form of encryption or non-standard file setup, in that they all appear skewed and have mangled colors.
The DDS files are encrypted (I think anyway) since no tool can open them. Trust me, I ran the gauntlet trying to open them.
The game logic scripting uses a file type unknown to anyone, yet (and according to the hex editor, appears to use the same encryption as the rest of the encrypted files). Note about it though, there IS game logic scripting! Once someone figures out what to do with it, it may prove useful.
The java classes are all under the same encryption as the xml-files. Again, those who have obtained them hooked the client and exported them at load time. According to replikant over at 033, they are obfusicated even after being exported without encryption. They use identifiers like a, aa, aaa, aab, aac and so on.
Collision uses a custom file type, not the standard physx or bullet, and unreadable so far.
Area information is in the format a01.lvl, a02.lvl, all of it is either encrypted or custom file type, so no info can really be garnered from it.
Meshes, again, custom file type or encrypted. No plugin in blender, 3dsmax, or milkshape would open them.
Lastly, vegetation definitions (don't know why they have them separated from the others) use a custom file type or encryption... nothing would open them.
Anything I've listed as custom file type or encrypted doesn't have any standard header information when opened in a hex editor, so odds are, they really did write most of the engine themselves, in that very little can be opened in a useful manner via 3rd party apps.
If I can get it to be nice, going to attach the full file list.
Done...
It didn't let me put on a .7z (which was 460K) but did let me attach a .zip (which was 608K)
You do not have the required permissions to view the files attached to this post. |
Who is online