Gunman

Did you rename the osbot jar file? You should be going to the location of this and selecting it

Do what Grand Pappy Medusa said

If you know what you are doing they can be banned with 5-10 minutes or 5-10 weeks.

Some do. But normally if you need to escape pkers or if it's a script with prayer flicking or something like that where timing matters then yeah it needs to be 50 ms. The only scripts that legit do not work on Mirror no matter what is I think Frost Caves. So stuff like wood cutting would be fine with higher ms. Good idea btw with starting in f2p. If you can survive f2p then you'll survive p2p.

@Nathan2302 Were you doing this in F2P or P2P? F2P has insanely higher ban rates. Also the way Mirror Mode works is one it will connect to the official runescape client making it look like you're using the offical client and not a 3rd party. Two it has a reaction system that can go anywhere from 50-5000 ms (1000ms = 1 second), which people believe help change the timing pattern the script would normally use. Do keep in mind some script won't work with Mirror unless it's set to 50ms also there is a few scripts that don't work with it at all.

And that wasn't even with mirror mode lol

"send nuds"

Depending on how many bots you're running and how often you do it. But I would say low. If you really wanna test this; Then try making a few new accounts and just power level a f2p runecrafting for a while with runners. Fluctuate the runners hours and the account your power leveling is. Let's say you make 20k/hr at the Fire altar. 10 runners could make you up to like what? 180-200k/hr xp. Imagine if you did this with lava runes. But again like everyone else said above there still is a chance of a ban.

Maybe but you are still having an issue. Add Dream's GE Firemaker to your script list and run it and see if the login handler works for you. If it does it's the script you're using. If not it's something else. Which might be a pain to figure out.

Seems useful not gonna lie.

You mean the login handler? That's been working fine. Think it's just you bro

@Eagle Scripts The issue in the video above appeared again for the first time in 2 weeks. Here's a picture of the position. Moving the camera view distance did nothing as you can see in the picture below. I don't think you will be able to fix this issue easily nor do I think it's worth your time right now since you're so busy right now.

Your reminder if you got time.

You mean this?

@icepotion Condition Sleeps. Number 9. Sleeping in Explv's Tutorial

It does have 4 points. Imagine when you set those 2 points they both shoot out lines horizontally and vertically. Then Area will grab where the lines intersect and set the 2 other points where x1 y1 x2 y2 intersect. And boom! Your square/rectangle area has been created.

Whoops forgot to remind you. But did you put it in?

Am I qualified for a trial?

With Mirror Mode there use to be a bug with bank tabs. I don't remember if it was fixed or not.

If you are using stable build try this build Other wise I am certain you are using bank tabs and I think there is still a bug with banks tabs and Mirror Mode. Just move all the items to the main tab and keep all the items in that one tab.

Does it still happen on a fresh client or one where you have stopped and started that script many times after changes and such? Probably would need to see the script source to diagnostic it more precisely. I might fall asleep here soon so If I stop replying that's why.

What do you mean by freezes? Is this in Mirror Mode or Stealth? Also could you provide a picture(If Mirror both clients)?

I think it mean Chicken Killer 🤣

1. Make a method for checking the value and enabling it using the API. 2. Try using this below instead of isWearingItem. getEquipment().isWieldingWeaponThatContains(axe); 3. Actually number 16. Adding a GUI in this post is I think 95% copy and paste for your current situation lol.