Account and server profile
The account connection and the server configuration are kept separate. This lets the platform show an actionable diagnostic — wrong version, missing proxy, AuthMe required — instead of hiding a failed connection behind a single generic status.
Worker and session states
A worker receives an allowed task, attempts the connection, and reports the result. Requested, assigned, connecting, online, and failed are distinct states, and the panel shows which one you are in rather than collapsing them into “on” or “off”.
Why diagnostics matter
Version mismatch, proxy requirements, AuthMe, resource packs, and manual verification are different technical conditions with different fixes. A safe system reports the specific one it hit instead of pretending every server works.
What you see when something breaks
When a session drops, the system records the stage it failed at and the last known good state. That history is what turns a vague “bot offline” into a specific, repeatable troubleshooting step.
Related pages
Minecraft AFK compatibility data, with its limits explained
Read AFKBase’s anonymized technical compatibility summaries and their limitations before testing your own Minecraft server setup.
AFKBASEMinecraft AFK bots: manage a permitted connection, not a bypass
Understand what a Minecraft AFK bot is, how a permitted session is managed, and why server rules and technical compatibility come first.
AFKBASEMinecraft AFK 24/7: understand the trade-offs first
Compare practical ways to keep a Minecraft account online for long periods without leaving your own computer running.
The Turkish page is the canonical source for legal, payment, and service terms. Turkish source.