Gunman

Try using !ore.exists() I don't know if this will work or not, depends on how OSBot does that method

It's possible to read login details of any account logged in, but not with native OSBot.

Right click -> open with -> choose Java. Java 8 is required btw.

@Wishy Thank you for the report. The evidence provided is sufficient enough to confirm the offense. The user has been punished. Dispute closed.

Make sure you have Java 8 installed and are opening it with Java 8

Yeah they also use finger printing

Depends on what works for you, some people run 1:1 some people run 1:2, 1:3, 1:4, etc up to even 1:60 or 1:100. But most people do 1:1 to 1:5 I believe.

$1-$15 a month depending on type and provider

Uninstall Java 17 and install Java 8

Not true. It's a temporary IP block. Switch IPs or wait a couple hours.

The details are stored locally and encrypted. Only way to retrieve them is by spam clicking the email field when the login handler goes to login.

@Teamwork OSBot doesn't hook var bits. So you can't access var bits with OSBot API. There was talk about adding them a while back, but they decided not to for some reason

You're using Java 11, Mirror only supports Java 8.

@sanyo1989 First photo says it's a jre but in the bat file you have jdk. Basically the path is wrong, change bat file jdk to jre. And the file path should still be in quotes as mentioned previously

Show bat file code

Generally not recommended to bot on accounts you care about.

Shouldn't having the friends only part of the chat selected and using the chat box api with maybe message listener work?

Add pause to the end of the bat file on it's own line. Should stop the box from closes so we can see what it says

Try jar fix https://johann.loefflmann.net/en/software/jarfix/index.html

Should rearrange it like below so you only sleep if the interact method returns true, if it failed then you will be sleeping for nothing. if (ashes.interact("Take")) { new ConditionalSleep(3000) { @Override public boolean condition() { return (!ashes.exists()); } }.sleep(); }

Short term it has no impact no, long term it might. And scripters can configure the mouse settings with the new mouse option, users don't have access to modify the mouse.

No, to trigger instant bans you would need to do some code related stuff. And normally from what I've seen they roll bans out during certain time frames of the day whether they're automated or manual. TL;DR - No it was from previous botting.

Check if it's http or socks5

Are they also socks5

Imagine clicking