Botting for RuneScape Classic that survives the update

Test

Auto login moved onto the character. It was one switch in Settings shared by every client in the window. It is now on the account's card in the Characters tab:

• Log back in automatically — yes, no, or leave it on the default.
• Wait first (seconds) — blank follows the default.

The wait is jittered a second either way, so several clients never come back on the same tick. Nothing to do on upgrade — every character carries on as it was.

Clients update themselves between scheduled runs. When one run finishes and before the next starts, the launcher checks whether the server has shipped a newer client. If it has, it downloads it, closes the old one, opens the new one on the same account without asking, and the schedule carries on.

It will not swap onto a build we have no hooks for yet — it waits and tries again — and it only closes the old client once the new one is downloaded and checked, so a failed download leaves you on the client you already have.

Closing a client now logs its character out, including when you close the launcher. Characters were being left standing in the world.

A big update. Characters now carry their own login, the scheduler has moved onto the character it belongs to, the sleep captcha reader handles both kinds the game throws at it, and scripts can log themselves out.

---

The Identity tab is now a character hub. Click an account and its own card opens with everything about it in one place.

• Save a username and password per character. Passwords are encrypted on your machine with a key that never leaves it. They are never sent to us, never written to a log, never in a crash report, and no script can read them.
• Every new client asks which account to use. Pick one, or pick "No account" and that client runs completely unspoofed - your own machine, your own connection, no proxy - for the accounts you play yourself.
• The login boxes stay filled. Once a client is on an account the username and password are put in, and put back. Type over them and they come straight back.
• "No spoof" hides the uid, machine and proxy fields, because none of them apply to an account you are not spoofing.
• A hand-typed login that works is saved for you. Log in by hand once and that account is in the hub afterwards.
• Every client's title bar shows the account it is linked to, and the console is now per client - click a client and you see that client's output and nothing else.

---

The scheduler has left Settings and moved into the character card, because a schedule belongs to a character, not to the launcher. There used to be one schedule and every client in the window obeyed it, so a day written for the account you were looking at also stopped and started the five beside it.

• The day in quarter-hours. Each column is an hour, top to bottom :00 :15 :30 :45. Left-drag from one quarter-hour to another and everything between them is picked - that is when this character may bot.
• Right-click a quarter-hour to say what runs from there on. Anything: a script on your computer, a script from the site, or any .jar or .bot file you point it at. It keeps running through every botting hour until you place another script later in the day, and then that one takes over.
• Hover a quarter-hour and it tells you what runs then.
• A "Schedule active" switch, off until you turn it on. Draw the day first and switch it on when you mean it.
• Export, import, and copy from another character. A day worked out over a week is worth keeping - save it to a file, send it to a friend, or put it on a second character without drawing it again.
• When the day is done it logs out, and it stays out - auto-login will not quietly pull it back in. It keeps asserting it until the character is actually gone rather than sending one packet and hoping.
• It only takes charge once you have run a script on that client. Opening the launcher outside your botting hours will not log you in and log you straight back out.

---

Two things, and the second one is the one that has been biting people.

It reads both kinds now. The classic word, and the newer arithmetic ones - a sum on a black background. The reader works out which kind arrived on its own; there is nothing to choose.

And it will not type a stale word. An answer is now tied to the exact sleep image it was read from, so a word from a previous picture can never be typed for a new one. If a fresh image arrives while an answer is in flight, the old answer is thrown away, the new picture is read, and that is what gets typed. Duplicate images are recognised as duplicates rather than answered twice, and a word that cannot be read is re-probed instead of guessed at.

---

New command in the text engine. It sends the game's own logout packet rather than clicking the button, so it works from anywhere without opening a tab first.

logout()
wait until not loggedIn() timeout 10000 else { print("still in - in combat?") }

The server has the final say. It refuses while you are in combat or have just been, and it says nothing when it refuses - so check loggedIn() afterwards rather than trusting the answer.

---

• Closing a client closes that client. When it was the only one open it used to close the whole launcher.
• The client now loads while you are choosing an account, rather than after.
• A client losing its window while shutting down no longer crashes itself on the way out.

- Names on parked clients
- Toast system to show messages sent when a client is parked
- Flash on clients not selected when someone is talking to you and nobody else is around.

- Fix to Dynasty client loading
- Fix voidscape 2 broken hooks
- Text engine IDE now detects what client you're focused on and runs it on that deck
- Implemented Rent a bear system where she can bot on her phone