MC AFK user guide

Follow Server → Bots → Panel → Chat to make your first connection. RehberBot and 10.0.2.2 in the screenshots are local capture data only; use your own server address.

1. Install the Android app from the download page. For Windows, use the separate Windows section below.
2. Save the address in Server; use Bots → Add First Bot to select your account and edition.
3. In Panel, enable the top service switch and the bot’s switch. Check for “Bot connected” in Chat.

If it will not connect, check the address/port, the bot’s actual edition and Microsoft requirements first. Avoid rapid repeated connection attempts.

A server profile saves its address and version selection. Java/Bedrock in the Server screen controls status queries; select the connecting bot’s edition separately in Bots.

1. Server → Add Server at the top right. Give the profile a recognizable name.
2. Enter only a domain or IP in Server IP / Host, without http:// or https://. Use the server’s port; otherwise follow the edition-specific field help.
3. Auto is recommended for Minecraft Version. Save and select the default server from the list. A bot with a custom address does not use this default.

Changing the version number does not solve every connection issue. The supported server version and the bot’s Java/Bedrock edition must match.

Microsoft authentication and a server’s /login password are different. Bedrock uses Microsoft. Offline Java accounts only work on servers allowing player-name sign-in.

1. Bots → Add New Bot, or select an existing bot → Edition: Java / Bedrock. Do not skip this because of the server profile’s edition.
2. For Java, choose the appropriate Sign-in Type. If Microsoft is required, complete the official flow opened by “Sign in to Microsoft account”. Never enter your Microsoft password in Account Login Password.
3. Choose an avatar and enter the player name for an offline account. Scroll to the bottom and finish using Create Character or the save action.

Complete Microsoft authentication first if unfinished. Using the same account in another client may disconnect it under the server’s session rules.

Panel combines the service, individual bot switches and the extra-bot time pool. An enabled switch requests a connection; confirm the actual connection in Chat.

1. Enable the top service switch in Panel, then enable each bot you want to run.
2. Read connected, connecting or error status on the bot card. Use Chat to view that bot’s messages.
3. Open bot settings from Bots; configure Auto Reconnect and its delay if needed, then save. Disable the bot switch to stop one bot or the service switch to stop them all.

Read the last chat message instead of repeatedly toggling a failed connection. Disable Low Power Mode in bot settings if it causes disconnects on that server.

This sends the Minecraft server’s own login/register commands. Do not use your Microsoft password here. The {password} placeholder is filled from this bot’s Account Login Password.

1. Bots → bot → enter only the password for this server in Account Login Password.
2. Enable Automatic Login (/login) and keep the template in the format required by the server: /login {password}. If registration is required, check Automatic Register and /register {password} {password}.
3. Save at the bottom; after reconnecting, read the login result in Chat. Use Slow Login Commands on slower servers.

Sonar compatibility is experimental and limited to Java 26.1 / Sonar 2.1.x; it is not a general solution for Java 26.3 or Bedrock. Complete CAPTCHA and /verify codes yourself. Never share your password in a support screenshot.

Authentication must finish first. Transfer Method uses a command or the server’s GUI. Check server-specific commands, items and menu layout in the normal game client.

1. Command: enter the server’s transfer command, for example /skyblock only if that server supports it. An empty field sends no command.
2. Menu / GUI: set Held Selector Item (Hotbar 1–9) to the item that opens the menu. Use 1 for a compass in the first hotbar slot, or leave it blank if the menu opens automatically.
3. Target Menu Slot counts from 1 at the top left, including empty slots. In nine columns, 12 is row two, column three. It is not a hotbar number. For successive menus use 12,14 or an appropriate item-name filter.
4. If needed on Java, enable Second Menu. Select Automatic Menu, Hotbar Item or Command and its target slot/item name for the menu opened after the first transfer is confirmed. Save.

If the menu opens but transfer fails, check the real slot/item name. Second Menu is off by default. A transfer-failed message means subsequent steps have not completed.

Select the correct bot in Chat first. The quick-tools row scrolls horizontally; it contains more than the first four visible buttons.

1. Select the bot’s name at the top and send a message from the chat/command field. Start commands with /.
2. Tap clickable TP/trade accept or decline text received from the server. This executes only the actual action sent by the server. Use chat search to find this bot’s messages.
3. Scroll the tool row sideways to Players, Bulk Command and Sidebar. Select target bots carefully for bulk commands; do not broadcast a personal /login password.

Controls may be disabled while disconnected. Seeing Accept/Decline does not prove completion; check the resulting GUI or server response.

Main Inventory, Hotbar and an open server menu are separate areas. Seeing an item icon is not the same as the server confirming a move.

1. Chat → Inventory. Tap a slot to open Item Details and Interactions.
2. Choose the displayed left/right click, move or hotbar action appropriate to your goal. Count GUI slots from 1 at the top left; hotbar 1–9 is separate.
3. After acting, refresh or wait for new inventory data. Open a menu via Chat → Menu or by using the correct hotbar item.

Protected or custom menus may reject clicks under server rules. If an item did not move, check the connection and active menu before repeating the action.

A server map/verification image is different from the live minimap in Movement. Sidebar is server scoreboard data, not inventory GUI. A Bedrock form opens only when a Bedrock server sends one.

1. Scroll Chat’s tools sideways and open Map to view a server-sent map. “No map data yet” means none has been received.
2. Use Sidebar to read server-sent crystal/balance values and close it with ×. Values in this screenshot are local examples, not a real server balance.
3. For Bedrock, fill in and submit a received form, or close it using the top ×. The user supplies answers to map/form verification.

An empty panel may mean that the server does not send that feature. There is no anti-bot/CAPTCHA bypass guarantee. Bedrock Microsoft authentication was not performed during these captures.

