Well, I've worked my ass off past 3-4 days now working on this, and I've finally gotten it done. As you can probably imagine I went through total and utter hell doing this, and there was probably an easier way but if so I was blind to it. But below are the links to about all the .dds files in the C-Flyff Client.
I've kept them separated in folders depending on what .wdf I pulled them from. I know C-Flyff is supposed to have "much superior" textures compared to E-Flyff, although I'm not sure if EVERY texture is better or not, but you can look and compare for yourself.
But theres a downside too, I'll tell you right now. And you may be like "Omg Roach, you just gave us all the C-Flyff DDS files, HOW could there be a downside!!!". But alas, there is. It took me a long ass time just to get all this done as is, but none of the files have the proper name, it's still all "hexed" so to speak. I've just went through and determined which all of the files were .dds by hand and then corrected their extension. And also, even though these SHOULD still be directly interchangable with their E-flyff counterparts, I make no promises at all as I've not gotten to test any.
So what I recommend you do, is if there's a certain texture you want to switch out you need to go get the dds thumbnail viewer from Nvidia if you don't already have it, and just go through the folder and find your textures. Keep in mind, you'll probably need to change the texture in the Texture_Low, Texture_Mid, and Regular texture folder so you'll have to find all the textures for the model you want to try.. I'm planning on trying to get them all seperated myself sometime soon, but until then they are all together and mixed up ( 14,854 files just in the model.wdf archive).
I've seperated that particular folder into 3 seperate ones, b/c the dds thumbnail viewer seems to have trouble showing the thumbnails of much over 5,000 files per folder on my computer. So if you are viewing one of the folders, and you start seeing blank dds files, you may have to seperate some into another folder as i'm not sure if that's just the program limit or if it varies per computer.
I'm sure there's at least a couple of people who may have done this for themselves already, but even better if not. I just hope someone actually trys to make use of some of these haha.. But here are the links, I've got the dds files for the model.wdf, model.wd1, env.wdf, and ui.wdf files all in a seperate 7z archive.
http://www.mediafire.com/file/vjznnm...env.wdf_DDS.7z
http://www.mediafire.com/file/nx4ywx..._ui.wdf_DDS.7z
http://www.mediafire.com/file/4kmkzo...del.wd1_DDS.7z
http://www.mediafire.com/file/jl1nut...wdf_DDS.7z.001
http://www.mediafire.com/file/hzzzzi...wdf_DDS.7z.002 just for clarification,need all 3 of these to unzip it
http://www.mediafire.com/file/cwznx0...wdf_DDS.7z.003
I've also got all the dds files relating to the worlds figured out also, but no link for those yet as I'm still looking into the world files some atm, but if I release any info there I'll release the dds files for those then. And I BELIEVE I've determined exactly which files are the LND files also following what DeadlyData suggested in this thread http://forum.ragezone.com/f483/help-...-files-530814/
and compared some files to the E-flyff files. And also I've determined that there IS indeed 03d files in C-Flyff also, based on the fact I've found references to them in what I "believe" to be the .sfx files. But like DeadlyData also said in the above mentioned thread, the LND files (and maybe more, if not all the files) may indeed need some work done to them before they would/could function in the E-flyff client. But it's a step forward never-the-less in my opinion, and I haven't seen much, if any, progress from anyone else to this point so maybe this will help motivate others to work more on this project.
I've no programmer, and no reverser, and not even a graphic artist for that fact. But I've made a lot of progress still yet, and have some other information regarding the worlds if anyone cares to hear about it. It may not end up helping much if any even, but I'll still post my findings if anyone wants to know.
@DeadlyData In the above mentioned post, you said you believed it was probably encypted with XOR, so I read up a bit on it to see if I could learn anything. I read XOR encryption is done using a key file/key phrase, is that correct? And if so, that file/phrase would have to be in the client somewhere wouldn't it to be able to decrypt the files on the fly? Do correct me if I'm wrong though please. But if that's the case, if we could figure out what the key is (if there IS just one for the whole client anyway) then it shouldn't be a problem decrypting everything.
But I'm gonna go to sleep now, been up 4 days almost working on this and tired as fuck. Only break I took was my 4th of July smoke out lmao. Night Ragezone, and hope you enjoy!

