Albatross

But it's weird because you have people using scripts that are absolute shit in terms of detectable patterns, etc, and they aren't getting banned. Maybe before they IP flag you (first ban), you're safe from autobans, at least for 07. Not really sure though completely

So let's assume no IP flag (I've never been banned); pretty "safe" to bot when it's like 1am in UK time? I guess we don't really know the true method for auto banning, I mean there's people who run scripts that have what people would consider terrible anti ban (pathing, mouse stuff, etc). All these people getting banned are usually IP flagged to begin with

Yeah no one ever talks about what time of day they were botting, and a lot of the bans are bot busting moderate bans which I believe are still manual bans. I'm thinking if you've never been banned before (aka your IP isn't flagged etc), this is a confirmed way to prevent initial bans. I don't know about the auto bans though that's what I'm trying to figure out

So I remember last year people were talking about the time of day being critical to avoid getting banned. Like if you are in the United States, it was recommended to bot starting at 6pm EST and beyond (11pm UK time) because no jmods would be working at that time. I see all these bot busting moderate bans and, at least last year, that meant it was always a manual ban or something. That could be different now though. Any input?

I'm pretty sure all of these bot busting moderate bans can be avoided by playing when mods are not at the office (so like 4pm EST and onward). I remember people talking about this a year back; I never had a problem. The auto bans however, that's another story

Yeah just multiplies in inventory.

Some IDs like doors (surprise exam for example) change from time to time when Jagex updates (usually weekly). This in turn breaks the randoms that were previously solved, unless OsBot uses a method to diminish the use of IDs in random events, but idk.

Surprise exam gets stuck when Mr. Mordaut says to go exit the room (doesn't click continue; if you manually click continue just clicks him again)