Getting Started
Boto starts unarmed. Prepare your queue, review the sidebar, then choose Arm when you are ready.
Before starting
Use the prepared Boto RuneLite installation and launch it manually. This guide begins once the plugin is installed; there is no public installer or automatic launch service on this site.
- Open RuneLite and the Boto Quester sidebar.
- Sign into the game yourself and dismiss the welcome screen.
- Wait for the account-mode observation and the quest catalogue to become readable.
- Read any preflight refusal in the sidebar. Resolve its named cause before arming.
Regular, Ironman and Hardcore Ironman are in scope. Ultimate Ironman is not supported. An unreadable account mode is shown as pending or unknown, never assumed to be regular.
Choose quests
- While the panel is Ready, select Edit quest queue.
- Search the catalogue in the separate selection window. Inspect the requirements and any implementation refusal.
- Add quests and arrange them in the desired order.
- Choose Save and wait for the save result. Closing without saving does not apply a draft.
The sidebar shows the saved selection and a preview of the next three quests. Unfinished prerequisites are placed before the quests that need them. A launch-time quest override takes precedence for that launch and is shown explicitly.
Catalogue colors have text labels: green — Completed, yellow — Eligible, red — Requirements missing. Unknown readings remain unknown. Eligibility is not a guarantee that every supply source or quest step is implemented.
Arm and follow progress
Select Arm to run the preflight. Boto acts only after those checks pass. Editing is locked during an active session.
The sidebar shows the current quest and activity, elapsed and remaining session time, upcoming quests and queue outcomes. Expand Queue notes for specific waiting or blockage reasons.
The session limit is measured from a successful Arm. Pauses, quest changes and reconnects do not restart the budget. Reaching the limit requests a safe logout; combat or a logout-unsafe encounter may delay completion.
Stop a session
Select Stop, then wait for the confirmed login screen. A stop request is not an immediate logout. Keep the client open while stopping completes.
Disabling the plugin does not log out. Use Stop first. Boto does not automatically re-login at the end of the session.
When a quest cannot continue
Read the specific reason in the sidebar. A quest-specific blockage can yield to another eligible selected quest; exhausted selections retain their outcomes. Missing inventory alone does not establish that the bank is empty.
- For a missing requirement, inspect the catalogue's current and required values.
- For a supply gap, look up the exact item form in item coverage.
- For Gate A instructions, use the login-screen diagnostics shown in the panel. Record and Probe are diagnostic actions, not quest start controls.