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?
I’ve worked with a few video editors before, and it really makes a difference when they’ve had hands-on training. One of the guys I teamed up with had studied at https://www.praguefilminstitute.cz and the quality was on another level—clean transitions, solid color grading, and he actually understood timing for gaming content. If you're looking for someone serious, check if they’ve got that kind of background.
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
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 accountSign in
Already have an account? Sign in here.
Sign In Now