Leaderboard

" If you found this useful let me know in the comments " Not at all, sorry. You were vague in this post and if anything you only started a discussion. If you're aiming to provide some help to the community start with some things that you figured out that causes bans 100% of the time like you say here... "like these are just some variables that have caused some of my bans which im 100% about."

Wtf why????

NEW! Added Gemstone Crab! 81 Hours at Cows Brutal Black Dragon support Sulphur Nagua support Blue Dragon 99 ranged 99 Ranged at Gemstone Crab 81 Range F2p Safespotting Hill Giants Hotkey List // F1 = set cannon tile // F2 = hide paint // F3 = Set afk tile // F4 = reset afk tile // F6 = Set safespot tile // F7 = activate tile selector // F8 = Reset tile selector // F9 and F10 used by the client, EDIT: will re-assign as they are no longer used by client // F11 = Set breaks tile // F12 = Reset breaks tile User Interface Banking Tab Demo (handles everything with banking) You can copy inventory (to avoid adding individual items...), you can insert item names which have Auto-Fill (for you lazy folk!) and you can choose whether to block an item and avoid depositing it in bank, ideal for runes and ammo. Looting Tab Demo (From looting to alchemy, noted/stackable items too) You can choose whether to alch an item after looting it simply by enabling a checkbox, with a visual representation. All items are saved upon exiting the bot, for your convenience! Tasking Demo (Not to be confused with sequence mode, this is an individual task for leveling) You can set stop conditions, for example to stop the bot after looting a visage, you can have a leveling streak by changing attack styles and training all combat stats, you can have windows alert bubbles when an event occurs and an expansive layout for misc. options! Prayer Flick Demo (Just example, I made it faster after recording this GIF) There are two settings: Safe mode and efficient mode, this is safe mode: Fight Bounds Demo Allows you to setup the fight bounds easily! Simplified NPC chooser Either choose nearby (local) NPCs or enter an NPC name to find the nearest fight location! Simple interface, just click! Level Task Switch Demo (Switching to attack combat style after getting 5 defence) You can choose how often to keep levels together! e.g. switch styles every 3 levels Cannon Demo (Cannon is still experimental, beta mode!) Choose to kill npcs with a cannon, recharges at a random revolution after around 20-24 hits to make sure the cannon never goes empty too! Results Caged Ogres: How does this bot know where to find NPCs? This bot will find far-away npcs by simply typing the NPC name. All NPCs in the game, including their spawn points have been documented, the bot knows where they are. You can type 'Hill giant' while your account is in Lumbridge, and the bot will find it's way to the edgeville dungeon Hill giants area! Here is a visual representation of the spawn system in action (this is just a visual tool, map mode is not added due to it requiring too much CPU) Fight Area Example (How the bot searches for the npc 'Wolf') Walking System The script has 2 main walking options which have distinctive effects on the script. The walking system is basically a map with points and connections linking each point. It tells the script where to go, and decides the routes to take when walking to fightzones. Walking system 1 This uses a custom walking API written by myself and is constantly being updated as new fightzones are added. Pros: - Updates are instant, no waiting times - More fightzones are supported Cons: - Sometimes if an object is altered, the changes are not instant - Restarting the script too many times requires loading this webwalker each time which adds unnecessary memory (there is no way to make it only load at client startup since I don't control the client) Walking system 2 This is the default OSBot webwalking API - it is relatively new and very stable since the developers have built it, but is currently lacking certain fightzones (e.g. stronghold) and other high level requirement zones. It is perfect for normal walking (no object interactions or stairs, entrances etc) and never fails. Pros: - Stable, works perfect for normal walking - All scripters are giving code to improve the client webwalker - More efficient when restarting the script since it is loaded upon client start Cons: - No stronghold support yet - Some new/rare fightzones not supported yet - If there is a game-breaking update or an unsupported fightzone, it may take some time to add/repair (less than 24 hours usually) So which system should I choose? Whichever one suits your chosen fightzone best! There really shouldn't be any problems - the sole purpose of these options are for backup and emergency purposes, if the script ever messes up there is always the next option to select. Note: If the script ever fails, there will be immediate updates to fix the walking systems! Script Queue/Bot Manager: Script ID is 758, and the parameters will be the profile name that you saved in the fighter setup! Bug Report templates: New feature request - What is the new feature - Basic description of what the script should do - Basic actions for the script: 'Use item on item' etc. For when the script gets stuck on a tile (or continuous loop): - Which exact tile does the script get stuck on? (exact tile, not 'near the draynor village') - Plugin or normal script? - Did you try all 3 walking options? Script has a logic bug (e.g. dies while safespotting) or (cannon mode doesn't pickup arrows) - What is the bug - How did you make the bug happen - (optional) recommendation for the bug, e.g. 'make the script walk back' or something - Tried client restart? - Normal script or a plugin? - Which exact setup options are enabled? Afk mode, cannon mode, etc etc.

Declare a timestamp variable before you execute the web walk. This will record the current time when you start the web walk. Then in the web walking conditional event do a comparison between your timestamp and the current timestamp. ORIGINAL_TIMESTAMP - CURRENT_TIMESTAMP = TOTAL ELAPSED TIME IN MILLISECONDS. In the conditional event if the total elapsed time equals whatever value you want, then exit the web walking event and using the same logic you can create a statement (or method) to compare the timestamps again before executing the web walk. If the timestamps equal the amount of time you want elapsed, then execute your code. Otherwise continue walking. To improve the functionality you can use a class in its entirety to handle all of this. You could use a singleton design pattern for a class called "RANDOMIZER" and handle all of the code in this special class.

