Leaderboard
Popular Content
Showing content with the highest reputation on 04/07/19 in all areas
-
Made an earlier post about how all OSBot scripts seem detected, and posted some findings relating to the banrates of changing various things such as timings, clickspeed, movement, and mouse DPI. In testing, I found that almost 100% of all OSBot's mouse movements follow very simplistic patterns that are picked up very quickly by Jagex's anti-bot. This goes for ALL other client's I've tested, all containing some flaw within their mouse movement, whether it be [Other-Bot-Client]'s flawed inaccurate spoofed mouse movement, or [Other-Bot-Client]'s consistency. I've reported these flaws to the developers of OSBot already, but was not met with confirmation on whether or not they'll do anything about it. Possibly because they're still under the illusion that mouse movement doesn't play a big role in detection. So here's a topic to prove just that. First off, let me start by showing that Jagex certainly does record mouse movement: https://github.com/zeruth/runescape-client/blob/master/src/MouseRecorder.java#L40 This shows the frequency of their collection. 50MS ticks, which is equivalent to 20 times a second. Now you could say.. But isn't 50 MS not enough to accurately depict mouse movement? And that is true to some extent, but it's more then enough data to analyse in order to find flaws or patterns. Here's what it looks like to move a mouse on a 50MS tick-rate: https://i.gyazo.com/4eb9de90c1c8a60959e874fb24488ab3.mp4 A common argument may be that collecting mouse movement is an absurd amount of data, but.. They combine the integers into mostly a 2 byte for small/medium, and larger a 3 byte or 4 byte and save/send it as that. That means they can store around 250,000-500,000 x/y captures per 1mb. That translates to around 3.4 HOURS of constant mouse movement data capture per user. That data would obviously build up over-time, but IMO Jagex most likely clears this data either every ban-wave, or every week. Which wouldn't really be that much. You could also compress these integers an insane amount due to how primitive the encoding would be. They also only send movements, not equal, or zero movements: https://github.com/zeruth/runescape-client/blob/master/src/Client.java#L3330 - Although, they still keep track of those equal/zero movements: https://github.com/zeruth/runescape-client/blob/master/src/Client.java#L3332 So we can see they record the data locally, but do they send it to the server? The answer is, yes. Here's proof of that (Annd they send a loot more then just that...): https://github.com/zeruth/runescape-client/blob/master/src/Client.java#L3307 And here's them encoding the difference between mouse x/y movements into a 2 byte integer and appending it to their packet buffer (Only medium speed movements under about 31 pixel per 50MS): https://github.com/zeruth/runescape-client/blob/master/src/Client.java#L3342 And here's them encoding movements into a 3 byte integer and appending it to their packet buffer (var10 = mouseY * 765 + mouseX): https://github.com/zeruth/runescape-client/blob/master/src/Client.java#L3345 And here's them encoding movements into a 4 byte integer and appending it to their packet buffer (var10 = mouseY * 765 + mouseX):: https://github.com/zeruth/runescape-client/blob/master/src/Client.java#L3348 They also can detect when you move your mouse outside of the screen, and how many ticks (Ticks are capped of course): https://github.com/zeruth/runescape-client/blob/master/src/Client.java#L3324 Reconstructing their mouse collection: ||) Equal, or zero movements are tracked by ticks. If you don't move your mouse for 30 ticks, they'll know. They most likely use this for multiple purposes, the biggest being the ability to figure out the entire mouse movement rather then just bits of it. 1) Movement of the mouse is tracked, smalls/medium movements exactly by this (Only medium/small per-tick movement difference under about 30 in length) int yDiff = (recordedY - previouslyRecordedYMove); int xDiff = (recordedX - previouslyRecordedXMove); handler.packetBuffer.putShort(yDiff + (idleIndexesPassed<< 12) + (xDiff << 6)); idleIndexesPassed = 0; movementIndex = the indexes skipped before finding a mouse move in the X/Y mouse recorder. Used to track time between mouse movmenets. 2) Larger movements that are made in less then 8 ticks of "idle" mouse: (Actual location sent) int var10 = (recordedY * 765 + recordedX); handler.packetBuffer.put24bitInt((idleIndexesPassed << 19) + var10 + 8388608); idleIndexesPassed = 0; 3) Large movements that are made 8+ ticks from being "idle" (Actual location sent) int var10 = (recordedY * 765 + recordedX); var14.packetBuffer.putInt((idleIndexesPassed << 19) + var10 + -1073741824); idleIndexesPassed = 0; (Don't mind the -1073741824 or other random numbers. Java doesn't support primitive unsigned numbers, so you have to use hacky stuff to compress your integer sizes) The majority of OSBot's movements would fall under #1's logging. The others are just for larger mouse movements (in terms of last X/Y -> new X/Y). Why do they multiple Y by 765? Because they've capped the X axis from exceeding 764 therefor they can easily mathematically combine the two integers for saving resources, then de-couple them whenever they want. So what does all this have to do with OSBot's mouse movement? Well, I performed a basic test to grab the mouse movement delta's between every 50MS tick (Just as Jagex does) and found 100% consistency among certain parts of their mouse movement patterns: OSBot's mouse movement: https://pastebin.com/AJn2NC31 My own mouse movement: https://pastebin.com/vnGtX16z Right away you should notice many flaws inside OSBot's mouse sample. As you can clearly see, OSBot repeats ONLY 4-5 at the end of movements, AND at the last few deltas at the end of the movement, it goes from Lower, Bigger, Lower, This seems to be the case with virtually all mouse movements over 4-5 pixels large made by OSBot. So if I'm able to detect this flawed mouse movement in a matter of seconds with basic math, then so can Jagex? This would also explain why tasks requiring massive amounts of mouse movement, such as agility, have much higher ban-rates vs something like fighting, or AFK tasks. Does this mean this is the only detection method banning OSBot? Absolutely not. However, in my experience, I've yet to be banned by using OSBot as an API for everything BUT mouse movement, or camera movement (Of course with a lot more human-like behavior sprinkled on top of the scripts). This is purely based on only a little more then a week of botting without a ban, so it's possible I'm not bypassing, but simply delaying my ban. Hell, it's possible I was detected the second my script first started and now i'm just riding a monthly ban wave. Still beats a daily ban wave though...4 points
-
I don't really see anything wrong with this. I think most people in this forum are very pessimistic about anti-ban. That's partly due to Alek's own beliefs that spread. But It's better to explore stuff and try it out. Who knows what works and what might not work. Yes, these same things have been tested but not all tests are the same and something new could be discovered. So yeah, just do you and try out new ways of anti-ban.2 points
-
Not only did I already tell you I believe mouse movement can be used for detection - all be it only a very small part of the system -, I also told you it's something we're interested in changing and are discussing. From months of testing I can confirm that you can bot without getting banned when botting 4+ hours almost everyday, when only using the OSBot API.2 points
-
Thank you everyone for all the support and feedback, this script officially is the most sold magic script on the market! Since 2015 it has been continually updated all the way to 2025! #1 SOLD MAGIC SCRIPT #1 MOST FEATURES MAGIC SCRIPT ESC MODE, HOVER-CLICK, NEAREST ITEM CLICK, FLAWLESS JMod nearby and we still alive. Anti-ban and Optimal script usage Anti-ban: - Don't go botting more than 3 hours at once, take breaks! Otherwise the ban-rate is highly increased! - Bans also depend on where you bot, for the best results: bot in unpopular locations Banking-related spells are the lowest ban-rate (spells which require banking or can be casted near a bank, e.g. superheating, maybe alching, jewelry enchanting etc etc) since you can just go to a full world and blend in with other non-bots (humans), for example: world 2 grand exchange If casting spells on npcs, then unpopular locations reduce the banrate by alot, So make sure not to go to botting hotspots otherwise you may be included in ban waves. - Some good areas used to be (until some got popular): grizzly bear, yanille stun-alching, any overground tiles (upstairs etc) but once the areas are overpopulated, try to go to another location which is similar to the aforementioned locations. This is a very popular thread with many many users so if a new location is mentioned, the location will be populated very quickly so I can only suggest examples of good locations - Don't go botting straight after a game update, it can be a very easy way to get banned. Wait a few hours! If you ever get banned, just backtrack your mistakes and avoid them in the future: you cannot be banned without making botting mistakes. Keep in mind you can be delay-banned from using previous scripts, so don't go using free/crap scripts for 24 hours then switching to a premium script, because the free/crap previous script can still get you banned! For more anti-ban information, see this thread which was created by an official developer: http://osbot.org/forum/topic/45618-preventing-rs-botting-bans/1 point
-
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.1 point
-
────────────── 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.1 point
-
1 point
-
View in store $5.99 for lifetime access _____________________________________________________________ Key Features: Progressive mode - The script will traverse the xp-optimum course for your current level; walking to the next course as your level increases. Reliability - The script was developed and rigidly tested with superior reliability in mind. Human replication - Designed around human simulation - behaviour tuned to replicate common rooftop play styles. Alching / Magic Imbue - The script can be configured to High/Low Alch items, or cast Magic Imbue as it traverses the course. Target system - Can be optionally configured with a target. Once this target is achieved, the script will stop. Available targets (variable λ): Stop when λ agility exp gained. Stop when agility level λ reached. Stop when λ magic exp gained. Stop when magic level λ reached. Stop when λ minutes passed. Healing - The script will consume edible items in your inventory to restore health, stopping if you run out of food. Mark of Grace looting - All marks of grace are looted while the script traverses the rooftop. Randomisation - All thresholds (including but not limited to Run energy and Critical Hp) are dynamically randomised. Energy restoration - The script will consume energy restoring items/potions when needed, provided they are available in the inventory. Web-Walking - The script utilises the OSBot Web to navigate the OSRS map, meaning it can be started from almost anywhere. Course detection - If you are on/near a rooftop course before setup, the course will automatically be loaded into the GUI. Error correction - The script will detect when it has made a mistake (e.g. climbed ladder in seers' bank) and will attempt to return to the course. ...and many more! Supported Rooftops: (Level 10) Draynor ✓ (Level 20) Al-Kharid ✓ (Level 30) Varrock ✓ (Level 40) Canifis ✓ (Level 50) Falador ✓ (Level 60) Seers' Village ✓ (Level 70) Pollnivneach ✓ (Level 80) Rellekka ✓ (Level 90) Ardougne ✓ Things to consider before trying/buying: Avoiding bans - while I have done my utmost to make the script move and behave naturally, bans do occasionally happen, albeit rarely. To minimise your chances of receiving a ban, I would strongly suggest reviewing this thread written by the lead content developer of OSBot. If you take on board the advice given in that thread and run sensible botting periods with generous breaks, you should be fine. That being said, please keep in mind that botting is against the Oldschool Runescape game rules, thus your account will never be completely safe and you use this software at your own risk. Web-walking - alongside a network of paths, the script moves around with the OSBot web-walking system, using it when in unknown territory. While it has proven very reliable, there are naturally some areas for which the web-walker may struggle. As a result, prior to starting the script, I would strongly recommend manually navigating your player to/close to the desired rooftop course. Progressive mode - the script features 'Progressive mode' which will cause the script to advance rooftop courses as you level up. Progressive mode relies on the aforementioned web-walking system for inter-rooftop navigation. Consequently, I would highly recommend monitoring the script as it traverses between courses to ensure the web-walking process correctly executes. Healing & Energy restoration - the script will automatically heal or restore run energy when needed. It will do so by consuming items in the inventory - this script will not bank. For optimal exp rates, I would strongly suggest keeping energy restoring items in the inventory (energy/super energy/stamina/fruits/summer pies/purple sweets/...). To prevent the script stopping prematurely, bring a few bites of food along. Using magic - The script supports the periodic casting of a magic spell while traversing a course to maximise experience rates. To determine whether or not you can cast a spell, the script checks your magic level as well as which runes are in your inventory and which stave you have equipped (if any). It is worth noting that, at this time, the script does not recognise any of the following items as rune sources, so avoid using them while running this script: Bryophyta's Staff, Tome of Fire, Rune Pouch. Script trials: I believe that trying a script before buying is paramount. After trying the script, hopefully you will be convinced to get a copy for yourself, but if not you will have gained some precious agility experience! If you're interested in a trial, please follow the instructions on my trials thread which can be found here. Gallery: Review (by Eduardino): Start up GUI (Graphical User Interface): Paint (optional, movable and self-generating): User screenshots: Testimonials:1 point
-
Want to purchase? Click here! For trials please join the discord and request one using our discord bot! Easy To Use GUI By enabling the custom area you can actually chop any tree anywhere in RuneScape with full banking support! You can automatically sell your logs to the grand exchange and wake up in the morning to Gold instead of Logs! Just follow these easy to use instructions! Grand Exchange Support Instructions: Please follow these instructions for the GE support. Depending on your area you will be required to have specific items in either your bank or your equipment , the list follows: To go to the Grand Exchange for all areas EXCEPT Varrock West, Varrock East, Draynor, Lubridge and Falador, you will be required to have Varrock Tele Tabs in your bank to travel to the Grand Exchange. However if you are chopping in these areas and have a Varrock Teleport Tab you will still use it to get to the Grand Exchange. The requirements for Traveling back follows: Draynor: If you have a glory in your equipment you will use the glory, if not, you will walk back to Draynor. Falador: If you have a Falador Teleport Tab in your bank, you will use the teleport tab, if not, you will walk back to Falador. Seers/Catherby: You will be required to have a Camelot Teleport Tab in your bank to travel back to Seers or Catherby Castle Wars: You will be required to have a Ring of Dueling on your equipment to travel back to Castle Wars. Barbarian Outpost: You will be required to have a Games Necklace on your equipment to travel back to Barbarian Outpost. Woodcutting Guild: You will be required to have a Skills Necklace on your equipment to travel back to the Woodcutting Guild. NOTE: The Grand Exchange will not be supported if you are using the customized areas. Powerchop Instructions: If you would like to use the powerchopping feature with shiftdropping please ensure that you have these settings enabled. The bot will not check/change these settings for you. If you enable powerchopping without shiftdropping or without changing the in game settings it will not shift drop for you. Progressive Axe Instructions: If you use the progressive axe feature you MUST have the required axe for the levels in the bank or it will not work! If you use the progressive axe feature and you reach level 41 and you do not have a rune axe in your bank the bot WILL STOP! This is not just for level 41. This is for ALL LEVELS that an axe must be upgraded. If you use the progressive axe feature it will ignore the selected axe in the drop-down box This feature DOES NOT work with bronze axes. Only use Iron or better. Progressive Mode: If you have progressive mode selected the bot will run this order: Woodcutting level 1-15 Chopping Normal Logs at Varrock West Woodcutting level 15-30 Chopping Oaks at Varrock West Woodcutting level 30+ Chopping Willows at Draynor. The bot will automatically walk to Draynor with no user interactions! WARNING: If your combat level is under 15 the mage in Draynor can attack you! I suggest only using this feature if your combat level is 15 or above. Progressive mode will not have the GE Support but it will include the Stop Level feature. Many Preset Locations Supported: Normal Trees: Varrock West Lumbridge Oak Trees: Varrock West Varrock East Castle Wars Seers Falador Willow Trees: Draynor Seers Barbarian Assault Maple Trees: Seers Woodcutting Guild Teak Trees: Castle Wars Yew Trees: Grand Exchange/Varrock Palace Edgeville Catherby Seers Woodcutting Guild Magic Trees: Seers Woodcutting Guild I am open to include more areas if they are requested. Just let me know and I will work on including them! Bug reports: What is the bug? How did the bug happen? What does the OSBOT logger say? Injection or Mirrored? PROGGIES:1 point
-
Before buying, please ensure you check-out with the correct script. Swapping scripts is not possible. View in store $4,99 for lifetime use - Link to Sand Crabs script thread (better exp/h!) - Requirements: Camelot tabs / runes in main tab of bank Designated food in main tab of bank ~ 20-30+ combat level Features: CLI Support! (new!) Supports Ranged & Melee Attractive & fully customisable GUI Attractive & Informative paint Supports any food Custom cursor On-screen paint path and position debugging Supports [Str/Super Str/Combat/Super combat/Ranged/Attack/Super attack] Potions Collects ammo if using ranged Stops when out of [ammo/food/potions] or if something goes wrong Supports tabs / runes for banking Option to hop if bot detects cannon Global cannon detection Option to hop if there are more than X players Refreshes rock crab area when required Avoids market guards / hobgoblins (optional) Automatically loots caskets / clues / uncut diamonds Enables auto retaliate if you forgot to turn it on No slack time between combat Flawless path walking Advanced AntiBan (now built into client) Special attack support Screenshot button in paint GUI auto-save feature Dynamic signatures ...and more! How to start from CLI: You need a save file! Make sure you have previously run the script and saved a configuration through the startup interface (gui). Run with false parameters eg "abc" just so the script knows you don't want the gui loaded up and want to work with the save file! Example: java -jar "osbot 2.4.67.jar" -login apaec:password -bot username@[member=RuneScape].com:password:1234 -debug 5005 -script 421:abc Example GUI: Gallery: FAQ: Check out your own progress: http://ramyun.co.uk/rockcrab/YOUR_NAME_HERE.png Credits: @Dex for the amazing animated logo @Bobrocket for php & mysql enlightenment @Botre for inspiration @Baller for older gfx designs @liverare for the automated authing system1 point
-
import org.osbot.rs07.utility.ConditionalSleep; import java.util.function.BooleanSupplier; public final class Sleep extends ConditionalSleep { private final BooleanSupplier condition; public Sleep(final BooleanSupplier condition, final int timeout) { super(timeout); this.condition = condition; } public Sleep(final BooleanSupplier condition, final int timeout, final int interval) { super(timeout, interval); this.condition = condition; } @Override public final boolean condition() throws InterruptedException { return condition.getAsBoolean(); } public static boolean sleepUntil(final BooleanSupplier condition, final int timeout) { return new Sleep(condition, timeout).sleep(); } public static boolean sleepUntil(final BooleanSupplier condition, final int timeout, final int interval) { return new Sleep(condition, timeout, interval).sleep(); } } Usage: Sleep sleep = new Sleep(() -> myPlayer().isAnimating(), 5000); sleep.sleep(); Or: Sleep.sleepUntil(() -> myPlayer().isAnimating(), 5000);1 point
-
1 point
-
Oh yeah you can for sure make it better than the barebones example I gave, was just trying to illustrate the point that this isn’t something without a solution that’s impossible to figure out.1 point
-
I think the important thing to take away here is that they do at least send the mouse data to their servers, it doesn't look very human, and if they wanted to they could use this as one of many metrics to detect bots. That alone should be enough to encourage a change, whether it be in the way OSBot itself handles mouse movements or by us scripters to handle movement ourselves.1 point
-
Some people refer to me as the Chad of Runescape botting. What do I do to get so swole you may ask, it's simple. I hover over my woodcutting skill no matter what I do, all these people are trying complex calculations to figure out the secret, but they've all left that one method, which has flawed all their research.1 point
-
Yep, just doing a few more test runs and I will push the update for delays and some tweaks for banking. As for gems, I will offer a few more options/customization for them, including an option for deposit box, should be more convenient to all users. Activated trials good luck guys, will activate double trial time since a new update is on the way. :D As for moving mouse out of screen, not yet but I can convert some code from my fighter scripts and add it to the motherlode script.1 point
-
How dare you suggest it's his testing method which is flawed?1 point
-
You mean the picklock door at chaos druids north of ardougne? As for trials, activated good luck. New update is going live today within a couple hours1 point
-
1 point
-
The discussion about what happens to the mouse data thats being sent to the server, is something that has been going on for years. In the end, everyone is just guessing1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
If I recall correctly, what you're looking at is Jagex's class checker. They are sent classes to check for from the server and reply back with having it or not. A friend of mine has logged a few of the classes they asked for and it seems to be classes related to the actual client, nothing external. They can't detect what client you're using, but knowing whether you're using an official OSRS client or not isn't hard to spoof if you know what you're supposed to change. It doesn't matter whether the client is reflection or injection.1 point
-
@CzarPlease help - I am trying to use the bot it seems to get stuck on picklock doors, it will not pick the lock on the door instead just constantly clicks on the door to try and open it how can I fix this?1 point
-
1 point
-
"We are talking about a bot...a macro to do an automated repetitive task." - Yeah "repetitive task". You mean the very task required for literally any skill on OSRS? You think mining iron, banking, mining iron, banking without botting isn't repetitive....? What's your arugment lmao I think you're completely misunderstanding me and instead think I'm attacking OSBot... I'm not, I'm actually trying to improve OSBot. If I was bashing it, I sure as hell wouldn't still be using it as there are many alternatives. What I said and provided is undenyable proof. If you honestly believe that the samples created from using OSBot's mouse isn't very easy to detect then you're delusional and need to seek help. It's not about being advanced.. The current movement is advanced, and even has deviation in it's mouse movement.. However, the developers who made it probably were more focused on making it LOOK human, rather then trying to see if they themselves could pickup on the pattern. So why make this post? To bring attention to this issue... As simple as that. I've provided more then enough evidence/samples that Patrick should be able to make the necessary changes within OSBot to reduce, or remove this highly flawed mouse movement. Why did I "bash" on using 100% of OSBots API? Well for starters, I wasn't TRYING to, I was simply providing that I myself now suddenly bypass after changing the mouse moving functionality... It was an example to further my claim, which IMO, it has.1 point
-
From the top of my head, I remember coins, leather gloves, leather boots, broken arrow. For the trowel digging, all I remember is broken staff maybe.1 point
-
I was doing the same with messages, didn't want to clog up the thread with videos and reports of the same. But yeah, thanks a heap, will give fixed a go now. Thanks for your help, it really is appreciated Cheers, Tesh.1 point
-
1 point
-
1 point
-
Here's a utility to sample mouse deltas: public class MouseDebugger { private int tick = 0; private int lastMouseX = 0; private int lastMouseY = 0; private boolean endedMovement = true; private int noMoveTicks = 0; private Script script; public MouseDebugger(Script script) { this.script = script; } //Run this on a 50MS tick, or whatever you want to sample on public void tick() { final Point mosePosition = script.mouse.getPosition(); if (lastMouseX != mosePosition.getX() || lastMouseY != mosePosition.getY()) { double actualDistance = Math.sqrt((lastMouseY - mosePosition.getY()) * (lastMouseY - mosePosition.getY()) + (lastMouseX - mosePosition.getX()) * (lastMouseX - mosePosition.getX())); if (actualDistance > 0 && actualDistance != Double.NaN) { script.log("Delta: " + actualDistance + " Tick: " + tick); } endedMovement = false; noMoveTicks = 0; } else { ++noMoveTicks; //Change according to how long you pause until making another mouse movement if (noMoveTicks >= 6) { if (!endedMovement) script.log("--Mouse movement ended"); endedMovement = true; } } lastMouseX = (int) mosePosition.getX(); lastMouseY = (int) mosePosition.getY(); ++tick; } }1 point
-
Just ran the Dig Site quest, only issue that it ran into was when the script was pickpocketing the workmen for the animal skull, it would drop the item that it didn't need but wouldn't drop all of them so it would fill up the inventory and still tried pickpocketing. Also the part when using the trowel on the soil to find the emblem its the same exact issue, it digs up the items it drops some but forgets some items and it ends up filling the inventory and still tries to dig the soil for more but can't because the invent is full. Besides these issues it ran nicely. Ran in mirror mode1 point
-
1 point
-
I will add a slider for speed so you can determine the best speed for you, the server ping must be factored in too so I can't depend on a single fixed speed. Update coming up.1 point
-
New Update (v241) - Trident support added, in magic pop-up - Updates for potion sipping, should work better - Added more areas in corsair cove - Added tweaks for npc detection (initial setup) - Teleport runes working again - Npc bound fixes for cannoning - Cannons can no longer be added to bank layout anymore, should fix a few bugs - Added improvements to 'can_we_fight' checker (cannon mode), so it should know whether to fight or bank - Added a few improvements to eating, and stronghold - will need some more testing to confirm. - Food handler no longer gets stuck and causes dying anymore, death bug fixed. Update will automatically go live within 24 hours, just doing some more testing and I will be pushing the update to SDN. After it's pushed it will go online Thanks guys! Looking forward to the next update1 point
-
1 point
-
Added 5 new quests on the GUI (56 quests supported now) Biohazard Nature Spirit The Corsair Curse The Dig Site X Marks The Spot Let me know if there are any problems. If everything's alright, I've got another 5 ready1 point
-
1 point
-
I think you have a few false premises. One of them being that Jagex bans manually. Jagex has stated that they've banned over 300k accs in one month previously. If they spent at least 1 minute per account they'd need over 5000 hours of work every month to review that many accounts and ban them. Most of the detection and flagging is already automated, Weath just has to press the button or run whatever program to ban most of them, I'd say a very small percentage of the accounts actually get reviewed.1 point
-
Heya, It's on my list of things to do, but i'm just waiting until they release the changes to Zeah mapping before working on this so that I can do both at the same time Apa1 point
-
1 point
-
1 point
-
yeah maybe add a delay. i mean runelite can figure out when the ore spot is gone, so i assume osbot has the api possible to do so. another piece of feedback, the clicking back and forth between the paydirt sack and the bank is aweful. it moves the camera wildly and the clicking is so inaccurate. maybe use the minimap to click near the bank? (instead of getting the bot to move jthe camera to click near the chest). OH, also after the bot pays dirt, can you make the bot deposit any gems that are in the inventory (before it goes back to mining in the east area (if agility shortcut option is turned on?). That'll make it way more efficient! oh , deposit via the bank deposit box instead of the chest. its faster as well1 point
-
1 point