ure solution would be to redo the netstat thing and find something with 2106 port? K so lets say i did all of the above wrong. Wich is the same IP my current bot shows when i log in game (that ip is shown in the picture, then one that u cant see). So the only thing i had close to 2106 in netstat, that shows up on the list list is the ip with 2107 "The login server port, usually its 2106, so if u use this u will no have problems." In the CMD window type: "netstat -n", then in the results(remote adress), search for this ip: :2106, where the Xs will be your server IP " Start lineage2 as usual, then login and when you get the server list minimize L2.exe and click START, then RUN and type CMD. If your l2j server uses a modified system, do this: Most of the l2j servers provide you and ip to add in your host file, that will be your ip and you can skip this step. Ok dude, want me to type that a 3rd time? L2DAP wrote:the pic is not using "netstat -n" So I have no idea were the above pic come from Nicooolito Registered User Posts: 17 Joined: Fri 08:22 AM So my solution was to throw the 9.3.2 files into the 9.3.0 files but i still get the same error :/Īny ides what i should do? should i try to repack the 9.3.2 files in a older IG version or a newer IG version of l2 divine?Īlso in "l2.bin" select, i cant find l2.bin, just l2.exe couse this private server had it removed in system folder, is there any way to create a l2.bin or bypass it somehow and select l2.exe in l2divine instead?. So if i close this i can still setup server connect info, but i cannot save it. "l2 divine found and installation error do you wish to continue" and if i press yes, then when i open the config window i get : "unhandeled exception has occured in your application bla bla bla bla bla" Wich is IG mode, but problem is when i un pack it it gives me a error: Wich seems to be the OOG divine, since i cant select to lauch l2 window in it
Ill post this here since "private server" section is close to dead )