Costumes
3D models and more 3D models...
It's overflowing!
29 topics in this forum
.thumb.jpg.021d7f8b0e6d25cad61c1533754714b9.jpg)
-
Current Donation Goals
-
Current MonthRaised 23.00 EUR of 65.00 EUR target
-
-
Activity
-
1
-
1
Black Steel Armors with wolfman
Download Alternative download links → Mediafire DL: contains Hungarian and English set names Icons:- 2
-
-
0
Korean server-side translations
I've been seeing some posts about old KR clients and I can tell that the community is still interested in this language and old files. What I couldn't find anywhere is Korean serverfiles or server-side translations such as the equivalent of translate.lua or oxquiz.lua. locale_string.txt already contains the Korean translations so that's the easy part. Item and mob names can be found in the latest GF proto dump for anyone looking for them Skill names can be obtained by any skilltable.txt read in EUC-KR encoding Client side translations are obviously obtained from one of the Korean client downloads available out there. So all that's really missing here is quest and quiz strings, if anyone knows how to get them please drop a link down in the comments, if the link contains translations for Dragonsoul and Belt system that would be additionally awesome! If you are looking for these resources as well drop a reaction to this post so more people see it -
6
fix Fix Skill Toggle when Dead
How to fix the Aura of the Sword/Stealth/Feather Walk/Swiftness and similar effects being attached to the mesh after death: This is about what @WhiteBambo asked specifically, I've seen a lot of clients having this and this is not relevant to togglable slots and skills. The reason this is happening is because of the server's 3-second stun-death (classic mechanism from YMIR) and this should be an easy fix by this guide: Please adjust changes for your own source!!! Normally, when a monster or player kills you, the server first sends a stun packet and only 3 seconds later the real death with the affect clear. The client handles that stun packet by calling Die() at once for your own character, and Die() wipes the affect flags without running each affect's off path. When the server's "flags off" update arrives 3 seconds later, the client sees no change and never detaches the visuals that live outside the affect slot array, such as the Aura of the Sword weapon glow, the reach scale and the stealth alpha. That is why only your own corpse shows it, never other players' screens, and why /kill and one-shot deaths are clean: those skip the stun packet. The client fix below makes the early clear run every off path properly. Making deaths instant server-side also avoids it, but that is a gameplay decision, not a fix. Some client-side fixes: Swiftness and Feather Walk can survive this fix in some clients, as well as overwrite eachother, or show to observer clients even if the character's movement has stopped! Test whether you have this before applying the following fix: Catching false-positive flags and disabling them (the actual client-side fix for this issue): -
4
-
1
[Work in Progress] QuantumCoreX
Sadly I have to say goodbye to this site. Sadly I cannot change my email address to anything not Google. I don't use Google anymore so I don't even have access to the email inbox linked to this account. This is unfortunate but support here is basically non existent. Saying farewell to this forum. You can't ban me because I'm closing my account myself. The project will stay available over at Github and maybe some other forums.- 1
-
-
0
MOB DEATH DISSOLVE
Mob Death Dissolve System When a mob/NPC dies, its model dissolves away in irregular patches (disintegration look) over a few seconds, instead of the corpse just popping out. [*]Noise-based patch dissolve (not a flat fade), triggered on death [*]Mobs/NPCs only — players excluded [*]Configurable speed & patch size, and toggled by one define (easy revert) Download- 16
-
-
-
43
-
0
System Installer
I believe this is the right section for this post. I want to issue a warning to potential users right away: while the program handles a significant portion of the system-adding process, I strongly advise against using it on any files that aren't integrated with GitHub. You should always verify the changes the program makes via GitHub. Since the program operates at a basic level, the error rate is negligible for simple instructions (like "search," "add below," or "replace"), but it can go a bit off-track with complex instructions. Therefore, it is essential to review the changes it makes. By using GitHub, you can both monitor the program's modifications and manually apply changes where necessary. This program was designed not to automate the entire installation process, but to reduce the time you spend working on the system. I hope it proves useful to everyone. Running the `build.bat` file included in the RAR archive will generate an executable (.exe) file for you. When you launch the executable, you will see the program interface. You can use the "Test" button to see how much of the code is being added, and click the "Add System" button when you are ready to apply it to your files. The button to undo the changes is clearly visible. Enjoy using it. What is it and What Does it Do? Metin2 System Installer v1 is an automated, smart integration tool that seamlessly patches Metin2 systems (e.g. Aura System, Won System, 6-7th Bonuses, Mailbox System, etc.) into your Server and Client source code with a single click. It eliminates hours of tedious manual searching, eliminates syntax errors, header class scope mismatches, and macro conflict issues. Key Features Smart Code Search & Block Matching: Automatically parses system instructions (Search, Add Below, Add Above, Replace, Add to End of File) from natural language guides, diffs, or code files. C++ Header Scope & Class Boundary Protection (}; Protection): Guarantees that member methods and variables inside header files (.h, .hpp) always remain strictly inside the class before };. Eliminates C2039: not a member of class compilation errors. Macro Boundary Isolation (#ifdef Isolation): Prevents newly inserted #ifdef blocks from getting trapped inside unrelated preceding #endif scopes. Safe Dry Run (Simulation Test): Test-runs the entire integration virtually without modifying a single file on disk. Reports all additions, skips, and potential warnings beforehand. One-Click Rollback (Undo): Creates automatic backups before applying modifications. If something goes wrong or you change your mind, undo the entire installation with one click. Built-in Visual Diff Viewer: Inspect searched code versus the closest code in your source file side-by-side in a split window. Bilingual UI ( Turkish & English): Switch between Turkish and English instantly using embedded flag buttons. Remembers your language preference. Automatic Visual Studio (.vcxproj) Registration: New .cpp and .h files included with the system are automatically placed in the correct directories and registered in .vcxproj and .filters files. What This Tool CANNOT Do (Limitations & Disclaimers) Does NOT Compile Visual Studio Solutions (.sln): The tool edits and registers source files; compiling the final binaries in Visual Studio is done by the developer. Does NOT Fix Incompatible C++ Architecture: If a system requires third-party dependencies, missing packets, or incompatible structures that don't exist in your base files, developers must adapt the underlying logic. Does NOT Modify Encrypted Pack Archives (.epk/.eix): The tool works on unpacked client scripts (root, uiscript, etc.) and C++ files, not encrypted archive packs. Does NOT Execute Live SQL Queries: Files like .sql or proto files are copied, but it does not execute queries directly against your live MySQL/MariaDB server. Does NOT Guess Beyond Completely Restructured Code: If the code you are searching for has been completely rewritten or deleted from your file, the patcher will safely skip that step rather than corrupting your source code. There is only the code, no .exe file. Download Alternative download links → Google Drive -
0
Great OfflineShop db leak fix
Dear friends, I found a SQL-side bug in the "Great Shop" system that was causing the `player.item` table to bloat. I have fixed it—the implementation is shown below—but I would like to ask for your opinion: do you consider this an optimized and correct fix? Thank you in advance for your comments, and I wish you success in life. void ITEM_MANAGER::SaveSingleItem(LPITEM item) { #ifdef ENABLE_FIX_SKIPSAVE_ITEM_LEAK if (item->GetSkipSave()) return; #endif if (!item->GetOwner()) { DWORD dwID = item->GetID(); DWORD dwOwnerID = item->GetLastOwnerPID(); db_clientdesc->DBPacketHeader(HEADER_GD_ITEM_DESTROY, 0, sizeof(DWORD) + sizeof(DWORD)); db_clientdesc->Packet(&dwID, sizeof(DWORD)); db_clientdesc->Packet(&dwOwnerID, sizeof(DWORD)); sys_log(1, "ITEM_DELETE %s:%u", item->GetName(), dwID); return; } sys_log(1, "ITEM_SAVE %s:%d in %s window %d", item->GetName(), item->GetID(), item->GetOwner()->GetName(), item->GetWindow()); TPlayerItem t; t.id = item->GetID(); t.window = item->GetWindow(); switch (t.window) { case EQUIPMENT: t.pos = item->GetCell() - INVENTORY_MAX_NUM; break; #ifdef ENABLE_BELT_INVENTORY_EX case INVENTORY: if (BELT_INVENTORY_SLOT_START <= item->GetCell() && BELT_INVENTORY_SLOT_END > item->GetCell()) { t.window = BELT_INVENTORY; t.pos = item->GetCell() - BELT_INVENTORY_SLOT_START; break; } #endif default: t.pos = item->GetCell(); break; } t.count = item->GetCount(); t.vnum = item->GetOriginalVnum(); switch (t.window) { case SAFEBOX: case MALL: t.owner = item->GetOwner()->GetDesc()->GetAccountTable().id; break; default: t.owner = item->GetOwner()->GetPlayerID(); break; } thecore_memcpy(t.alSockets, item->GetSockets(), sizeof(t.alSockets)); thecore_memcpy(t.aAttr, item->GetAttributes(), sizeof(t.aAttr)); #ifdef ENABLE_SOULBIND_SYSTEM t.sealbind = item->GetSealBindTime(); #endif db_clientdesc->DBPacketHeader(HEADER_GD_ITEM_SAVE, 0, sizeof(TPlayerItem)); db_clientdesc->Packet(&t, sizeof(TPlayerItem)); } LPITEM ITEM_MANAGER::CreateItem(DWORD vnum, DWORD count, DWORD id, bool bTryMagic, int iRarePct, bool bSkipSave) --inside #ifdef ENABLE_FIX_SKIPSAVE_ITEM_LEAK item->SetSkipSave(bSkipSave); #else item->SetSkipSave(false); #endif @ Amun @ martysama0134 @ Intel @ Karbust @ Geoffrey @ Mali @ Owsap @ Distraught
-
