Jump to content

L2.NET Interlude-latest support


mpj123

Recommended Posts

no idea about Frintezza

 

Chronicle?

Anti bot?

Server ip?

 

np, glad you worked it out.

 

Hellbound

As far as I know they have a kind of anti-bot system which allows you to log in with L2W and such, later it reports you randomly one time per week or something like that (Fire.dll ?)

66.71.248.34 (I think it's the correct one)

Link to comment
Share on other sites

not sure how they are detecting if you are botting or not, but L2.NET shouldn't be detectable via packets. Only via client side protections.

 

You can make sure this never happens by using the L2 client on one computer, and rerouting the ip to your second computer/vmware client running l2.NET... I recently put up a guide on ltwonet on how to do this.

Link to comment
Share on other sites

not sure how they are detecting if you are botting or not, but L2.NET shouldn't be detectable via packets. Only via client side protections.

 

You can make sure this never happens by using the L2 client on one computer, and rerouting the ip to your second computer/vmware client running l2.NET... I recently put up a guide on ltwonet on how to do this.

 

Following that will I be safe or almost safe ?

Link to comment
Share on other sites

Depends how they are detecting... cant say 100% safe or anything, but it should be hard to detect... specially with The bot not even being on the same computer. And if L2.NET's packets are detectable then thats the first time I would hear about it.

 

I'd say your pretty safe.

Link to comment
Share on other sites

you probably have the wrong token/blowfish... I dont play there, I dont know. But thats what is seems like.

 

I'm using the blowfish which comes with the L2.net, is that wrong ?

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.




  • Posts

    • Welcome to my store : https://topestore.mysellix.io/fr/ 2015-2022 Aged Discord Account 2015 Discord Account : 60.99 $ 2016 Discord Account : 10.50 $ 2017 Discord Account :4.99 $ 2018 Discord Account : 3.99 $ 2019 Discord Account : 2.99 $ 2020 Discord Account :1.99$ 2021 Discord Account :1.50$ 2022 Discord Account :0.99$ Warranty :Lifetime Payment Methods : Crypto/ PayPal Contact Me On Discord Or Telegram Discord : @ultrasstore11 Telegram : https://t.me/ultrastore11 Whatsapp ; +212614849119
    • The heavy lifting is done in the client, because while you can get away with small imperfections in the java, everything in the client must be impecable. So, if you haven't touched the client, I'd say pick the newest protocol version you can find the client editing tools and Interface.u (mandatory) / NWindow.dll (better to have it) / Engine.dll (optional) sources for. At the very least, you need the Interface.u to fix the Clan Window and enable skill enchanting on Classic/Essence versions, if you decide to use one of them instead of MAIN/LIVE.
    • Thanks for clarification. Do you think the newest clients offer solid advantages compared to the classic ones like Salvation? I'm also in the process of porting h5 to one of them just for the sake of it, so I was wondering if I should just attempt to go to the newest possible.
    • Upgrading to Salvation is exactly the same as upgrading to the newest client with the only difference being access to free-shared client editing tools and resources. I am speaking from experience. I have upgraded my HF source to one of the newest clients by myself (in terms of server side. got help with the client) and hit every single wall there was in the process. Now, I already have several multi-protocool server cores so I can easily compare different approaches to tackling the same issue, which also helped the learning process. Best way to learn would be to use this one (link below) to snoop around and figure out what has been changed in the server side (the packet structure will be different, for sure, but works for understanding/figuring the process out in general terms). https://github.com/iBezneR/L2J_SunriseProject_Purity The client side will always be the same, always the same files, only the DAT structure will be different. I personally wrote myself some parsers for the data of the DAT files from OLD -> NEW client.
  • Topics

×
×
  • Create New...