Jump to content

Recommended Posts

  • 3 weeks later...
Posted

Definetely not a good idea.

 

If you change protocol version it has to be changed in l2j's serverpackets and clientpackets.

Besides that there's absolutely no reason to do that, even ncsoft doesn't know why protocol version exists and even if they do, l2j surely doesn't.

Posted

if we change protoco version you cannot move l2.ini to another system, cause server won't allow log in with a diferent version, so if i put protection in system how to avoid that?

Posted

They'll take the client files related to Protocol Version move them to an unprotected patch and done. Besides that ALL client protections (no connection with Java) are lame and can be easily bypassed.

 

If you want to protect yourself that way the best thing you can do is LameGuard. Running for a couple of years and still, it hasn't been bypassed.

Posted

I have no idea how the cracked one works since i don't know russian. Only someone who speaks russian can help you or someone who has the time and the patience to decompile the lameguard library and understand its functionality.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..