Beiträge von Heggeg

    Hallo zusammen,


    gibt es bereits Informationen darüber wie man den 2x Char Attack Exploit der in zwei größeren türkischen Bots/Hacks implementiert wurde fixxed?


    Viele Grüße

    Heggeg

    _____________________________________________________________________________________________________________________________________________

    Hello all,


    is there any information on how to fix the 2x char attack exploit that was implemented in two major Turkish bots/hacks?


    Many greetings

    Heggeg

    Hello all,


    I'm trying to figure out how it used to be possible to bypass the old torrent patcher from the official Metin2 and start the client without a patcher.

    The reason why I want to start without the torrent patcher is that I have created a language pack for the official Metin2 Brazil and the community often has the problem to use the language pack because the patcher updates the changed files again. I can't figure out what the patcher does in addition to generating the key using the date/time.


    I already have a batch script with which I get the client started partially without problems. However, I must have started the client every 2 minutes once with the normal patcher, because this still changes 4 in my opinion dummy files in the client. If I started the client at 15:00 with the patcher normally, then I am able to start the client with my batch file without the patcher until 15:02. After exactly 2 minutes I have to run the patcher again to make it work with my batch file again. I see that after each patch operation the following files are processed:


    /lib/xml/dom/minidomer.pyc

    /lib/xml/parser/invers.pyc

    /pack/metin2_patch_nodelar.eix

    /pack/metin2_patch_nodelar.epk

    At least the .eix and .epk files I can't unpack with PackMaker unfortunately.

    The batch script looks like this:


    Code
    1. @ echo off
    2. echo 116807 >> 003254
    3. set /a key = 781072347 + (%TIME:~3,2% * 2) + 2
    4. metin2client.bin %key%

    Does anyone know what the patcher does additionally and why I can't start the client with my batch file after two minutes?

    DE:

    Hallo zusammen,


    ich versuche von einem offiziellen Metin Server (BR) eine alte Client-Version nutzbar zu machen. Ich bin so weit, dass ich mich mit dem Client wieder einloggen kann und teilweise Ingame bewegen kann. Zudem kann ich den Client ohne patchen starten und Xigncode wurde gebypassed sodass Veränderungen am Client vorgenommen werden können. Hin und wieder stürzt der Client allerdings ab und im syserr log erscheinen dann folgende Einträge:


    Code
    1. 0428 03:56:29364 :: CInstanceBase::RegisterEffect(eEftType=267, c_szEftAttachBone=, c_szEftName=d:/ymir work/effect/affect/damagevalue/nontarget.mse, isCache=1) - Error
    2. 0428 03:56:29365 :: CInstanceBase::RegisterEffect(eEftType=270, c_szEftAttachBone=, c_szEftName=d:/ymir work/effect/affect/damagevalue/poison.mse, isCache=1) - Error
    3. 0428 03:56:46292 :: Unknown packet header: 169, last: 143 143


    Der Client stürzt aber nicht jedes Mal ab. Es spielt hierbei keine Rolle, auf welcher Map man sich einloggt. Der Client stürzt gefühlt willkürlich ab. Sobald man aber Ingame ist und dort Interaktionen ausführt wie z. B. auf der Bazar Map NPCs anspricht, erscheint folgendes im syserr log:



    Mit meinem gefährlichen Halbwissen würde ich nun sagen, dass dort mit den letzten Client Patches Packets angepasst worden sind und der Client nun nicht mehr damit umgehen kann.


    • Habe ich überhaupt die Möglichkeit ohne Kenntnis von der Konfiguration auf Serverseite zu haben, die Packets so zu editieren, dass es am Ende nicht mehr zu Problemen führt?
    • Wie geht man bei der Anpassung einer Client.bin vor? Theoretisch glaube, ich habe ich die aktuelle und ältere metin2client.bin entpackt vorliegen. (Vielen Dank hierfür an dotpngr#3873






    EN:

    Hello all,


    I am trying to make an old client version of an official Metin server (BR) usable. I am so far that I can log in with the client again and move partially ingame. I can also start the client without patching and Xigncode has been bypassed so that changes can be made to the client. Every now and then, however, the client crashes and the following entries appear in the syserr log:


    Code
    1. 0428 03:56:29364 :: CInstanceBase::RegisterEffect(eEftType=267, c_szEftAttachBone=, c_szEftName=d:/ymir work/effect/affect/damagevalue/nontarget.mse, isCache=1) - Error
    2. 0428 03:56:29365 :: CInstanceBase::RegisterEffect(eEftType=270, c_szEftAttachBone=, c_szEftName=d:/ymir work/effect/affect/damagevalue/poison.mse, isCache=1) - Error
    3. 0428 03:56:46292 :: Unknown packet header: 169, last: 143 143


    However, the client does not crash every time. It does not matter on which map you log in. The client crashes seemingly at random. However, as soon as you are in-game and carry out interactions there, such as speaking to NPCs on the Bazaar map, the following appears in the syserr log:



    With my dangerous half-knowledge, I would now say that packages have been adapted there with the last client patches and the client can no longer handle them.


    • Without knowing the configuration on the server side, do I have the possibility to edit the packages in such a way that it no longer leads to problems in the end?
    • How do you go about customising a client.bin? Theoretically, I think I have the current and older metin2client.bin unpacked. (Many thanks for this to dotpngr#3873