Czar

Hello it's recommended to have the runes/staves/equipment already prepared before starting the bot for maximum stability, if you'd like I could easily add a way to withdraw runes too, would only take a few mins. I'll do this for the upcoming version ty :]

Will add a handler for this too. Any success with the script lately, any bans/decent level-ups?

Done enjoy, update was delayed for a bit since I'm using the opportunity to re-write a couple core parts of the bot, you guys will appreciate it and notice a huge difference Edit: posted v136.0 will be live automatically in a couple hours enjoy. Some features in the previous page described were antiban features which help prevent bans but I am in the process of making everything optional, and placed in the behaviour tab. With that being said I’m also adding new stability improvements in the next version

You mean like equipping the staff to alch then re-equipping main weapon once the game starts? I can add this if you want, easy I just thought it would be more efficient & safer (fewer bot clicks) to just alch with runes - update coming up.

Bot is back online enjoy! It's working again EDIT: Also, update v141.1 is now live you guys will be noticing some improvements over the last version, gl

Done enjoy! I'll take a look at the code @eremenow thank you

Please avoid botting in hotspot/typical botting areas like Monk of Zamoraks.. that's one of the worst places to bot nowadays. Try zeah, there's a whole continent out there if you really want to avoid bans you'll avoid them. It seems none of you have mirror mode I highly recommend using mirror if you want to prevent bans, but stealth is fine. Make sure you give this a read before botting and you'll see better success: Preventing RS Botting Bans V3 - Botting & Bans - OSBot :: 2007 OSRS Botting

Authed a few bots. I'll announce it as soon as the patch/fix goes live. So sorry guys it's completely my fault I wanted to optimise the script for the newer coming client style and made a few mistakes

Guys please use the new devbuild, the setup interface keeps glitching on the old osbot (v2.5.87) and freezes. It is sorted out & fixed in the old client too we're just waiting on an update (automatically happens and shouldn't take long) but please stick with the newer clients: http://osbot.org/devbuilds/osbot 2.6.0.jar If you still can't get it to run, pm me I'll temp auth you other bots of mine to use for free until the update goes live. This applies only to users who own a copy of the Perfect Miner bot!

Hello sir Did it use any teleports or did it manually walk there via minimap, I'll try figure out what happened Thanks!

Fixed sorry. I was trying to make it compatible with the newer version of osbot (devbuild/new theme) and the old one is no longer starting up. Update will automatically go live within a couple hours, so sorry about this guys

Working better now? If not show console logger so we can help ^^ the bot is currently working as we speak btw! And did you have [Hop on crash tile] activated? If not dw about it, I'll try add a case so it knows how to prevent this scenario. Also with world hopper? Much respect ty sir, activated trial enjoy! Activated trial enjoy!

Dw about it, if you get another chance to use the script lemme know if it works better for you please ^^ As for trials activated enjoy. Still working on GE restocking guys, my apology for the delay.

Awesome! Lemme know if you have any other issues or feedback so I know what to do in the next pest control bot update please ^^

Sure, enjoy guys! Activated all, in other thread too

Not yet so sorry. It's a super unique/niche method that may as well be a private script by itself. I am going to add it as soon as I can, since I also need this type of system for my fighter bot and the code will be the same. I will let you know when it's added, but there is no promised date. For the record it's not as easy as people think Found the issue, will be in v141. I've talked to devs and other scripters and apparently the osbot webwalker prioritises roads over other paths, should be an easy fix. Will fix, along with the issue of varrock clay mine in terms of webwalking that @Diesal mentioned above It's supported, added trial enjoy Straight after tut (after botting tut) or manually completing tut? It makes a huge difference to be fair. The only data I have with bans is the thread, so we need to go back a few pages and see any reported bans. Are you planning on mass goldfarming or training a main? Please confirm so I can help further Yes activated trial enjoy. I'll update the thread to show that it's supported too, ty for the reminder

I'm happy to hear this, any hiccups or issues since then? Weekend's coming up for more blast furnace so I'll be preparing some accounts too I hope muling is ready before friday I know I keep saying this but it's a semi-complex task to add Where/when - questing, blast furnace, grand exchange? I will help Yes, but I recommend only botting blast furnace (in general) on throwaway accounts since it's a hotspot for bans. However if you must, then please keep the botting hours to a minimum of 1-2 hours per session followed by at least 2 hr breaks for the best results in my opinion (in terms of preventing bans).

Done enjoy!

RS Isn't even loading for me rip

Done enjoy!

I think I know exactly why - will be fixed for the update coming today. Any parts of the script which you would like to see sped up or slowed down? ^^ EDIT: Also any good progress (or hopefully not bans) btw? Or any pets? xD

Done enjoy

Done trials activated enjoy. Yes the npc name for curse alch is fine, just be sure to choose a good place to curse alch

private CombatManager cm = new CombatManager(myPlayer(), gearNames, lummyCows, lootables); this needs to be: private CombatManage cm; and then in onLoop, you can do: if (cm == null && myPlayer() != null) { // once player exists, and if cm isn't instantiated, create one. cm = new CombatManager(myPlayer(), gearNames, lummyCows, lootables); } This can also be done in onStart but the player may either be logged out while the script is running and maybe not everything has been initialised just yet so it's better in onloop. If anyone has any recommendations or anything to contribute let us know xD So it's generally recommended to only instantiate stuff after the script starts, so that myPlayer() has meaning/context. Before the script runs it's null so you're essentially giving null parameters to the CombatManager class. Variables declared outside methods will execute before everything else, so you need to be wary of that xD If the above code still doesn't work we may need to see some more code to help

Done trials activated good luck!