Leaderboard

────────────── PREMIUM SUITE ────────────── ─────────────── FREE / VIP+ ─────────────── ──────────────────────────────────────────────────────────── ⌠ Sand crabs - $4,99 | Rooftop Agility - $5,99 | AIO Smither - $4,99 | AIO Cooker - $3,99 | Unicow Killer - £3,99 | Chest Thiever - £2,99 | Rock crabs - $4,99 | Rune Sudoku - $9,99 ⌡ ⌠ AIO Herblore - FREE & OPEN-SOURCE | Auto Alcher - FREE | Den Cooker - FREE | Gilded Altar - FREE | AIO Miner - VIP+ ⌡ ──────────────────────────────────── What is a trial? A trial is a chance for you to give any of my scripts a test run. After following the instructions below, you will receive unrestricted access to the respective script for 24 hours starting when the trial is assigned. Your trial request will be processed when I log in. The trial lasts for 24 hours to cater for time zones, such that no matter when I start the trial, you should still get a chance to use the script. Rules: Only 1 trial per user per script. How to get a trial: 'Like' this thread AND the corresponding script thread using the button at the bottom right of the original post. Reply to this thread with the name of the script you would like a trial for. Your request will be processed as soon as I log in. If i'm taking a while, i'm probably asleep! Check back in the morning Once I process your request, you will have the script in your collection (just like any other SDN script) for 24 hours. Private scripts: Unfortunately I do not currently offer private scripts. ________________________________________ Thanks in advance and enjoy your trial! -Apaec.

I've seen a couple threads with people having trouble with the trade api so I wrote this up to hopefully help with that. This features initiating trades, offering items, declining the trade and accepting all the way through the trade or accepting just one screen. If you want anything added to it or find any bugs let me know, and I will try and implement/fix it quickly. The constructor takes the MethodProvider as a parameter. The trade() method takes a Player or a string of the players name as a parameter. The offerItem() method takes an Item or a string with the name of the item as a parameter, and the amount to offer. The offerAll() method also takes an Item or a string as the parameter. The acceptTrade() method takes a boolean value as a parameter, if True it will accept both screens, else it will only accept one. The declineTrade() method takes no parameters. Example of it being used. The Code.

This is part two of my findings, although this time I created an entire 3D imaging software to bot with. Previously I was banned using a randomized alching macro script, paired with a HID device completely indistinguishable from a normal mouse in terms of appearance to native programs - although it took around two weeks of near constant alching. The software... Similar to how colorbots work, but based on imaging physical objects due to all the free libraries all over, computational speeds, and the simplicity of 3D objects in-game. I created a new software to control my HID device using a COM's port (Which it then translated to natural HID input). My mouse mover was a very advanced algorithm I worked on when I used to use OSBot, including a trained neural network portion which aided in speed/translations/overshoots/deviation/whatever. Multiple hours trained using my movements in-game to insure Jagex wouldn't be able to establish a difference between my movement, and the bots movement. The HID device was then seeded by https://www.random.org/ as generated a seed on a device is incredibly difficult due to the simplicity of the OS and overall hardware obviously. The bot, although somewhat slow at times, was very similar to my own movements. It's job was to simply mine for around 10 hours a day, then turn off. Then turn on the next day. Surprisingly this bot managed to net 3 million GP mining tin, in the course of about 1-2 weeks, with some days off. That compared to MirrorMode on OSBot is a MASSIVE increase in botting time. Sadly, it was just banned for Macro Major.. Ban cause speculation This ban bothers me. The software, undetected, the physical "mouse", undetected, the mouse movement, exactly as my own.. I'm really thinking, what pattern could possibly be this blatantly obvious that they would ban my poor bot permanently? No way it's the mouse movement? The pattern in mining, doubt it as it was based on my own (once more), and is simply too basic to detect a pattern. The timings? Should of been very random, with unbounded lengths (Meaning a random integer between 1-100 could result in 20,000 randomly), but still not ruling this out. Then lastly, the ban time frame.. It matches the alch bot near-perfect. A bot that did nothing but click a mouse, which didn't rely on software on the computer at all.. Is it possible that... Mouse down -> Mouse UP timing (A record I've already shown they logged), is responsible for these bans? Is it possible they're brute-forcing our seeds or using some type of algorithm which eventually learns our random patterns and can predict the next random number in the sequence (Given our randomizers use pseudorandom chains). Since we all use a static range of numbers between Mouse Down/Up, they will eventually detect regions of time of where our click events contain a constant, say 50-200MS between bound. Theoretically, given enough time, most numbers between these given bounds will result in the near-same number of uses. Writing an algorithm to detect a randomness pattern between the up/down (Or in other words, time it takes to click) would not be difficult, it would just require a lot of data. Furthermore, the ban rates tend to reflect mouse clicks. Agility for instance, requires clicking every 2 seconds. Essentially my conclusion: Randomization is a double edged sword. May appear random, but given enough time, creates a perfectly symmetrical shape. Instead of a horizontal random number picker, perhaps we need to look into more "human-like" randomization. Plans going forward... What I plan to do now, for anyone who cares, is to graph some of this data to visualize the data Jagex is being sent just to see how "random" looks. My next plan is to once more bot the living FUCK out of some rudimentary task, but this time with mouse delays based on my own timings. If I'm still banned, I'm just going to assume Jagex carelessly bans anyone who is doing a task for too long and this whole thing is a waste of time lmao The reason I focused on the mouse click delay in this thread is because it's the easiest input to track. No matter what bot, script, or macro you use, they all have randomized clicking. This is also the easiest pattern as it's consistent throughout all botting tasks

