To point my 'l2.ini' to my WAN IP, I followed the USER guide to decrpyt:
l2encdec -l l2.ini
And encrpyt:
l2encdec -e 413 dec-l2.ini
This is an interlude pack. However, whenever I execute L2.exe, nothing starts. But when I revert back to the original l2.ini which is version 413, the executable starts fine.
Am I doing something wrong? Is there another method to point my client to connect to my server so I can log ingame?
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Always remember, when you buy files, just compare with my files that I publish for free. and you will know that you are being ripped off.
Greetings to all community!!! 🙂
he kept his promise! i think it's a good idea to unban his old account. he shares files with the community and could help both new and veteran l2off users!
good job, Guytis!
Question
segfault
I have the main server executable loaded up.
To point my 'l2.ini' to my WAN IP, I followed the USER guide to decrpyt:
l2encdec -l l2.ini
And encrpyt:
l2encdec -e 413 dec-l2.ini
This is an interlude pack. However, whenever I execute L2.exe, nothing starts. But when I revert back to the original l2.ini which is version 413, the executable starts fine.
Am I doing something wrong? Is there another method to point my client to connect to my server so I can log ingame?
4 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.