In short: A macro repeats a fixed sequence of clicks and key presses. It does not react to what happens on screen. When farming, that is exactly the sticking point: Metin stones never stand in the same place twice. A pixel bot looks for the target first and then clicks where it actually is.
In this article
What a macro does
AutoHotkey and similar tools play back a list of instructions: mouse to position X and Y, click, wait 800 milliseconds, press a key, start over. The tool is powerful, but it is blind. It does not know what is currently visible in the game.
As long as the world does not change, that is perfectly sufficient. Topping up a potion every two minutes, opening a window, pressing a button that always sits in the same spot — nobody needs image recognition for that.
Where it fails at farming
Farming is the opposite of a fixed world. Four things break every macro:
- The position is never right. Stones spawn in changing places, and your character never stands exactly the same. A fixed click point therefore almost always hits nothing.
- The duration is never right. How long a stone holds depends on gear, buffs and level. A macro that blindly waits 20 seconds either wastes time or aborts the fight.
- It notices nothing. Another player is already fighting your stone, a private message arrives, you die — the macro keeps clicking.
- Map changes end it. After every change the situation is new, the script is not.
In practice this ends in scripts with more and more special cases that still only work on one map and with one character.
What image recognition adds
A pixel bot reverses the order: look first, then act. BeaTzVision searches the image for the stone you captured, clicks it where it currently stands, and waits for the health bar before the stone counts as accepted. How that works technically is covered in How BeaTzVision Works Internally.
That enables things a macro cannot do by design:
- Pick the nearest target instead of clicking a fixed point
- Wait for a state, namely the health bar, instead of a stopwatch
- Skip stones someone is already fighting, because the bar is not full
- Stop on a private message and pause when a player shows up on the radar
- Line up more stones while the current fight is still running
Direct comparison
| Macro (e.g. AutoHotkey) | BeaTzVision | |
|---|---|---|
| Basic principle | replay a fixed sequence | analyse the image, then act |
| Finding a target | no, fixed click point | yes, via image recognition |
| Waiting for a state | waiting time only | the stone's health bar |
| Avoiding kill-steal | no | only stones at full health |
| Reacting to messages | no | PM alert stops it |
| Several windows | only with your own effort | up to two (premium) |
| Effort for you | write and maintain a script | capture stones, set the threshold |
| Cost | free | free version, premium for the rest |
What does not make a macro worse
One point belongs here even though it does not fit a sales pitch: a macro is technically no more conspicuous than a pixel bot. Neither reads memory, hooks into the game process or modifies a file. Both simulate perfectly ordinary input.
So the difference is not invisibility, it is capability. And there is a second point: a macro that stubbornly clicks the same spot every 800 milliseconds behaves more mechanically than a bot with random breaks and fatigue simulation. In game you stand out through behaviour, not through software. More on that in Metin2 Bot Without Ban.
And for both: using them generally violates the terms of service of the respective server.
The simple rule
If it always happens in the same place, a macro is enough. If the position changes, you need image recognition. When farming stones, it always changes.
Frequently asked questions
Can I build a Metin2 farmbot with AutoHotkey?
For fixed sequences yes: pressing a key on a timer, clicking a button that never moves. The moment the target changes position, it ends. A macro does not know where the stone is, and it does not know when the stone is destroyed.
Is a macro safer than a bot?
Technically there is little between them: neither a macro nor a pixel bot reads memory or hooks into the game process. Both simulate input. The difference is capability, not invisibility. And both generally violate the server's terms of service.
What is a macro genuinely good for?
Anything that always happens in the same place: topping up potions, opening a window, pressing a key on a fixed rhythm. None of that needs image recognition.
Ready to try it yourself?
Join the BeaTzTools Discord and get access to BeaTzVision and BeaTzSignal, setup guides and support.
Try it free →