In short: Queue mode lines up the next Metins while the current one is still being fought and then works through them in order, instead of searching again after every stone. On dense maps that yields the most stones per hour. Whether a session then actually runs long is decided by the settings around it: speed, breaks, fatigue and the safety features.
In this article
How queue mode works
The cycle consists of four steps that repeat constantly:
- Walk to the first stone. The bot clicks the nearest detected Metin and waits until its health bar appears. Only then does the stone count as accepted.
- Line up more while fighting. During combat the bot clicks the other detected stones and queues them. That time would otherwise go unused.
- Stone down, next one up. When the stone falls, the bot takes the next one from the queue. Walking there is handled by the game itself.
- Queue empty, new search. Once the queue is done, the bot starts a fresh search on the current image.
The gain sits in step 2. In normal mode the bot stands still after every stone and only then keeps looking. In queue mode that pause disappears.
When queue beats normal
Queue mode lives on several stones being visible at once. That gives a simple rule:
- Dense map, many stones on screen: queue mode. This is where it pulls ahead.
- Stones spread far apart: normal mode. If only one stone is ever visible, there is nothing to line up.
- First setup: always normal mode. You immediately see whether detection runs cleanly, without several mechanics interacting at once.
Speed, breaks, fatigue
Three settings determine how the bot behaves over time. They belong together and should be thought of together.
Speed profile
Four levels set how long the bot waits between two actions. Safe is slow and unremarkable and meant for continuous operation, Normal is the middle ground, Turbo is fast with a higher risk of standing out, and Ultra Fast runs the maximum scan rate with minimal waiting between windows. For a night session, Safe or Normal is the sensible choice.
Breaks
With breaks active, the bot stops every 400 to 600 stones for 3 to 8 minutes. Both values are drawn at random. That is the whole point: a break every exactly 500 stones would itself be a pattern.
Fatigue
Fatigue simulation slows the bot down the longer it runs. Each strength level adds 7 percent per hour, so strength 3 is roughly 21 percent. It stops at 70 percent, otherwise the bot would eventually grind to a halt. Click intervals, search intervals and window-switch timing are all affected.
Why these belong together
Turbo plus breaks off plus no fatigue produces a character that clicks in exactly the same rhythm for twelve hours. No scanner notices that, but every player who walks past twice does.
What saves the night
A long session rarely ends because of detection. It ends because of small things:
- PM alert. When a private message arrives, the bot stops and waits for you to confirm with ENTER. The PM icon has to be captured once for this.
- Player radar. You capture the colour of your own dot on the minimap. If another player shows up there, the bot pauses until the radar is clear again.
- Kill-steal protection. The bot only attacks stones at full health, so it never takes a stone someone else is already fighting. For that you capture the full HP bar.
- Auto-revive. Without it, the character lies dead from the first death until morning.
These four belong to the premium version. The free version is meant for trying out the detection and runs 60 minutes once, then 10 minutes per program start.
A setup to start with
If you do not want to experiment for long, this combination usually works well on a private server:
- Speed Safe or Normal
- Breaks on, fatigue on at strength 2 to 3
- PM alert, radar, kill-steal protection and auto-revive on
- Only switch on queue mode once detection runs cleanly in normal mode
How the detection works at all is covered in How BeaTzVision Works Internally. Step-by-step setup is in the farmbot guide. And if nothing is detected, the troubleshooting guide helps.
Frequently asked questions
What is the difference between normal and queue mode?
In normal mode the bot searches again after every stone. In queue mode it already lines up the next stones while fighting and then works through them in order. On dense maps that noticeably increases stones per hour.
How often does the bot take breaks?
With breaks enabled it stops every 400 to 600 stones for a random 3 to 8 minutes. Both values are rolled randomly so that no fixed pattern appears.
What does fatigue simulation do?
The bot gets slower every hour, like a human. At strength 3 that is roughly 21 percent per hour, capped at 70 percent. It affects click intervals, search intervals and the timing of window switches.
Can the bot run overnight?
Technically yes. Whether it survives the night comes down to three things: inventory, death and interruptions. Auto-revive, PM alert and radar cover the rest. All three are premium features.
Ready to try it yourself?
Join the BeaTzTools Discord and get access to BeaTzVision and BeaTzSignal, setup guides and support.
Try it free →