Distraught

And that's what is incorrect.

There is no x32 or x64. There is x86, which is an instruction set, but it has nothing to do with being 32 or 64 bit. There are x86 and x86-64 too, but they are the same, with an extension over the other. That is how even registers got named. In the 8-bit era, registers were named like AL and AH (BL, BH, CL, CH, etc) (meaning A low and A high). Then later, when we ascended to the 16-bit era, they became one and named to AX, BX, CX, etc. After we reached the 32-bit era, they got 32-bit wide and had to find new names to be able to address its native 32-bit view, so they became EAX, EBX, ECX and so on (E meaning extended AX, etc). In the 64-bit era, they got wider again and got the name of RAX, RBX, RCX (R just means register, cause they already used E as extended, so they needed to find something else not to be ambigious).

“x32, x64” - we arrived at the era of vibe coders

I officially close the development of these files. I got fed up of ungrateful people badmouthing me because I don't work for free constantly on this project. I did way more for this community over the years, than most of the people, but when you give your pinky, they want your whole arm. I never signed up for updating these files for eternity, and I completely had enough of many a-hole pricks.

As sadly many people with massive AI usage pushed a lot of things I take back the merge rights to only myself. The next weeks I'll go through all the past merges and check through those codes, to get this project back to a good state.

Opening Date: 27/02/2026 18:00 CET Website: https://landofheroes.eu/speed-server Discord: https://discord.gg/landofheroes Facebook: https://facebook.com/landofheroes.eu

I'm closing the addition of new updates to the files for some time and I'll only accept bugfixes. When the files are stable again, we'll do the new updates to it more organized with monthly meetings.

Yes. I wanted to do a big community project and this is what it has become.

UPDATE Python 2.7 upgraded to Python 3.14 with JIT enabled Lib folder removed from client, python libs are built into the binary Performance benchmark between Python versions: [Source: [Hidden Content]] This benchmark was done with a pretty similar use case to Metin2.

New PRs have been merged, the mentioned build errors shouldn't exist anymore.

There is nothing there yet. But join guys to my Discord, there is a topic for the development of the files.

Sure: [Hidden Content]

It's called placebo. The game won't change visually just because you use a different graphics API. The game will only look different if you write shaders for it to alter how things rendered.

Sorry, but I'll have to discard this PR. I deliberately did not use submodules, vcpkg and other things so the repo is completely self contained and not dependent on the availability of other repositories or pre-installed system libraries. This would break this principle. What if a repository gets deleted or made private? For pre-installed system libs it's even worse: what if there is a breaking change between the version we used and the version installed on the system? For example MariaDB is built with DEFAULT_SSL_VERIFY_SERVER_CERT=ON by default since version 3.4. Maintainability and being able to reproduce the exact same builds are much more important than having lower build time in general. Let's try to keep ourselves to standards. Request access to the official Trello board so everything is kept together.

My point here was never to fix Metin2 bugs or implement features. Only to modernize backend things and make it a standard that people use CMake and has a well organized work environment. This project is intended for people who wants to learn and put their own effort into building something. Also, as I pointed out in the original post: contributions are welcome. If someone wants to fix old Mt2 bugs, make a PR.