In short: A pixel bot only sees the image. If it detects nothing, the image has almost always changed: resolution, graphics settings, window mode or Windows scaling. If it detects but does not click, the rights are missing. If it finds stones where there are none, the threshold is too low. Work through the points from top to bottom instead of turning several dials at once.
In this article
First: the live preview
Before you change anything, open the live preview. It shows exactly the image the bot works with, draws boxes around detected stones and prints the match score. That value between 0 and 1 is the single most useful clue:
- No box, no score: the bot does not see the stone at all. Continue at "Nothing is detected at all".
- Box with a score just below your threshold: the capture is fine in principle, the threshold is simply too strict.
- Boxes in places without a stone: the threshold is too loose, or the template contains too much background.
Without that look you are guessing. With it you know within thirty seconds which way to turn.
Nothing is detected at all
The bot only photographs the area of your game window. Anything that changes that image breaks detection:
- Exclusive fullscreen. On some graphics drivers this produces a black image. Switch to windowed or borderless windowed.
- Resolution changed. Every change invalidates your captures, because the stone now has a different size.
- Windows scaling. At 125 or 150 percent the window is captured differently from how it looks to you. 100 percent is the safe setting.
- Graphics settings or gamma. The contrast equalisation inside the bot absorbs part of the brightness differences, but not every gamma change.
- Wrong window assigned. In multi-client this happens quickly when both windows share a title. Start them one after another and assign each right after launch.
- Switched servers. Different Metin models mean different captures. Templates are stored per server.
The tip that saves the most
Write down resolution, window mode and graphics settings as soon as detection runs cleanly. If nothing works weeks later, almost always exactly one of those values has changed.
Detection works but nothing is clicked
This is the clearest case of all: the bot detects cleanly, but nothing happens in game. Then it is about rights. If the game runs with administrator rights and the bot does not, Windows blocks input into that window. Start both with the same rights.
Less often, focus is to blame: if another window is in the foreground, a key press lands there instead of in the game. In dual-client the bot brings the right window to the front itself.
Matches in the wrong places
When boxes appear all over the screen, there are two causes:
- Threshold too low. Raise it in small steps and watch the preview.
- Too much background in the template. If you captured grass, water or a piece of terrain along with the stone, the bot finds exactly that pattern everywhere. Crop tighter.
For areas that keep producing false matches, such as chat or minimap, use a mask. The bot paints that area black before it searches.
Stones get missed
The opposite, and the more common case:
- Threshold too high. Lower it in small steps.
- Template cropped too tightly. If the characteristic element is only partly included, the score stays low permanently.
- Auto-zoom off. With it active, the bot tries nine sizes between 0.8 and 1.2 and finds the stone from other distances too. Without it, only the original size counts.
- Only one variant captured. Two or three captures of the same stone in different situations absorb differences in lighting and effects.
All symptoms at a glance
| Symptom | Likely cause | Fix |
|---|---|---|
| Black image in the preview | Exclusive fullscreen | Windowed mode |
| No matches at all | Resolution or scaling changed | 100 % scaling, re-capture templates |
| Detection yes, click no | Game as admin, bot not | Start both the same way |
| Matches everywhere | Threshold too low, too much background | Raise threshold, crop tighter, mask |
| Stones get missed | Threshold too high or template too tight | Lower threshold, auto-zoom on |
| Gone after a map change | Background in the template | Re-capture on neutral ground |
| Clicks your own character | Exclusion zone too small | Enlarge the zone |
| Nothing after switching servers | Different Metin models | Capture templates for that server |
If it persists, Discord support usually helps within minutes. The fastest way is a screenshot of the live preview, because the match score is visible on it. How detection works technically is covered in How BeaTzVision Works Internally, and the complete setup is in the farmbot guide.
Frequently asked questions
The bot suddenly detects nothing although it worked yesterday
Then the image has almost always changed: a different resolution, different graphics settings, a server patch or another window mode. Re-capture the stones and check that Windows scaling is back at 100 percent.
Detection shows matches but the bot does not click
Then the rights are missing. If the game runs as administrator, BeaTzVision has to run as administrator too, otherwise Windows does not allow input into that window. The bot detects everything correctly, nothing simply happens.
The bot finds stones where there are none
The threshold is too low, or the captured image contains too much background. Raise the threshold in small steps and put a mask over areas such as chat or minimap.
Do I have to re-capture everything after switching servers?
Yes. Every server has its own Metin models and its own interface. BeaTzVision keeps captures separate per server, so you lose nothing when you switch back.
Ready to try it yourself?
Join the BeaTzTools Discord and get access to BeaTzVision and BeaTzSignal, setup guides and support.
Try it free →