adrian

this is really impressive... would love to see you guys going ahead with great results.

I got into same thought, as I didnt see other file corruption in other threads... but, I have these files backed up, so no problem. and btw, did you take a look to see if it is possible to use this tutorial to get in a way to apply your own encryption to server.dat?

hi, guys. I've been offline for long time. I'm sorry to hear that you have been into problems to download the files. in fact, the files were damaged (maybe a problem with forum server that might corrupted the files). but, good news! I've re-uploaded the files, so you may now unzip without problems. let me know if the files are okay now.

this is where i want to get at. nice job, btw.

yes, next step further. currently working on 5967.

nevermind, i already found the socket creation addresses on the client. to update you guys, what i've got so far is that i could make the client ignore the flash error and "auto start" the login process... is like simulating the click on the "enter" button of the flash start. the problem now is that, when the auth server receives the connection, and sends the pcs packet, the client is crashing... so i'm trying to find a break point to debug and see where it actually breaks. i believe its because of the flash update, that shows the animation and stuffs... so if i could make the client bypass this animation update, i think the client will not break anymore and we can then keep the normal login flux... this being said, the last step is to introduce a custom login modal, window or whatever we can in the midst of client start and the "auto login" action. a custom login will be needed to set in the process memory the server chosen, the ip, and the account/pass data. putting this things in the right place, the client will find these values in the memory when running the login process and things will go on as before.. that's the plan...

guys, i suspect that the socket created for login server connection is created in login flash. do you know anything about this?

is not a copy paste, really... i got an idea to a start point. will see what i get and share with you guys.

that is how i do feel too. but "thinking out loud" now... what if we try to replicate what the new client does now?

maybe we should work on this together and search for a possibility to make a new login screen.

I'm glad you did it! this should work fine on 5517 client. thank you, @Mugaru.

I'm sure you can use these methods to make it work with any CO2 client, but I'm curious to see what you get.

I didn't have time to take a look on latest patch files. it's a bit confusing how TQ is handling these files encryption. but is it all that you want: "decrypt the ItemType.dat" ?

Would you be interested in share basic start steps into encryption reversering? I would like to try it soon by myself, but have no idea how to start... not the whole process, not every ".dat" file is decrypted into a temp file as "server.dat". for other files you just need to jump over the decryption and make sure the decrypted data is in the right place when the client will use it. there is a little hacky way to copy memory from address A to B in the memory if needed, I can tell you if you are interested.

thank you. :) the first time I was studying and trying to do this, i took almost one week to figure it out how it works and make things right. but this time, i took one afternoon to repeat and write all the process... also, I decide to leave it registered so myself could do it at any client in the future and not start from scratch again...