In-Game Autopatcher

[Froslass 905]

It's an autopatcher that works directly inside your game client:

• It doesn't require players to start the game from a different .exe
• The ui is made in a .py like any other metin2 system so anybody can easily modify it

Video:

Spoiler

 

 

This is the hidden content, please

• Sign In
• or
• Sign Up

This is the hidden content, please

• Sign In
• or
• Sign Up

Alternative download links →

This is the hidden content, please

• Sign In
• or
• Sign Up

 

[Anielle Noir 144]

Slow clap.

Open the entire game client, initialize the window and processes, check and download the update, close the game, launch an external executable to install it, then reopen the game again.

What a fucking achievement.

It is like starting your car, driving out of the garage to check whether it needs fuel, turning it off, pushing it to the petrol station, and then starting it again.

An external helper for replacing loaded files is understandable. Launching the entire client first and advertising this loop as an “in-game autopatcher” is not.

I would honestly be ashamed to come up with this workflow, start coding it, and still think: “Yes, this is a good user experience.

AAAND, The best part is the initial installation logic.

A new player cannot use this “in-game patcher” without first downloading enough of the full client to initialize the game. So the owner must either distribute a multi-gigabyte, potentially outdated client archive and make the player patch it afterward, or distribute a normal external patcher, which already makes this entire launch → check → close → external patch → relaunch circus redundant.

A small external bootstrapper could simply download the latest client and launch it once.

This "system" is like mailing someone an outdated refrigerator so its built-in screen can tell them to call a delivery company for the current refrigerator.

Edited August 2 by Anielle Noir

[maniacwarframe 0]

5 hours ago, Anielle Noir said:

Slow clap.

Open the entire game client, initialize the window and processes, check and download the update, close the game, launch an external executable to install it, then reopen the game again.

What a fucking achievement.

It is like starting your car, driving out of the garage to check whether it needs fuel, turning it off, pushing it to the petrol station, and then starting it again.

An external helper for replacing loaded files is understandable. Launching the entire client first and advertising this loop as an “in-game autopatcher” is not.

I would honestly be ashamed to come up with this workflow, start coding it, and still think: “Yes, this is a good user experience.

AAAND, The best part is the initial installation logic.

A new player cannot use this “in-game patcher” without first downloading enough of the full client to initialize the game. So the owner must either distribute a multi-gigabyte, potentially outdated client archive and make the player patch it afterward, or distribute a normal external patcher, which already makes this entire launch → check → close → external patch → relaunch circus redundant.

A small external bootstrapper could simply download the latest client and launch it once.

This "system" is like mailing someone an outdated refrigerator so its built-in screen can tell them to call a delivery company for the current refrigerator.

Edited August 3 by Metin2 Dev International
Core X - External 2 Internal

[Froslass 905]

14 hours ago, Anielle Noir said:

Slow clap.

Open the entire game client, initialize the window and processes, check and download the update, close the game, launch an external executable to install it, then reopen the game again.

What a fucking achievement.

It is like starting your car, driving out of the garage to check whether it needs fuel, turning it off, pushing it to the petrol station, and then starting it again.

An external helper for replacing loaded files is understandable. Launching the entire client first and advertising this loop as an “in-game autopatcher” is not.

I would honestly be ashamed to come up with this workflow, start coding it, and still think: “Yes, this is a good user experience.

AAAND, The best part is the initial installation logic.

A new player cannot use this “in-game patcher” without first downloading enough of the full client to initialize the game. So the owner must either distribute a multi-gigabyte, potentially outdated client archive and make the player patch it afterward, or distribute a normal external patcher, which already makes this entire launch → check → close → external patch → relaunch circus redundant.

A small external bootstrapper could simply download the latest client and launch it once.

This "system" is like mailing someone an outdated refrigerator so its built-in screen can tell them to call a delivery company for the current refrigerator.

That's literally industry standard dummy.. If you open apps like discord or steam you will notice there will be 2 icons in your taskbar, one is the application, the other is the patcher, you just don't notice it because they have the same icon.

An executable CANNOT replace itself while it's running so a patcher must do the work, there are no exceptions in the world to this.

Metin was literally the only app in 2026 that required players to launch the autopatcher instead of directly opening the game and then it does all the work itself.

And yes opening the game once and then it updates itself and re-open itself when done is literally the best user experience you can have, that's why it became industry standard. I don't know how you can think having 2 launchers in your client folder, one to open the game and one to update it, could be a better user experience.

Lastly but not least, that's a free system, if you are one of those people that don't understand how modern workflow works and would rather keep living in 2004 just don't use it, why would you be mad about a free release 

[friendtm 4]

On 8/3/2026 at 12:43 PM, Froslass said:

That's literally industry standard dummy.. If you open apps like discord or steam you will notice there will be 2 icons in your taskbar, one is the application, the other is the patcher, you just don't notice it because they have the same icon.

An executable CANNOT replace itself while it's running so a patcher must do the work, there are no exceptions in the world to this.

Metin was literally the only app in 2026 that required players to launch the autopatcher instead of directly opening the game and then it does all the work itself.

And yes opening the game once and then it updates itself and re-open itself when done is literally the best user experience you can have, that's why it became industry standard. I don't know how you can think having 2 launchers in your client folder, one to open the game and one to update it, could be a better user experience.

Lastly but not least, that's a free system, if you are one of those people that don't understand how modern workflow works and would rather keep living in 2004 just don't use it, why would you be mad about a free release 

Not true. You have a lot of games developed in these recent years that still use this flow. Black Desert, Arena Breakout, other free games where you usually need to login first before the game launches, usually they check the game for updates outside of the client. So, no, Metin2 is not the only app doing it. Talking about this feature, i actually don't see a benefit, its just different. If you want to make your metin2 different, yes, but this does not make it better. Actually, the autopatcher is a faster flow then this one. The only benefit of this, is if you are able to bypass the autopatcher. In that case, the ingame check would force you to close the client and update. Other than that i don't see a benefit.

Anyway, good thing, its the first time i see this implemented.

[CONTROL 939]

The idea of having an in-game patcher isn't bad at all, it's actually brilliant

The only bad part is that he didn't use it the way modern games/apps do

Modern games can handle missing textures, models, etc. properly, so they can still run without having every single asset downloaded

With Metin2 though, missing assets can easily lead to undefined behavior or even crashes

But still, you can simply prioritize your packs dynamicly with each update

root -> true
high priority, so it gets downloaded first & you can't log in without it.

icon -> false
can be downloaded while you're playing. Worst-case scenario, you just get a missing icon, which will be replaced once the download finishes anyway.

You could also just ask the player to restart the game once everything is downloaded.