Token

Yes Authed

I am aware of a few issues caused by the new client version, the fix should be on SDN soon Authed

Lol you have a perm auth in my database idk why

Fruity and Realist are usually online

Just refresh the scripts in the client and it should be there It's most likely waiting for the witch to move to the best position so that it doesn't get caught, may take up to 30-40s until the witch walks a full path, PM me the whole logger contents if that's not the case

Authed

Authed Authed

1 trial per person

Thanks but only thing I need for quests is data & algorithms which are by no means easy to obtain Thanks, I'll check it out

Authed Idk

Just speak to Edmond and he will give you the teleport scroll if you don't have it, or if it's in your bank all you have to do is read it

Authed About 69 I think ~10 hours Depends on quest That's not an error, it means whoever completed Plague City on that account did not finish all stages including getting the teleport reward at end which the script automatically does

It's impossible to figure out since we all have a different botting style, which is why some of us get banned while others don't

Authed

It's exactly what I told you from the first time I'll look into it The Knight's Sword is already added

Try doing what I mentioned above, that's going to fix everything Are you sure you aren't using mirror mode? Fill in the bug report template otherwise

You can find out if that's really the issue by opening the logger, but yes you should be able to run Goblin Diplomacy however this error is in the OSBot client, not the script, and there's nothing that can be done from a script to fix it other than implementing a private webwalking API for when OSBot's fails to load

Open the logger and check what's written in there From your description this is usually the most common cause

That most likely means you did Priest in Peril manually and forgot to unlock access to Morytania at the end which is required for Animal Magnetism, or you are missing other requirements. Check the logger to find the exact cause.

That's been implemented since september last year

Authed Authed

Fill in the bug report template

There is no ETA

Authed

Authed