Thirty questions, answered before they become blockers.

Create or sign in to your account, claim your permanent public name, start the one-time trial or submit an access request, choose an available desktop platform, download the protected client, pair that device, then review the local route and safety settings before arming automation.

Yes. Your access, software bundle, download grants, paired devices, scripts, and support cases are account-scoped. Sign in happens in your browser; the desktop app never asks you to type website credentials into the app.

It gives your account a safe customer-facing identity for trials and Creator route packs without exposing a provider subject. Names are 3–24 safe characters, unique without regard to letter case, preserve your chosen casing, and cannot be renamed after the server commits the claim.

An eligible account can claim one seven-day, machine-bound trial. It has one device slot and binds permanently to the first machine you pair, so another account or a different spelling of the same device key cannot create a second trial.

The seven days start when you claim the trial, not when you finish pairing. Pairing later does not restart or extend it, so choose your public name, download platform, and first machine before claiming when practical.

Arrange payment with the operator off-site, then submit the selected plan, duration, and payment reference in Access. The request creates no entitlement by itself. Access begins only after the operator verifies it and records an audited acceptance reason; an open request can be updated while it waits.

Player is the USD 10/month reference plan for personal use. It includes the same local engine, stable releases, public or directly shared route-pack downloads, one desktop slot, and one mobile slot when a mobile product is published. The account still runs only one app process at a time.

Creator is the USD 20/month reference plan. It adds a second desktop slot, beta releases, priority support, and the ability to create, upload, publish, share, version, and revoke route packs. It does not add a second simultaneous app process.

Use Player when you operate Minibot for your own sessions on one desktop. Choose Creator when you need a second registered desktop, beta access, priority support, or route-pack distribution tools. Use the one-time trial first when you are eligible and only need to evaluate the product.

The desktop bundle understands Windows, Linux, and macOS. A mobile choice is offered only when the private release catalog contains a published mobile artifact. Any platform marked Coming soon has no production download and cannot be selected as if it were released.

The lock binds downloads and device authorization to the exact platform covered by the current access grant. Choose the desktop platform you will actually pair; add mobile only when the dashboard offers a released option. Repeating the exact choice is harmless, while a different switch is rejected without creating a download or device record.

No. Player may register one desktop and one mobile device; Creator may register two desktops and one mobile device; a trial has one machine-bound slot. Those are registration limits. Every plan permits only one active Minibot app process per account at a time.

Use Dashboard → Downloads after access is active and your desktop platform is locked. The public Downloads page shows availability, but only the authenticated dashboard can issue the private release grant for your account and selected platform.

Production artifacts stay private. A permitted download receives a short-lived, one-use grant bound to current identity, entitlement, device, release, and object metadata. An expired, reused, revoked, foreign-account, or mismatched grant fails closed.

Every production artifact is signed over its exact kind, version, channel, platform, architecture, object identity, byte size, and SHA-256 hash. The client verifies that identity, signature, size, and checksum and rejects redirects, downgrades, truncation, or altered bytes before staging an update.

Start pairing in the desktop app, open its short-lived link or code in Dashboard → Devices, and compare the displayed device name, platform, architecture, and abbreviated public-key fingerprint. Approve only when the browser preview exactly matches the app in front of you.

Return to the desktop app and create a fresh pairing request. Unknown, malformed, expired, consumed, denied, or incomplete requests never expose an approval control, and retrying with stale data cannot authorize a device.

Revoke the old device from Dashboard → Devices, then pair the replacement within your plan capacity and locked platform. Revocation invalidates that device's credentials. A trial remains bound to its first machine and cannot be transferred to a replacement.

Inside the installed Minibot app on your machine. Healing, targeting, walking, combat, inventory, route, and team decisions stay in the local realtime path instead of waiting on a website round trip.

It owns identity, access decisions, platform selection, paired-device authorization, runtime leases, signed release metadata, private download grants, route-pack distribution, and support. It never hosts a gameplay runtime, remote bot session, or command stream.

No. Minibot is automation built for the live Minibia client. You provide and control your own game installation, account, character sessions, network connection, and in-game decisions; the Minibot subscription covers only the Minibot product.

Confirm access and pairing, import or record the intended route, inspect its transitions and recovery waypoints, then review healing, targeting, supplies, capacity, alarms, protector actions, and team roles. Arm automation only when the selected character and operator state are unambiguous.

No. Realtime decisions are local, but a current server-issued runtime lease is still mandatory and there is no offline gameplay grace. A network problem may retry outside the fast loop, but it cannot extend expired authority. The app window and local configuration remain available when automation cannot arm.

The local engine fingerprints the visible tiles against its owned offline brain. A trusted, unambiguous match may be submitted locally. An unknown or ambiguous set raises a critical repeating alarm, blocks ordinary hunting actions, and requires the operator instead of guessing.

It is a versioned, validation-first package for route-owned behavior such as waypoints, targeting, sustain, loot, refill, banking, alarms, team settings, notes, and compatibility metadata. Imports show a scoped preview before Apply and exclude credentials, runtime leases, active pauses, and character-private ledgers.

Yes. An entitled Player can browse and download published public packs and packs shared directly with that account for personal use. The package is integrity-checked and registered by the local engine; the Website stores and distributes it but never executes it.

An active Creator can upload a validated draft from the Website or a paired desktop, create immutable versions, publish publicly or share with named accounts, and revoke access or a version. Recipients receive expiring, integrity-bound downloads carrying the Creator's permanent public name.

The app first performs a read-only metadata check. Update now explicitly requests a one-use download, verifies the pinned signing key, full artifact identity, size, and SHA-256, rejects downgrades or redirects, and stages bytes atomically. Installation is refused while a bot or kill moment is active.

New engine starts, runtime authorization, protected downloads, and new device authorization stop. The desktop window still opens so you can see the access state and keep local configuration. Submit a new operator-reviewed access request when you need to restore authorization.

Use authenticated Dashboard → Support and name the affected device or release, what you expected, and what happened. Attach only the bounded safe diagnostic categories the portal offers. Never send passwords, cookies, tokens, private keys, recovery phrases, browser profiles, or unrestricted raw logs.