Jump to content

Recommended Posts

Posted

hello folks well this time share this usefull guide from users want protect own servers for avoid programs for example,walkers,halpex,l2phx and others so i explaint how to configure options ok lets start guys first of all clarify what incluided this pack and info about that

 

1. Included in the package is:

 

[updater/Loader Components]

-LineageII.vmp1.exe

-Config.exe

-AuthD_BK_C135.exe

-AuthDBK.dll

-AutoUpdata.inf

-user.ini

 

[Registration Components]

-Preg.exe

 

[server Control Components]

-Project1.exe

 

[update Component]

-Updata.inf

-Upinf.exe

-TbkCheckFile

 

A. Updater/Loader Installation Guide

============================

    A.1 Config.exe Usage

 

        A.1.1 [Config]

 

        notice:

        ---------

        leave blank to not show any announcement page

        ;notice=http://lin2post.lineage2.com.tw/index.asp /*Official Taiwan*/

        ;notice=http://l2post.lineage2.co.kr/main.html /*Official Korea*/

 

        homepage:

        ----------------

        set homepage URL to display homepage upon clicking forum button

 

        bbs:

        ------

        set forum URL to display forum upon clicking forum button

 

        regist:

        --------

        set registration URL to display registration page upon clicking registration button

 

        A.1.2 [Option]

 

        infoURL

        -----------

        set URL to download autoupdata.inf. *NOTE 1 (Check Bottom)

 

        ExePath

        -----------

        set folder name where l2.exe is located, default is ..\system, you may set ..\l2system if you wish to change your system folder name

 

        webreg

        ----------

        enable this to bring user to register on the web instead of from preg.exe module on server

 

        Revision

        ------------

        set protocol version for client, you'll not be able to logon server is protocol version isn't correct

 

        Method

        ----------

        Login method, choose login method depending on the l2server.exe you're using

        C4 - for official C4 l2server.exe

        C5 - for modded l2server.exe which supports C5. e.g. ET or AJIA L2 Extender

        NFC5 - for NF version of l2server.exe with minor mods to support C5 client

        Interlude - for Interlude version of l2server.exe

 

        LoginPort

        --------------

        Set port number on server to connect to AuthD

 

        RegPort

        -----------

        Set port number on server to connect to Preg, must be same with IP set in regset.ini

 

        CreateInk

        -------------

        Check this to create desktop shortcut during lineageII.vmp1.exe execution

 

        Autorun

        -----------

        Check this to autorun upon Windows startup

 

Notes 1: During execution of LineageII.vmp1.exe, it'll lookup path for autoupdata.inf, if value of #version in client side is lower than server side's #version value, then it'll refer to server side  autoupdata.inf parameter and download the updated files, consequently it'll also decompress mc.zip content and patch it over client side's data.

 

    A.2 Setting up server side update files

       

        A2.1 Setting up client files update pack

        All client sided updates needs to be packed in only 1 file and be renamed into mc.zip, to compile these files, you have to put client files in their respective folder as it is intended to be updated in client side, e.g. weapongrp.dat must be in system folder etc.., then select those folders and compress it in .zip format, then rename it to mc.zip

       

        A.2.2 Setting up Autoupdata.inf parameters

        #url1- set URL to download mc.zip

        #url2 - set URL to download BK loader/updater

        #url3 - set URL to download autoupdata.inf

        * Leave url3 blank and specify autoupdata.inf in url2 if you do not wish to provide BK loader/updater updates

 

        A 2.3 Increase Autoupdata.inf #version value

 

http://rapidshare.com/files/209225270/Bake_Ice_Loader.rar

 

Credits to -VeNoX-postpacific

 

  • 2 weeks later...
  • 5 weeks later...
  • 2 weeks later...
Posted

Its not a virus, its just an edited file, code or whatever, it will always detect you as a virus, if this is a virus so the l2.exe file official from ncsoft is a Win32/Packed.Themida potentially unwanted .... lol

 

P.S Thanks for share CriticalError

Posted

Its not a virus, its just an edited file, code or whatever, it will always detect you as a virus, if this is a virus so the l2.exe file official from ncsoft is a Win32/Packed.Themida potentially unwanted .... lol

 

P.S Thanks for share CriticalError

 

bullshit

Posted

bullshit

 

Ok its your problem i tried and my pc is fine and i dont have problems and i set off the item as a think that antivirus wont bother it.

For me works, so thx again for share.

Posted

bullshit

well man you are not right don't put bad words is totally true sometimes antivirus give some files are troyan and is not the true for example l2.exe and is a virus no!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Guest
This topic is now closed to further replies.



  • Posts

    • LIVE VERIFICATION? SUMSUB? “IMPOSSIBLE”? ▪ Spoiler: it is possible — if you know who to work with. A client came in with a task to pass **live verification** on **WantToPay**, a Telegram virtual card service. On the platform side — **Sumsub**: liveness check, SMS, manual review. “Fast” and “by eye” simply don’t work here. › What was done: → analyzed the verification scenario and Sumsub requirements → built the correct flow: phone number, email, timing → **completed live verification remotely, without account handover** → handled SMS and confirmation codes → brought the process to final approval ▪ Result: → verification passed → access granted → no flags or repeat requests ▪ Live verification is not luck. It’s scenario-based preparation — not hope. › TG: @mustang_service ( https:// t.me/ mustang_service ) › Channel: Mustang Service ( https:// t.me/ +6RAKokIn5ItmYjEx ) *All data is published with the client’s consent.* #verification #sumsub #livecheck #kyc #case
    • IMPORTANT INFO: In a few days, I will switch to completely new code, written from scratch with a new download system, patch building and management system. The Updater will become true 2026 code with "foolproof systems". I'm going to create a Discord server for customers to request new ideas and features. FIRST CUSTOMERS ARE ALREADY USING THE NEW UPDATER ON LIVE SERVERS! Watch this topic for upcoming info because the new updater is around the corner! Yes, you can still use self-update on the previous updater! No, the new updater won't be compatible with the old patch system! A new build is required, but players who already have game files won't have to download the entire patch again! New templates and updates to existing templates are coming soon! Sneak peek:  
    • i used guytis IL project and source. i found in his project there are 3 Client version source... 1,CliExt_H5   --->this one cant be compiled in VS2005,i did know why..is it for H5 client? 2,CliExtNew  --->this one is IL version ,but when i compiled it and use it.player cant login game,MD5Checksum wrong.i check the source code,but not found any hints. 3,L2Server    --->this one for HB client?im not sure...   so my question is what are the differences between these three versions of cliext.dll?how can i fix the issue of the MD5Checksum not matching problem?   01/29/2026 21:04:11.366, [CCliExt::HandleCheckSum] Invalid Checksum[1130415144] vs [-721420287] packet[dd] len[29] sum[2698] key[30] HWID[] Account[]! 01/29/2026 21:04:11.366, SocketLimiter::UserSocketBadunknownprotocol 11111111111 01/29/2026 21:04:11.366, [usersocket]unknown protocol from ip[113.137.149.115]!      
  • 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..