Website tracking

The Tracking button opens the Website Tracking screen. It has one field, Script API Key, which links your runs to your account on dentist-scripts.com so you can see your stats there: runtime, quest points gained, XP gained, tasks completed and levels gained.

Setting it up

1. Get your API key from dentist-scripts.com.
2. Open Tracking and paste it into Script API Key.
3. Press Start as usual.

The key is saved with your other settings, so it’s in Last Run and in any profile you save (see Profiles). If you change it in Edit plan & settings during a run, the new key is used from the next update.

What is sent to the stats website

The script sends a small update to dentist-scripts.com as soon as the run starts, then every 3 minutes, and a final one when the script stops. Updates are only sent while the account is logged in.

Each update contains:

• Your OnlyBot user ID.
• The account’s in-game name.
• The script’s name (Crazy Ironman Builder) and version.
• Whether the login screen is showing the account as banned.
• Your Script API Key, if you entered one.
• How much each of these has gone up since the last update:
  • Quest points gained.
  • Total XP gained, across all skills.
  • Tasks done: tasks in your plan that weren’t finished when the run started and are finished now.
  • Total levels gained.
  • Current quest points.

Runtime isn’t sent as a number; the updates themselves mark when the run started, that it’s still going, and when it stopped.

Note

These updates are sent whether or not you enter a key. The key only decides whether the stats show up under your account on the website. There’s no option to turn the updates off.

Other data the script sends

Besides the stats website, Ironman AIO sends the following while it runs. None of these have an option to turn them off, except the Discord alerts you set up yourself.

Usage statistics

Every 3 minutes and when the run ends, the script reports to the script developer’s statistics service on the developer’s own server (api.crazyservice.org):

• A random ID for the run, your OnlyBot user ID and OnlyBot username, the account’s in-game name and account type (for example ironman or hardcore ironman).
• The script version, when the run started and ended, and how long it was active and paused.
• XP and levels gained in total and per skill, current quest points and quest points gained.
• The name of each quest completed, and a note if the login screen reports the account as banned.

The same service works out your runtime rank, the “#x of y” line at the bottom of the paint, from your OnlyBot user ID.

Your Discord alerts

If you enter a Discord webhook URL in Preferences, the alerts you tick are posted there. Each one names the account and includes a screenshot of the game. Nothing is posted without a URL.

Diagnostics to the developer

These go to the developer’s own server (api.crazyservice.org), which passes them on to a Discord channel run by the script’s developer, to help find and fix problems. The script itself holds no address for those channels.

• On every death (at most one per 30 seconds): the account’s name, runtime, task and status, position, health and prayer, what it was fighting, up to 8 inventory items, recent game messages and status changes, and a screenshot of the game.
• When the script stops by itself for any reason other than finishing the plan (for example nothing left can run, or a login timeout), and at the end of any run longer than 24 hours: the account’s name, the reason, the runtime, the current task and status, the account’s position, its inventory, recent game messages, the unfinished tasks and their status, and a screenshot.

Debug reports

A debug report is sent when you press Send debug report in the side panel, and automatically when the script stops itself for standing on one tile too long, dying repeatedly, or a bank step failing over and over. It is the OnlyBot client’s own debug report, which includes a snapshot of the client’s recent log, a screenshot, and technical details of what the script was doing, plus the script’s own notes: the task, its status, progress, completed tasks, recent game messages and status changes. A screenshot with the task and status is also posted alongside it.

The client sends its report straight to a Discord webhook run by the developer. The script fetches that webhook’s address from the developer’s server while it runs, rather than carrying it. The screenshot posted alongside goes through the developer’s server like the diagnostics above. If the address can’t be fetched, the client’s report isn’t sent: the script sends its own notes and the screenshot through the developer’s server instead.

Humanized Mode doesn’t send its timings anywhere.