Movement provides manual direction and held-item controls. Its live minimap uses world data received by the bot, not knowledge of the whole unseen world.

1. Chat → Movement. Check coordinates and direction. Make small, safe movements with Forward/Back/Left/Right.
2. Adjust the view using Turn Left / Turn Right; use Jump or Sneak when needed.
3. Left Click (Hit) is a single interaction. For continuous block breaking use Tasks → Mine in Looking Direction. Right Click (Use) uses the appropriate held item.

An empty minimap or reversed movement may be due to missing chunks or server restrictions. Do not start automation near drops, lava or protected areas.

Tasks separates saved jobs from configuration. Selecting a preset or saving a task does not start it automatically. The tabs scroll horizontally.

1. Chat → Tasks. Choose Patrol, Mine, Mine in Looking Direction, Fish or Collect and follow the task-specific instructions below.
2. Review safety, chest, full-inventory, work/break and reconnection settings. Approve block breaking only on a server where it is allowed.
3. To reuse it: Save Task → name → Save. To run it, use the bottom action/“Start as new task”, then review and approve its summary and permissions. Run saved tasks from the Tasks list.
4. Monitor active-task status and Task Results. Cancel using Stop; do not restart a safe-stopped task before correcting its cause.

A wrong dimension, missing tool, inaccessible target, protection, full inventory or invalid schedule may stop a task. Read the reported reason. These screenshots show configuration, not proof of success on every server.

Link a chest rule to deposit products when inventory fills and return to work. Transfer only selected products; do not accidentally include tools, rods, food or valuables.

1. Tasks → Chest → Find Nearby Chests. Check the coordinates before choosing Target Chest.
2. Select products in Items to Transfer. Select All may include every item, so inspect the list. Enable Continuous Transfer for full-inventory deposits and complete the required confirmation.
3. Return to mining/fishing and confirm the chest rule is linked. Configure low health, damage, allowed area and nearby-player safety rules.
4. If you need replacement tools, enable Take Spare Pickaxe from Chest, select the product chest or a separate supply chest and allowed pickaxe types. It takes one tool and returns; it does not discard the old tool.

Chest space, inventory space, correct filters, permission and an accessible path are required. Nearby-player safe-stop/notification settings also appear in Bots → bot → Notifications.

These tasks consume materials. Read the real input/output summary before approving; opening the form does not execute it. Special or enchanted items are not treated as ordinary crafting ingredients.

1. Scroll the Tasks tabs sideways to Craft, Furnace, Harvest or Trade. Enter the task-specific targets and limits below.
2. Prepare materials in the bot’s inventory. Ensure the required crafting table, furnace, crop area or villager is reachable and permitted.
3. Preview the recipe/summary to check consumption, approve safety and quantity limits, then start. Monitor status; check inventory before repeating an uncertain result.

Missing materials, wrong coordinates, full output space, protected items or server rejection can cause a safe stop. Resolve the cause before restarting.

Choose deliberately: stop, deposit in an approved chest or continue without a chest. Chestless work is possible, but you accept the risk of lost products.

1. In Mine, Mine in Looking Direction or Fish, locate “Continue working when inventory is full”.
2. Leave it off and configure an approved Chest transfer to preserve products. Without a chest, the task stops when inventory fills.
3. Enable it for continuous chestless work, then check the saved/start summary. Uncollected drops may remain on the ground and despawn.

This does not disable server protection, unbreakable blocks or task safety. Use chest deposits if you do not want item loss.

Settings at the top right includes language, theme, chat timestamps, resource packs and help. Notification rules are in bot settings; Android notification permission is in phone settings.

1. Top-right Settings → Language changes app language; Theme selects System/Dark/Light. Enable chat timestamps if desired.
2. Use Resource Packs → Open or the pack card in Inventory → Download (detected version). With Auto, the version is taken from the real connection. Wait for download/icon preparation to finish.
3. Use Load Your Pack for a suitable ZIP containing item/block PNG textures. In Bots → bot → Notifications, configure disconnect, low-health and Java nearby-player/private-message rules, then save.

If downloading fails, check the network and detected version; use a trusted pack. If notifications do not appear, check Android permission too. Help and Feedback includes diagnostic options.

While enabled, the service attempts to maintain connections in the background. Android power management, network changes and server rules may interrupt them; uninterrupted operation is not guaranteed.

1. Confirm the service and bot are enabled and actually connected in Panel. Allow Android notifications for MC AFK and check the service notification.
2. Check whether MC AFK’s background activity is restricted in phone app/battery settings. Option names vary by manufacturer; you do not need to disable all device battery protection.
3. Check Auto Reconnect and a reasonable delay in bot settings. If the server disconnects idle clients with Low Power Mode enabled, compare with that option disabled.
4. Background the app and later check Panel/Chat status. For support, share phone model, Android version, bot edition and the last disconnect message, but never passwords/tokens.

Force-stopping the app stops its service too. “Timed out” may indicate network/server issues, not automatically a version error. The official Android Doze/App Standby explanation is linked below.

The first two bots are free. Ad-funded extra bots share a pool; each bot does not receive its own 24 hours. Only extra bots actually connected consume pooled time.

1. Panel → Extra-Bot Time Pool. Read remaining time and consumption status. If a purchase benefit applies, use the current package terms shown in the app.
2. The first completed rewarded ad adds 24 hours; subsequent completed ads add 12 hours. Opening an ad or closing it early does not earn a reward.
3. Each connected extra bot consumes one pool hour per hour. If the third and fourth bots both stay connected for one hour, two pool hours are used. Stopped/disconnected extra bots consume none; the first two are excluded.

If an ad is unavailable, check the connection, use Retry on screen or return later. Do not confuse bot-ad removal with removal of all ads; read the purchase screen’s scope.