Just picked it up today. I love the super heat. As an Ironman these scripts make the grinds more bearable. Thank you.

This is an almost flawless script, and simple to use...even for me! Good work.

ah, you mean randomized actions. You can do those in a timer and execute them regardless if it's walking or not. It doesm't do anything to reduce bans just so you know. Create various timers for the actions and couple the action with the timer reset. Run these on separate threads.

thanks loving the script fucking fantastic nice neat gui aswell

Wow, that is actually pretty good progress!

int count = 0; int counterRandom = random(1, 15); ScheduledExecutorService executor = Executors.newScheduledThreadPool(1); @Override public int onLoop() throws InterruptedException { if (myPlayer().isMoving()) { count += 1; sleep(1000); log(count); } if (count == counterRandom) { log("Done"); counterRandom = random(1, 15); count = 0; } return 0; } // separate thread public void startCounter() { executor.scheduleAtFixedRate(new Runnable() { public void run() { if (!myPlayer().isMoving()) { count = 0; } } }, 0, 1, TimeUnit.SECONDS); } // stop counter public void stopCounter() { executor.shutdown(); } // call start counter method before starting webwalking startCounter(); // perform webwalk // call stop counter method after webwalking is finished stopCounter(); So basically, what you need to do is start a counter before you begin the webwalk. This counter will run in the background while you're moving. It will keep track of the count every second. If your player stops moving, the counter will reset back to zero.

ASYNC

Enjoy!

Just do it on a separate thread. The main thread will be executing the webwalkevent.

Sure, trial activated -Apa

New Update (v164.0) - Added safety for superheat ore + running out of coal/ore - Added Custom Break Manager, you can now run this with your favourite manager + Botting hub CLI More new features to come! Just wanted to release this because of popular demand

This is a recent screenshot from today i made a fresh new lvl 3 account and its still going on 😀 don’t forget to break alot

Hey looking to purchase this for my ironman but want to see features first. Could I please have a trial

I asked for a trial couple weeks back , duno if you activated it or not . either way i missed it . any chance of a retrial? want to test it on my ironman

Done added trial enjoy Be sure to check out the GE restocking feature for enchanting, right now this is the only magic bot on osbot that has some sort of GE feature

Yikes.

This is a horrendous way to make your name on OSBOT lol... he gave you honest feedback and you're lashing out like a child.

Hey great script but I was wondering if you plan on updating script anytime soon. Had some ideas for updates like putting in support for dark lure as well as running only to get to implings instead of just constantly running

Alternatively if you don't want to make a custom break manager, you can simply tell the bot to go to an area before breaks are triggered by using this method that based pat improved recently: getBot().getTimeUntilNextBreak() this will tell you the time (in seconds now) until breaks will trigger. So if getBot().getTimeUntilNextBreak() < 20, walk to bank or walk to a safe area.

Hi guys, This is my first real forum post on something I think is useful to the botting community. First of all my names Sam and ive been botting in OSRS for around 15 years having a few years off in between. Please ignore my slang/spelling lol I Cant even remeber the client i used 15 years ago but i do remember the only flawless script was mining Pure Ess Via V East bank. Shortly after a few more clients came available and better scripts came to the average user. Obviously with more users starting to use these clients jagex had to put a stop to all of this with the decline of legit osrs players joining the game and also OG players quitting due to the rampage of bots. So where im getting at is jagex created the Automatic Detection system/Program which basically eliminated the average botter completely with bans coming within 2 weeks max. But this was not the case for everyone botting, Depending on the script your using is really important and understanding how the detection system works is also a key factor in avoiding these bans. This now leads to what i wanted to talk about in this thread which is understanding the Jagex detection system. Now this comes with only experience and nothing else (getting banned 100 times for example) in my eyes is experience. So if your new to botting this will just be a waste of time as im not going to explain how. Im going to assume you already know this. So last week ive had a farm going in 2 different areas. I wont be specific as i dont want anything to cause unnessasary bans as these accounts are mid and end game and required alot of time. I noticed my first ban in a few months and normally i wouldnt think about why it got banned as id just make a new one and replace or forget about it quickly but this time I looked into it and relised i had set a variable different by accident and not relising. For example normally i could set something like Min break time (mins) - Max break time (mins) Min Run time (mins) - Max run time (mins) Hop worlds after X runs min - Hop worlds after X runs max Sleep variables for opening bank etc etc Dead hours (when your sleeping so its shut down for x amount of hours) the list goes on.... like these are just some variables that have caused some of my bans which im 100% about. If you found this useful let me know in the comments as i have more advice i would like to share even for begginer botters cheers Sam

What a good waste of 5 minutes of my lunch time.

mm2 chinning script got me a 2 day ban on my main with 1500 total level within 8 hours. never botted on this account. Definitely linked. Beware.

Well you probably haven't come across a decent Developer as of yet. That comes with experience, and yes there are plenty here. Say i was running a raid level 500 solo farm. You think i would tell you about it? Use some common sense im trying to help in some way and some people are going to understand it more than others. Have a good day.