Older nostale Client

[krzysiu250699]

Hello, I've got a question about the nostale version\s:
If you open an older version of nostalex.dat when you try to log in it says:
Error: Client does not have the latest version (something like that)
Please downlod a new version of the client from the website.

Do any of you know how to bypass this message is it would be fun to play around with an older client version, as well as being able to use older cheats that no longer work.

Thank you in Advance

Regards 3roK

[Bombasticx3]

You cant use older cheats with older client, because the "cheats" are serversided and you can't downgrade the server.
When you have an old client just change the version number and delete the patcher.
Here in epvp are TUTs for changing version numbers of clients.

[JMII89]

I will explain you how to skip the version handler. The client version is handled via the analysis of the login packet.. For be more specific, i can redirect you to check the last part of it. It depends by username. I post the algorithm for be more clear:

md5(md5(nostalex.dat) + md5(nostale.dat) + LoginID)

There are two options for edit the packet at the fly..
- Editing the registers, you have to be able in reverse engineering.
- Using a broker, you have to be able in sockets programming.

The second option is definitely easier but as we say in my country, beautiful things are those that require more time.

As they already have mentioned, don't expect to restore long-standing bugs. Are serverside, the memory will doesn't solve your problem. Nothing will be able to do what you're dreaming..

Welcome in the real world, where fairies are nothing more than a figment of the imagination.

[ernilos]

Originally Posted by JMII89

I will explain you how to skip the version handler. The client version is handled via the analysis of the login packet.. For be more specific, i can redirect you to check the last part of it. It depends by username. I post the algorithm for be more clear:

md5(md5(nostalex.dat) + md5(nostale.dat) + LoginID)

There are two options for edit the packet at the fly..
- Editing the registers, you have to be able in reverse engineering.
- Using a broker, you have to be able in sockets programming.

The second option is definitely easier but as we say in my country, beautiful things are those that require more time.

As they already have mentioned, don't expect to restore long-standing bugs. Are serverside, the memory will doesn't solve your problem. Nothing will be able to do what you're dreaming..

Welcome in the real world, where fairies are nothing more than a figment of the imagination.

Nope.
Just searching in memory the old version number and changing to actual one, it's so easyyy.

[iArtrix]

Edit version in resource hack

[JMII89]

Originally Posted by ernilos

Nope.
Just searching in memory the old version number and changing to actual one, it's so easyyy.

I pratically said the same:

Originally Posted by JMII89

- Editing the registers, you have to be able in reverse engineering..

@ernilos Want you a clap clap for your affirmation ? I want recall that you aren't really good to reverse an application.. By when / what started the beginners to write "So easyyy." ? As you always say.. Pathetic.

Originally Posted by iArtrix

Edit version in resource hack

Nope, the login hash isn't calculated by file version. You have for sure to edit it but isn't the only.

[ernilos]

Originally Posted by JMII89

I pratically said the same:



@ernilos Want you a clap clap for your affirmation ? I want recall that you aren't really good to reverse an application.. By when / what started the beginners to write "So easyyy." ? As you always say.. Pathetic.



Nope, the login hash isn't calculated by file version. You have for sure to edit it but isn't the only.

Wrong number version throw's a server related error.

Good version throw's a login error.
It's easy as find in memory the vesion number ^-^

[JMII89]

Originally Posted by ernilos

Wrong number version throw's a server related error.

Good version throw's a login error.
It's easy as find in memory the vesion number ^-^

Congratulations, you have changed the new version number (8) in the previous issue (7) and did a screen. Too bad you have left out the hash, is different in each client. Is evident that your screens are fake. You keep acting like with the new lua in elsword some month ago. Well done.