Gunman

We love you too buddy. Some will hate you for this but they will come back around

Gratz on release. Ditto party

yes <- Config used. Goes here -> C:\Users\user\OSBot\Data\StealthNmz

if (!getInventory().contains("Law rune")) { if (!bankArea.contains(myPOS)) { getWalking().webWalk(bankArea); } } !getInventory().contains("Law rune") <- if this returns true it will forever return true. Since it always returns true it will forever loop the code above^ Just move the banking stuff after the bank area check would probably fix this. Avoid using static sleeps when you can. Static being sleep(1000); or sleep(random (1000, 2000)); <- both are what I consider static. Another thing why is your onloop returning hopTo which is == -1? Change it to return like 500 or something.

I own the script. I looked and it has tele alching. Pic below of the script

No, all sites claiming to be Bogla or Arcus are scams. Alch is the new big one. If I remember right Alch is owned by the original owner of Bogla before he sold it to Arcus.

Only one that I know of and could find was Perfect Magic AIO

@xnitionI recently ran into this issue. A temporary fix would be using 64 bit java instead of 32 bit. After a while I also assumed it was a client issue, but it wasn't. I would recommend you reboot your system into safe mode. Open a CMD or PowerShell and type "sfc /scannow" . It should say something like "Beginning verification phase" and there should be a another line below it saying "Verification x% complete". Wait till it finishes, then restart your pc and try opening MM again.

@obrandso The script will forever be stuck in the first if statement if you don't have law runes.

@bigbob420Pretty sure project SDK needs to be set to java 8 and in artifacts you don't put the osbot jar there and you're not exporting the script file. Open test element and double click the test out file

I remember reporting this a long time ago but the bot get's stuck on a rock fall at the blue circle below. If I remember correctly this can happen in more locations. But what it looks like is the bot is walking and checks if a rock fall is then, then trys to walk further to the bottom right position but a rock fall falls at the right time right in front of it. Bot will stay stuck trying to walk thinking the rock fall isn't there till I manual have it mine the rock fall. It's fairly uncommon. Happens to me once every hour or 2. Client: Stealth Injection 2.5.70

I currently have 0 bans on either version... .70 has 1 account suiciding in p2p for ~48h now, 1 combat account killing chickens when melee stats under 20 and then switches to cows till base 60's at ~24h .73 has 1 account suiciding agility in Mirror Mode ~24h, Another combat like above with same hours of ~24h 100% sure it's because of Jagex working at home. Plus the server issues probably, got their hands full.

They're down again. They were up but not anymore

What do you mean they workin now....

Mhmm looks like rc just sucks lol

No. None of the tutorial island scripts does this here at OSBot.

Botters together stronk!

Did you not see the 2 post above you, where one person asked for a trial and he authed them. The answer is yes lol

@Patrick Do you have any ideas to counter the issue with combat scripts? Example being Fruity Zulrah and Excellent Vorkath would need faster mouse speeds.

Oh that's hella cool. May be a problem with bans lowered because of the quarantine, but still can do testing of the 2 mouse version side by side.

I highly doubt that. People get false banned quite often. Even when using Jagex's client. Just appeal the ban, if you didn't bot you should get unbanned.

Yeah, just use the or operator -> || and add another boolean to check if you leveled up

@Jueix Does changing the if's like this fix that? Because it shouldn't go into the else if like you have it now if it already was inside the if before it. if(randomclicks < 3) { //stuff } else if(randomclicks >= 3) { //stuff } if(inventory.getItem("My item end").getAmount() == 28) { //stuff }

@Jueix Okay I see why it's going to stage 3. It's because the break; is inside the else if and the code isn't reaching that, so it continues to the next case. Now idk if anything else is broken in case 2 but that's why it's moving to case 3 regardless if it should or not.

@Jueix You had it right using the press and release getKeyboard().pressKey(32); getKeyboard().releaseKey(32); I personally use the number^ But it said there was an NPE at line 128. What's line 128?