Breaks and anti-ban

Ironman AIO has its own break and world-hop options, and it also works with the breaks you set in the OnlyBot client. All of them wait for a safe moment, so a break never starts in the middle of a fight, a minigame round or the Wilderness. This page explains how they behave. The options themselves are listed in Preferences.

Kinds of breaks

Break	Where it’s set	What it does
OnlyBot client breaks	The OnlyBot client	Your client’s break schedule. The script holds a break off at unsafe moments and takes it later.
Circadian breaking	Preferences	Breaks that follow this account’s daily habits: short pauses, meals, errands and sleep.
Enable global mini breaks	Preferences	An idle pause every so often, for the length you choose, optionally logged out.
Force break	Side panel	A short break right now (when it’s safe).
Herb-run wait	Automatic	When only a Herb Runs task is left waiting for its herbs, the script logs out until the next run is due.

Circadian breaking and mini breaks are either/or: turning one on turns the other off.

When a break can start

The script’s own breaks and world hops wait until the account is in a safe spot:

• logged in, the game loaded, and not in an instance;
• not in Guardians of the Rift, Tempoross, Wintertodt or Fishing Trawler;
• not in the Wilderness;
• not in combat, and at least 10 seconds after the last fight (the game won’t let you log out sooner);
• no dialogue or make screen open;
• standing still and not animating;
• health at or above 50%;
• not in a moment a task has marked as critical, such as Tithe Farm (the plants would die), waiting for a quest boss to appear, or looting blue dragon drops.

A break that comes due at a bad moment waits for the next safe one. If something happens during a break that doesn’t log out (an attacker shows up, say), the break ends early.

OnlyBot client breaks

The script leaves the client’s break handler on, and turns it off only while the account is somewhere unsafe: an instance, one of the minigames above, the Wilderness, combat (and the 10 seconds after), health below 50%, or a critical moment. A client break that comes due during that time isn’t lost: the script takes it, at its full length, as soon as the account is safe again.

The script doesn’t log in during a client break, and logs back in by itself once the break is over.

Circadian breaking

Each account gets its own break habits (see the break table in Preferences):

• Regular breaks come on average every 22 to 40 minutes, depending on the account. Most are short and stay logged in. Bathroom breaks, meal breaks and errands log out.
• Bedtime is between 9 pm and 2 am by your computer’s clock, and moves by up to 30 to 75 minutes either way from night to night. Sleep lasts about 6½ to 9 hours.
• Sleep never starts within 20 to 30 minutes of logging in. Once bedtime has passed, regular breaks wait so the account goes to sleep instead.
• Break frequency (Fewer, Normal, More) spaces breaks out or brings them closer, and changes how often they log out. Sleep isn’t affected.

Mini breaks

Mini breaks are the simple option: a pause every 15 to 45 minutes (by default) lasting 15 to 90 seconds, picked at random from your ranges. With Logout during mini breaks on, the account logs out for the break. The Force break button in the side panel uses the mini break length and logout setting too.

World hopping

With Enable global world hopping on, the script hops on a timer (every 45 to 90 minutes by default):

• It waits for a safe moment, like a break.
• It never hops during the Arceuus Library, Guardians of the Rift, Fishing Trawler or Mass Tempoross.
• It picks a different world of the right type for your account: members worlds for members, free worlds for free accounts. It skips PvP and high-risk worlds, members worlds with special rules (such as skill-total worlds), worlds whose requirements you don’t meet, and worlds that are nearly full.
• With a World-hop region set, it only picks worlds in that location.
• A failed hop is tried again a minute later.

Some tasks hop by themselves for their own reasons, such as another player at an item spawn. A members account that finds itself on a free world hops to a members world.

Per-account habits

Many small choices are rolled once per account and then kept, so each account plays a little differently but the same way every run:

• how low its health gets before it eats, and when it eats while walking;
• the run energy at which it turns run on;
• how long it waits between actions, and between tasks;
• whether it switches game tabs with the F-keys, the mouse or a mix;
• the pattern it drops items in (always shift-click dropping);
• how many coin pouches it collects before opening them;
• how much food it brings for quests;
• its break habits and bedtime;
• which money maker it prefers within a tier;
• with Randomize task order per account or a preset, its task order.

Dialogue is answered with the number keys, and the space bar to continue.

Humanized Mode

Humanized Mode is experimental and off by default. When it’s on, during safe moments it:

• adds small pauses and hesitations, and now and then lets a moment pass;
• does idle things: glances at the quest, skills, magic, equipment or prayer tab and comes back, hovers a skill it’s been training, peeks at a right-click menu, nudges the camera, moves the mouse off screen, or scrolls the bank;
• on long, quiet tasks (passive skilling or combat), sometimes notices late that the activity has ended;
• builds up fatigue over a session and as a break or bedtime gets closer, which slows it a little. Logged-out breaks rest it: sleep fully, errands and meals mostly, a bathroom break a little.

It also shifts the account’s eating threshold a little. Mouse movement itself is left to the OnlyBot client: Humanized Mode only tells the client how tired the account is.