How Metin2 private servers are building mobile clients

Metin2 private-server developers are taking two distinct routes to mobile: adapting the existing PC client, or rebuilding the client in an engine such as Unity or Unreal while recreating its communication with the server. Public threads now describe both, with very different levels of completion.

The interesting work goes beyond a virtual joystick. Developers have to bring over the world, animated models, inventory and network behaviour, then make them usable on a small touchscreen. The projects below show where that work is happening. Their documented state was checked on 24 October 2026; developer reports are attributed, and no APK was installed or independently benchmarked for this article.

Generated illustration based on Metin2 character references; the phone interface is concept art, not a screenshot of a named mobile client.

In the BGFX/FGR2 development diary on Turkmmo, started on 29 August 2026, the author describes a shared C++ core with BGFX handling graphics across platforms. The posted setup uses OpenGL ES 3 on Android and D3D11 on Windows. The author reports login, world entry and character-animation work on a physical Android device; Vulkan and iOS Metal appear as later targets.

That approach tries to retain the original client's behaviour while replacing platform-dependent pieces. Its FGR2 work addresses how model and animation data reach a portable runtime. A new renderer alone would not make the old Windows interfaces, game data and controls work on a phone.

Andro2, another Turkmmo project introduced on 30 September, describes an Android NDK/ARM64 build of the original C++ client with a DirectX 8-to-OpenGL ES 3 translation layer. Its author says the network protocol is preserved. That is a project-specific claim, not a promise that the resulting client can connect to every private server.

A different route is to rebuild the front end. In a 29 May 2026 M2Dev thread about a Unity/mobile client, the developer lists terrain loading, GR2-to-FBX conversion, models, animations and initial login/packet-flow experiments. Those are the foundations of a client; the post describes work in progress and a longer-term Android/iOS goal.

There are also commercial projects. The Alesta2 Mobile presentation on Turkmmo describes a Unity 6 client, converted game assets and PC/mobile access to the same server. An Alesta2 Mobile Google Play listing was publicly reachable when checked and showed an update dated 22 October 2026. The listing establishes an Android store presence; cross-play, feature coverage and performance remain the developer's statements rather than results of our testing. The forum post says its iOS release is awaiting review.

Cynex Mobile's Turkmmo diary, opened on 27 September, takes the Unreal Engine 5 route for PrimeSchool. The team describes a new mobile client intended to speak the existing server protocol. Later replies discuss friends/private-message work and the choice of C++ and Unreal. This is an actively discussed development project, not evidence that every announced system or an iOS store release is finished.

Maps and models are only part of the job. In M2Dev's Rewritten GR2 engine thread, Koray describes a Rust reimplementation of the model/animation engine and later mobile/browser compatibility work. This is an example of a component that can support a broader client effort. It should not be mistaken for a complete mobile game simply because its preview renders a character.

Cemre's October Android-port write-up gives a concrete example of a less visible problem: an inventory feature setting changed where the client expected equipment slots, so an equipped item could appear on the character while being absent from the equipment panel. Client and server had to agree on the layout before changing the window would help.

The same write-up separates build targets from tested devices: it describes ARM64 and x86_64 builds, but says its runtime evidence is mainly from an x86_64 Android emulator and that physical ARM64 validation still remains. An emulator session and a long session on a real phone answer different questions.

For an established private server, the attractive promise is keeping your character while moving between PC and phone. Achieving that requires the new client to match that server's packet formats, feature set and account/world setup. The engine name does not establish those things. A client can render familiar Metin2 assets and still disagree with the server about an inventory slot or a character-selection packet.

The operator's Rohan2 Mobile announcement on elitepvpers illustrates why the realm name matters. The relevant 16 October 2026 announcement is inside an older thread and describes a Mobile (S2) world, with changes for existing worlds discussed separately. That wording does not establish that a character from an older realm automatically carries over to the new one.

There are earlier-stage server projects too. Lupus2's developer first-look on the Romanian M2Forum describes native phone-client development and a PC/mobile shared-world goal, while explicitly saying it is early development and has no launch date. These are useful projects to follow, without treating their goals as a finished service.

The milestone to watch next is sustained play through ordinary game activities: changing maps, using items, talking to other players and reconnecting after the phone is interrupted. These are proposed checks for future testing, not tests completed for this article. They say more about a usable mobile client than a single clean login screen.

For players, this development could make existing worlds accessible away from a Windows PC. The result will depend on the particular implementation: touch controls, small-screen windows and the server's own systems all have to work together. Use the Metin2 private-server directory to find the project's primary website, then follow its mobile development thread and exact realm announcement.

The links above lead to the developers' own posts or product pages, rather than a generic mobile APK list. For updates, start with the Turkmmo BGFX/FGR2 diary, Andro2, M2Dev Unity experiment, M2Dev GR2 engine work, Alesta2 presentation, Cynex Mobile, Rohan2's operator thread on elitepvpers and Lupus2 on M2Forum. The Android-port case study provides additional technical detail.

Source state checked on 24 October 2026. These links document different projects and different milestones; they are not a ranking, a security certification or a claim that a universal mobile client exists for all Metin2 private servers.