Jump to content

Recommended Posts

Posted

Hi evry1, this is my first post hope it is useful.

 

If u guys get a file size error when runing the game on ur IG walker it means that the file on ur system folder named L2.exe is not the right one that IG walker can work with. So simply what u got to do is changing the names of the files normaly named as L2.exe and Lineage2.exe. DEV's love to change them cause this way half of the boters stop before they could find out why they cant log. So to make it work u just have to name L2.exe-->Lineage2.exe and Lineage2.exe-->l2.exe but u have to make one diferent for a while cause their will be 2 = and the computer wont acept, so is just change one and then the other and then fix the first one.

 

If this only fix the file size error but not the log in it is another problem. Like i play L2forever and there they have also changed the .ini files. so u also have to change this names like before just exchange the names.

 

Hope u understand me >.< Hf

Posted

I work with IG 1,50 and had this prob. Tried to rename the lineage2.exe to l2.exe but

i couldnt connect. So next step was to check the .ini files as u said.

The only two .ini files tha had the path of exe file was

1) lineage2.ini

2) lineage2gg.ini

and change the var : EXEName=lineage2.exe ---> EXEName=l2.exe

 

But still i cant log in. So any idea here ??

 

PS. On forever server.

 

 

Posted

make a new update so ur system file will get back like it was. then u got a file named L2f.exe( an edited icon) change that one to Lineage2, then the other lineage2.exe change it to l2.exe. now when those are done, its the .ini files part, so u got L2.ini and lineage2.ini. u got to have them.(if u dont, when u update like i said u will get them.) so then is just open ur Ig walker load the new l2.exe file from the walker and voila ;p hf

Posted

rename lineage2.exe ----> l2.exe

rename l2f.exe ----> lineage2.exe

open lineage2.ini in system file and change the var : EXEName=lineage2.exe ---> EXEName=l2.exe

decode with l2encdec (use search) the l2.ini file an add the IP of forever and change

the var : EXEName=lineage2.exe ---> EXEName=l2.exe

 

I'm using walker 1.50

Ps: it is obious tha u have to change the hosts files and use larsv. Use search

 

 

Posted

rename lineage2.exe ----> l2.exe

rename l2f.exe ----> lineage2.exe

open lineage2.ini in system file and change the var : EXEName=lineage2.exe ---> EXEName=l2.exe

decode with l2encdec (use search) the l2.ini file an add the IP of forever and change

the var : EXEName=lineage2.exe ---> EXEName=l2.exe

 

I'm using walker 1.50

Ps: it is obious tha u have to change the hosts files and use larsv. Use search

 

 

Very usefull  ;)

 

I made a file for those who feel the guide hard.

 

Extract this to your system folder overwriting the files.

 

rename l2f.exe ----> lineage2.exe

rename lineage2.exe ----> l2.exe

open lineage2.ini and change:  EXEName=lineage2.exe ---> EXEName=l2.exe

decode l2.ini an add the IP of forever:  ServerAddr=xxx.... ---> ServerAddr=208.72.155.114

decode l2.ini and change:  EXEName=lineage2.exe ---> EXEName=l2.exe

Posted

or just go to www.towalker.com and download the newest ingame :S

It wont work with that only. You need l2asrv and edited system files also (see my post).

 

PS Haven't checked to log in there for a while. So my files might not work. Test out and see.

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


  • Posts

    • Hi, great work! Are there any bugs? And will it work with a high five?
    • For others that would like to understand in more details:   The login server also uses a protocol (sent by the server to the client in the very first packet). For instance, the C4 client (the one I'm developing my emulator for) expects the protocol number `50721` (or `0xc621`) which works as follow (from what I've gathered): Preamble: L2 packets are divided into two parts: size and payload; As mentioned, every packet starts with two bytes containing the whole packet size (thus including those two bytes, e.g. a packet of size 15 will have the number `15` written onto its first two bytes and a following payload of 13 bytes); For login server, first byte of the payload is the opcode (game server must deal with variable-sized opcodes); Next bytes are the packet content; Before sending the packet, its buffer size (minus the initial two bytes) is padded to 8 bytes (required by upcoming Blowfish encoding); A checksum of the packet is appended at the end, then the payload is again padded to 8 bytes; If the opcode is not `0` (also written as `0x00`), then the payload is encoded by Blowfish; Packet is sent over the network. You can have a look at my implementation (in C++) here (do note I'm assuming little-endian).   In this protocol, the auth packet (`0x00`) sent back by the client is RSA encrypted using the RSA modulus sent in the first server packet, inserted right after the protocol number.  
    • Hello guys I wanna buy some  Lessons for an L2J Developer
    • Let me give you something for inspiration and get you addicted to bot AI     And a siege 😛     What I have notice helps a lot the LLM to act real, is to give it a real-persons background. So for each LLM in the context beggining, besides the L2 facts, give it a real-life back story "You are a 67 years old retired nurse who plays Lineage 2 while her husband reads his newspaper, you are calm, collected but get mad if insulted". But that makes for a creative bot but its repetitive. So what you can also do, is pick random 20 news sites and for each bot every 2-3 days, initialize a context that is affected by the "news" the bot reads in the "real world".  So for example there's Iran - US war ok ? You take the news, put it in an LLM and ask it, extract the "abstract feelings" that this news piece invokes into you without mentioning anything related to the news. Then you take the result and inject it to the bots LLM prompt after its backstory.  This leads to some VERY human-like behavior from bots. 
  • Topics

×
×
  • 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..