could be due the recent runescape update

Feed back removed as it doesn't fit the feedback system scheme. Positive: Positive feedback is meant for trades that have been completed without a problem. Also you are completely satisfied with what you have received and how the deal took place (The seller/buyer's behavior in the situation etc). Neutral: Neutral feedback is meant for trades that were successful but you are left unsatisfied with how the trade was completed. For example, if you were treated harshly during the trade or the item was not as described, feel free to warn other members of the seller/buyer's attitude or service by leaving neutral feedback. Negative: Negative feedback is meant for trades to where you have not received the item you have paid for or someone has taken away money given to you for a service. This can also be left if the buyer and/or seller is extremely rude or demanding, these will be handled in a case by case scenario by the Staff Team.

Running time between 90-120 Break time between 15-30 Log: [ERROR][Bot #1][03/23 08:13:36 AM]: Error in script executor! java.lang.IllegalArgumentException: bound must be positive at java.util.Random.nextInt(Unknown Source) at org.osbot.rs07.script.MethodProvider.random(ln:174) at aioLooter.CON.i(l:322) at aioLooter.CON.d(l:351) at aioLooter.AIOLooter.k(u:1869) at aioLooter.AIOLooter.onLoop(u:10) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(ol:278) at java.lang.Thread.run(Unknown Source) [ERROR][Bot #1][03/23 08:13:36 AM]: Error in script executor! java.lang.IllegalArgumentException: bound must be positive at java.util.Random.nextInt(Unknown Source) at org.osbot.rs07.script.MethodProvider.random(ln:174) at aioLooter.CON.i(l:322) at aioLooter.CON.d(l:351) at aioLooter.AIOLooter.k(u:1869) at aioLooter.AIOLooter.onLoop(u:10) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(ol:278) at java.lang.Thread.run(Unknown Source) [ERROR][Bot #1][03/23 08:13:36 AM]: Error in script executor! java.lang.IllegalArgumentException: bound must be positive at java.util.Random.nextInt(Unknown Source) at org.osbot.rs07.script.MethodProvider.random(ln:174) at aioLooter.CON.i(l:322) at aioLooter.CON.d(l:351) at aioLooter.AIOLooter.k(u:1869) at aioLooter.AIOLooter.onLoop(u:10) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(ol:278) at java.lang.Thread.run(Unknown Source) [ERROR][Bot #1][03/23 08:13:36 AM]: Error in script executor! java.lang.IllegalArgumentException: bound must be positive at java.util.Random.nextInt(Unknown Source) at org.osbot.rs07.script.MethodProvider.random(ln:174) at aioLooter.CON.i(l:322) at aioLooter.CON.d(l:351) at aioLooter.AIOLooter.k(u:1869) at aioLooter.AIOLooter.onLoop(u:10) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(ol:278) at java.lang.Thread.run(Unknown Source) [ERROR][Bot #1][03/23 08:13:36 AM]: Error in script executor! java.lang.IllegalArgumentException: bound must be positive at java.util.Random.nextInt(Unknown Source) at org.osbot.rs07.script.MethodProvider.random(ln:174) at aioLooter.CON.i(l:322) at aioLooter.CON.d(l:351) at aioLooter.AIOLooter.k(u:1869) at aioLooter.AIOLooter.onLoop(u:10) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(ol:278) at java.lang.Thread.run(Unknown Source) [ERROR][Bot #1][03/23 08:13:36 AM]: Error in script executor! java.lang.IllegalArgumentException: bound must be positive at java.util.Random.nextInt(Unknown Source) at org.osbot.rs07.script.MethodProvider.random(ln:174) at aioLooter.CON.i(l:322) at aioLooter.CON.d(l:351) at aioLooter.AIOLooter.k(u:1869) at aioLooter.AIOLooter.onLoop(u:10) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(ol:278) at java.lang.Thread.run(Unknown Source) [ERROR][Bot #1][03/23 08:13:36 AM]: Error in script executor! java.lang.IllegalArgumentException: bound must be positive at java.util.Random.nextInt(Unknown Source) at org.osbot.rs07.script.MethodProvider.random(ln:174) at aioLooter.CON.i(l:322) at aioLooter.CON.d(l:351) at aioLooter.AIOLooter.k(u:1869) at aioLooter.AIOLooter.onLoop(u:10) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(ol:278) at java.lang.Thread.run(Unknown Source) [ERROR][Bot #1][03/23 08:13:36 AM]: Error in script executor! java.lang.IllegalArgumentException: bound must be positive at java.util.Random.nextInt(Unknown Source) at org.osbot.rs07.script.MethodProvider.random(ln:174) at aioLooter.CON.i(l:322) at aioLooter.CON.d(l:351) at aioLooter.AIOLooter.k(u:1869) at aioLooter.AIOLooter.onLoop(u:10) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(ol:278) at java.lang.Thread.run(Unknown Source) [ERROR][Bot #1][03/23 08:13:36 AM]: Error in script executor! java.lang.IllegalArgumentException: bound must be positive at java.util.Random.nextInt(Unknown Source) at org.osbot.rs07.script.MethodProvider.random(ln:174) at aioLooter.CON.i(l:322) at aioLooter.CON.d(l:351) at aioLooter.AIOLooter.k(u:1869) at aioLooter.AIOLooter.onLoop(u:10) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(ol:278) at java.lang.Thread.run(Unknown Source) [ERROR][Bot #1][03/23 08:13:36 AM]: Error in script executor! java.lang.IllegalArgumentException: bound must be positive at java.util.Random.nextInt(Unknown Source) at org.osbot.rs07.script.MethodProvider.random(ln:174) at aioLooter.CON.i(l:322) at aioLooter.CON.d(l:351) at aioLooter.AIOLooter.k(u:1869) at aioLooter.AIOLooter.onLoop(u:10) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(ol:278) at java.lang.Thread.run(Unknown Source) [INFO][Bot #1][03/23 08:13:36 AM]: Terminating script Fury AIO Looter... [ERROR][Bot #1][03/23 08:13:36 AM]: Error in script executor! java.lang.IllegalArgumentException: bound must be positive at java.util.Random.nextInt(Unknown Source) at org.osbot.rs07.script.MethodProvider.random(ln:174) at aioLooter.CON.i(l:322) at aioLooter.CON.d(l:351) at aioLooter.AIOLooter.k(u:1869) at aioLooter.AIOLooter.onLoop(u:10) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(ol:278) at java.lang.Thread.run(Unknown Source) [INFO][Bot #1][03/23 08:13:36 AM]: [INFO][Bot #1][03/23 08:13:36 AM]: Thanks for using Fury AIO Looter! [INFO][Bot #1][03/23 08:13:36 AM]: ===== Results ===== [INFO][Bot #1][03/23 08:13:36 AM]: Time ran: 00:00:02:55 [INFO][Bot #1][03/23 08:13:36 AM]: Profit: 0 [INFO][Bot #1][03/23 08:13:36 AM]: Items looted: 0 [INFO][Bot #1][03/23 08:13:36 AM]: Successful loots: 0 [INFO][Bot #1][03/23 08:13:36 AM]: ===== Most Expensive Loot ===== [INFO][Bot #1][03/23 08:13:36 AM]: Name: null [INFO][Bot #1][03/23 08:13:36 AM]: Amount: 0 [INFO][Bot #1][03/23 08:13:36 AM]: Value: 0 [INFO][Bot #1][03/23 08:13:36 AM]: ===== Most Expensive Loot Missed ===== [INFO][Bot #1][03/23 08:13:36 AM]: Name: null [INFO][Bot #1][03/23 08:13:36 AM]: Amount: 0 [INFO][Bot #1][03/23 08:13:36 AM]: Value: 0 [INFO][Bot #1][03/23 08:13:36 AM]: [INFO][Bot #1][03/23 08:13:36 AM]: Script Fury AIO Looter has exited!

Khal tut island updated to V2.26: - Split up Default bot settings into seperate toggable options - Fixed several smaller issues - Fixed annoying Hide roofs game bug issue Note that the previously saved CLI files will not work anymore! Please save then again using the new system. Will be live soon! Khal

Go on some Discord shops, not gonna name any, and ull soon find fresh lvl3 with or without tut island completed for about 6 cents per account. And you can order then 100's at a time. Thats how I do it. No bans.

here we go again with you posting quality info and people replying shitpost or disregard. funny thing is the last time after all the gaslighting they finally listened to your findings and said to have changed mouse interactions.