romegames 1
romegames
noisiv 1
noisiv
Manwe Work 1
Manwe Work
Best Studio 1
Best Studio
kralhakan2009 1
kralhakan2009
Vahsi Uzman 1
Vahsi Uzman
InfernoShade 1
InfernoShade
BlackFullMoon 1
BlackFullMoon
Agora Metin2 1
Agora Metin2
PrimeAC 1
PrimeAC
ShadowFon 1
ShadowFon
Hikaye Ekle
Reklam vermek için turkmmo@gmail.com

Looking for an updated Metin2 client item_proto dumper

Dabtep

Level 1
Üye
Katılım
19 Eki 2025
Konular
1
Mesajlar
3
Online süresi
17h 23m
Reaksiyon Skoru
0
Altın Konu
0
TM Yaşı
7 Ay 24 Gün
Başarım Puanı
8
MmoLira
95
DevLira
0
Ticaret - 0%
0   0   0

ROHAN2 WORLD 1-120 TR TİPİ OFFICIAL YOHARA, BALATHOR VE AMON! 80. GÜNÜNDE! +10.000 ONLİNE! HİLE VE BOT %100 ENGELLİ HEMEN TIKLA!

Hi everyone,


I'm looking for an updated Metin2 client item_proto dumper .


My situation:


I have a client-side item_proto from (multi-lang) locale/en/ that is clearly in the newer binary format.
The file reports a struct_size of 176 bytes.
Most public tools I found only support the older 156-byte, so they either stop right away or throw a mismatch error like:

LoadItemProto: invalid item_proto structSize[176] != sizeof(SItemTable) [156]

I've tried around 7 different dumpers/converters (classic dump_proto, older ProtoReader builds, client→server proto converters, some JSON-based ones),
some of them didn't even start (crashed on load),
the rest all failed on the same thing: they expect 156 bytes per item, but this client has 176 , or they stop on unknown flags/applies like APPLY_ATTBONUS_STONE, ITEM_STACKABLE, ANTI_PET, WEAR_GLOVE.

I would like a dumper that can read a 176-byte client item_proto.

I'm attaching the item_proto (rename to gif, because I can't upload the original, so just remove the .gif tag) that needs to be unpacked, so you can test directly against the real file.


If anyone has a newer ProtoReader / DumpProto build that already supports this 176-byte layout, or source code that handles “struct_size > sizeof(SItemTable)” by skipping the extra bytes, that would solve it.

Thank you in advance!

Regards,
Dabtep
 
Hey Dabtep,

Interesting case — thanks for the detailed description. Before diving into a potential fix or rebuild, could you please share some technical details about your environment? Specifically:
  • Which client version or build date are you using? (e.g., private source build, etc.)
  • What locale structure is it using (multi-lang, locale/en, or locale/xx rebase)?
  • Which compiler or runtime setup was used (e.g., VS2019, GCC, etc.)?
  • Is your client binary packed or modified in any way (e.g., with Themida, custom loader, or encrypted item_proto)?

The 176-byte SItemTable variant suggests a more recent structure revision (post-2021 builds often include extra anti-flags, apply blocks, and bonus types).

If you can confirm your client environment, we can narrow down the struct changes — or at least patch an existing dumper to dynamically adapt when structSize > sizeof(SItemTable) rather than failing.

Once we know your setup, I can check whether my current ProtoReader (built on the 19.6 source base) can be modified to parse the extra 20 bytes cleanly.
 
Hey,


thanks for your time and the quick reply,


I’m working with AVA2 server files and the client that belongs to that pack. It’s a multi-language client, but right now I only want to touch the locale/en/ part. In this client the files don’t have extensions and there’s no classic .eix / .epk pair, in the pack folder every resource is just one file (no extension) per folder (locale, root, ui, etc.) on the other hand thats my second problem, I don't know how to unpack these files, I have only the encrypt method with prueba.bat. So my item_proto is literally pack/locale/en/item_proto.


On the server side I have the usual:
  • item_proto.txt
  • item_names.txt
    and those work, the server reads them. But in this client-side proto there are extra anti flags and bonus types (that’s why your guess about a newer structure was fully correct).

Compiler: I’m on VS2019.


About your last question I wasn’t 100% sure what you wanted there, but here’s what I can tell you:

the client exe is built from source and can be compiled with VS2019,
I don’t know about any additional protection/packing on the exe itself (no Themida that I’m aware of),
but the files inside the pack/ folder are encrypted (locale/root/ui/etc. are not plain).



So to summarize:
  • client: AVA2-style, multi-lang, flat pack (no eix/epk)
  • file: locale/en/item_proto
  • header says: MIPX, structSize = 176, tableSize ~ 11k
  • this proto definitely has extra anti-flags / bonus types

Thanks in advance,
Dabtep
 

Şu an konuyu görüntüleyenler (Toplam : 0, Üye: 0, Misafir: 0)

Geri
Üst