Skip to content
View in the app

A better way to browse. Learn more.

OSBot :: 2007 OSRS Botting

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Leaderboard

Popular Content

Showing content with the highest reputation on 01/10/14 in Posts

  1. Two instances that you are using osbot.paul not 0sbot.paul You are clearly lying, also I have checked the ip that is using the skype osbot.paul and it is a 100% match to yours. Therefore you will be forced to pay back within 24 hours or you will be banned, which means you lose your VIP + all your scripts and have no access to the bot. Next time don't scam a few pixels that you can gain by using our bot within a few days. Also he doesn't need proof he is talking to you, when I matched the ip 100% that it is you.
  2. 6 points
    Dear community, We want to give you a heads up on OSBot 2. Over the past couple of weeks we ran into many problems with JavaFX. It turned out that JavaFX isn't mature enough for the job we are trying to pull off with it for OSBot 2. It made us decide to convert the GUI back to Java Swing. With this being worked on and almost being finished, you might be wondering what has been done and what is still left to do. I'll try to make an overview of the features in OSBot 2, both already implemented ones and ones that are still to be finished up. Green is finished, orange is not completed yet but nearly finished and red is not started on but planned. Asynchronous Script Engine (ASE). OSBot 2 has a new script engine. This engine is based on tasks that can be executed after events are being triggered, or tasks within tasks. The scripter has full control whether to keep newly created tasks to be executed within the task it's executed from, or dispatch the event to the engine which will execute the task asynchronously. The engine will take care of several multi-threading issues by itself and won't allow you to execute two tasks asynchronously that both use the keyboard, or the mouse. If not explicitly defined what mode to run tasks in, tasks that are executed from within tasks will be executed sequentially in the same thread. Scripters can however explicitly define to execute tasks from within a task that will be dispatched to the engine to be executed asynchronously. This gives a lot of control to scripters to perform logic on different levels where this is possible, for example mouse and keyboard control at the same time, or a background process listening to events that can be used to interrupt other tasks if necessary. This engine is ready and we have not found any bugs in it so far. OSBot 1 Script Converter (OS1C). OSBot 2 has full capability to transform OSBot 1 scripts to run on the OSBot 2 engine. The engine contains a skeleton for the OSBot 1 logic, which is wrapped into the OSBot 2 classes and adapted to use the OSBot 2 equivalent methods and classes. A transformer transforms the bytecode of the original scripts to match the skeleton, which can then be wrapped into the OSBot 2 logic. The logic of the scripts are then executed as blocking tasks within the ASE, benefiting of the improved power OSBot 2 has to offer. Injection, Wrapper and Callback system. The OSBot 2 injection is far more intelligent than its previous OSBot 1 counterpart. First of all it is designed to be completely undetectable by any sort of classpath check, if this would ever be implemented by Jagex (which would be a very efficient way of detecting bots). Doing this at loader level is much smarter than having to create a work around later which would be far less convenient. The injection system allows for far more efficient wrapping of the client hooks, lowering the amount of CPU and resources being used compared to the system in OSBot 1. Another improvement that was allowed by this new system is the way callbacks work. Callbacks now use significantly less resources and CPU. Client Synchronization. OSBot 2 is synchronized far more with the OSRS client. Where in OSBot 1 some things would be done out of synch with the loop cycle of the OSRS client, in OSBot 2 we have made sure they will communicate at the correct moment for caching or accessing data required by the OSBot 2 client. This means data is precise and accurate. Tab Monitors. You won't have to worry about monitoring your tabs anymore. Each tab is now represented by a miniature of the OSRS client image on the right side of the OSBot 2 client. With it you see information what account is logged in to it. On top of that, you have a screen where you can monitor all your tabs with larger images, approximately half the size of the original client per tab. Another thing we introduce, is rename-able bot tabs. There is still some work needed to complete on the GUI part of this, as we converted back to Java Swing. Separated Tab Consoles. Where is OSBot 1 you had 1 console with output from all your bots and on top of that the output of the OSBot 1 client itself, in OSBot 2 you will be confronted with separated consoles. One for the OSBot 2 client's output and one for each tab you are running. This will simplify tracking down problems or gathering much needed information. There is still some work needed to complete on the GUI part of this, as we converted back to Java Swing. OSBot 1's resemblance in OSBot 2. As you can understand we have kept all features in OSBot 1, but most of them have been rewritten or improved along the lines. The big difference with OSBot 1 is that the old features of OSBot 1 are now available within the ASE of OSBot 2. On top of that, the API presents more ready to go features that you won't have to write yourself anymore. API. The API has gotten a big overhaul in OSBot 2. Where the OSBot 1 API was written without a proper design in mind, the OSBot 2 API has been designed with great care. There is still work to be done to the API, but in terms of organization it's done. The API, as is the entire OSBot 2 structure, is very generic and very clean. Everything is separated in categories and all features are correctly divided amongst those categories. Besides that, the API contains way more conditional work, improved and new features. The API should be finished after this weekend. Bot Scheduler. OSBot 2 has a plan for a bot scheduler. This basically means you can setup a schedule for an x amount of tabs and schedule scripts in there attached to accounts. You can save this and load this, where all the work of opening the tabs etc will be done for you. You can schedule different accounts on different tabs, breaks etc. This can all be configured dynamically, meaning that if possible the scheduler will move one account to a different tab at randomized timing if preferred, to randomize the schedule. SDN. For OSBot 2 we have a new webpage for free scripts with SDN integration. You will be able to add and remove free scripts to your collection. For paid scripts, the old systems will still be used, however this might be changed in the future too. Another feature for the future might be paid script trials, where people could try out scripts for an hour. Security Manager. The security manager will be a feature that will block any file writes or reads to files outside the allowed directories, which will be the OSBot folder in your home directory. Further more the manager will block any use of reflection, bytecode analyzation tools (which would also be detected in the SDN verification process anyways) and access to the command line. This will effectively create a near 100% safe solution to prevent any malicious code being executed in scripts, especially when you know all scripts in the SDN are verified anyways. Other things that still have to be done. The OSBot 2 client still needs to get server and SDN integration. This is something that can be copied from the OSBot 1 client for the most part, however we have some changes made to the SDN system as mentioned above where we need to create some new code for. And now, after writing this giant wall of code I'm going back to my editor and pump out more code. Stay tuned, OSBot.org Edit 1: User Behaviour Profiles ANTI-BAN. For OSBot 2 we have been mind mapping what we can do to make two players, running the same script, behave in different ways. We will not openly discuss what aspects we have thought of and how we will implement this. But what we can do, is tell you that we have gathered towards 20 different aspects, that can safely be randomized and stored in a user profile. This means the chances that you will bot in the same way as another user, even though you use the same script, are very small. This system is something we wanted for a very long time but never got started to be written. WIth OSBot 2 being designed a lot more generically, we can implement this system even though most of the code for OSBot 2 is done, without too much extra effort. Bot Proxy Configuration. This will make a lot of people who use multiple accounts very happy. For each bot tab (you will be able to open them in a different way than usual) you can specify a proxy server configuration. This is something that is also going to be implemented in the Bot Scheduler, making your life very easy. Hiding behind proxies can save your accounts if you are running a farm.
  3. Gonna lock this thread now... turning into a bitch off instead of a script off. * Locked
  4. This script will allow you to show what OSBot users are currently using your scripts via a website. Setup is required and you will need website hosting and a MySQL database. MySQL Create a MySQL database, write down all the connection information and then run the following query: CREATE TABLE `online` (`id` int(11) NOT NULL AUTO_INCREMENT, `username` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `script` varchar(255) COLLATE utf8_unicode_ci NOT NULL, `time` int(11) NOT NULL, `ip` varchar(255) COLLATE utf8_unicode_ci NOT NULL, PRIMARY KEY (`id`)) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci PHP Upload the following package to your website and edit the 'include/database.php' file: http://uppit.com/8q7nlo4h998w/online.zip Note: Edit the key in the index.php file. Java Add a class to your script called: Online.java and paste the following code in it: http://pastebin.com/raw.php?i=2j9TDdHW Note: Don't forget to edit the key and php information. Now, add the following imports to your script: import java.util.Timer; import java.util.TimerTask; Add the following at the start of your scripts class: Timer timer = new Timer(); String script = "SCRIPT NAME"; Add the following to the start of your onStart method: log(Online.add_user(client.getBot().getUsername(), script)); timer.scheduleAtFixedRate(new TimerTask() { @Override public void run() { Online.add_user(client.getBot().getUsername(), script); } }, 0, 60000); And the following to your onExit method: log(Online.remove_user(client.getBot().getUsername(), script)); timer.cancel(); Usage! $online = json_decode(file_get_contents('http://YOURSITE.COM/online/index.php'), TRUE); //show every user and the script they are using foreach($online as $user) { echo $user['username'] . " : " . $user['script']; } //show total online user count echo count($online); Note! It's 3am, i'm tired and iv probably made a few mistakes. Please just post if you notice any errors or mistakes so i can get them sorted out.
  5. So i got asked to create a script that will allow script developers to show the username of accounts using their scripts. This was done by sending secure POST calls to a PHP script that then stored the usernames in a database. Showing the usernames of OSBot users using your script is a stupid idea ? well simply just show a count of online users! I will be releasing this publicly once i do a little more testing.
  6. 2 points
    do you feel the urge to suck a dick?
  7. User is banned, clearly lied about sending the money, failed to send a picture, and then made another excuse without defending him saying "sent the money".
  8. Crafting account A/W - 3m SKYPE: Joshua.osbot No bans No recovery's Comes with email Original owner 28 Days membership left ​ # Stats # Bank # BANS
  9. 1 point
    Dear community, This release contains the fix for the walking. The download can be found here: http://www.osbot.org Sincerely, OSBot.org
  10. this is my main account I am selling, personally I have really enjoyed playing on it - and I hope the buyer will too. It is a very well balanced account so there are high level skills as-well as combat. I am the original owner of this account, and I am accepting OSRS money only - I will expect the money first before; I hand over account details and pin number - however this can be discussed over Skype. I am open to offers
  11. You are getting banned for clearly lying. You were on the skype that is the only ip that has been on that skype and your Osbot account. Pay him back or you will be banned and lose access to the bot. Stop lying you have been matched 100%
  12. Bye

    1 point
    Gonna miss you releasing new beast scripts making the paid ones shit :P anyways have a good life
  13. I can do it for 300k, pay me after i dont mind:) skype : smurfinzo
  14. You need an "anti ban" that is completely random to each user. Due to how Jagex anti botting system is currently getting better and better and how they read on patterns and behaviours that are repeated over and over we need more than just "check skills every 5 mins" "click this every 2 mins" ect. If anything this would get us banned even more due to it being a repeated process that everyone would be doing and not random at all. It needs to be more complex, like using different walking tiles to get to a certain point every single trip.. ect. Traditional anti ban's made by scripter offer absolutely nothing and are a joke, anyone experienced in gold farming and botting knows this. ^^ Guy above me gets it.
  15. Everyone who's been in the scripting scene for a long time know these "Anti-ban methods" have no effect on Jagex recognizing that you're a bot. If you want to have a true impact on the ban-rate you're going to have to come up with something much more drastic. I've been looking into other botting sites for quite some time now and it seems the most successful approach so far is to create unique botting profiles for each user, and to make each script perform differently based on this profile.
  16. I doubt this is the case when other players around you try to interact with you, for example when talking to you.
  17. 1 point
    I'd enjoy it if you calm down basic, I'm closing this weekend because 2 other people contacted me saying they'll contribute. I don't see any problem here, it's not my fault no one entered for a whole week before this either, time for you guys to be a bit patient.
  18. 1 point
    Well I PM'd Maldesto and he told me I couldn't make an auth system similar to Alek's because he works for "free". I just want to help out future script writers by having this clearly stated in the rules instead of saying could happen.
  19. http://forums.zybez.net/runescape-2007-prices/820-yew-logs
  20. Easy sell for more. Goodluck Wrong section by the way; http://osbot.org/forum/forum/30-items/
  21. Oh NVM, okay man sounds good bro i just have to renew 2 scripts next month than daym this is better then other bots out there haha it's just 1am in aussie land didnt see that part =D
  22. 1 point
    Please scan your computer, and please realize that using other bots or playing private servers before ours means that you could still be infected from them, just because they acted today doesn't mean you weren't infected 2 weeks ago or 2 months ago.
  23. no longer need thanks satan
  24. Whenever anyone views the online users it quickly updates the database and removes any entries that haven't been updated in 2 minutes.
  25. kWarriors, kGiants, kOgres. You can use any of those for free to get your 70 strength real fast.
  26. This looks really cool seeing the code, shame I don't have a clue what 95% of it means!
  27. 1 point
    just purchased the script, buying buckets as of now. heres a suggestion: you should add an amount of buckets you want to buy? just so the players wont overspend their money working good for now awesome script, worth the money!
  28. Something like that. I just think that they have no high resources to investigate closely did they really made up profit etc, so multiple accounts from the same ip no matter what you bot = gold farm
  29. Why would I have to go into my paypal to cancel payments. It is their responsibility to stop charging me once I cancel it on here.
  30. I hope I win too, this script is too awesome from one of my favorite movies
  31. 1 point
    GREAT!!!! Thanks!! Give us a tease please. short 1minute video. (60 second video!) Show us a little nipple or something?? Thank you
  32. Feedback removed. You cant give negative feedback because someone else gave you negative feedback. This isn't a kindergarten. * Locked * Moved to archive
  33. 1 point
    Nice, any ETA?
  34. Might possibly accept paypal and yes I'm original owner
  35. Add my Skype (in signature bottom right).
  36. 1 point
    Also, you have another 24 hours for spamming my inbox. I don't have time to deal with your spam a thread is enough not 5 messages on skype + spam pm.
  37. I am the original owner, main quests done are : mm/heroes/d slay/lost city/ and has addy gloves from rfd. will give any other info you may need. 1. Pictures of the account stats http://gyazo.com/35eff1c43583776b41efa1e1a7d62d3a 2. Pictures of the login details http://gyazo.com/0ca056c6a2ab4d37c8a98c5dc0 3. Pictures of the total wealth (if there is any) There is no wealth 4. Pictures of the quests completed http://gyazo.com/a04338c3d47b54d59e7119f7a352196b 5. The price you will be starting bids at : 5M 6. The A/W (Auto-win) for your account : none 7. The methods of payment you are accepting : Accepting 07 gp or Paypal 8. Your trading conditions : Will use a MM unless you are trusted 9. Account status : http://gyazo.com/107bb22ae8535c41403cccccf1dddb65 10. Original/previous owners/Original Email Address : Original Owner
  38. Need to update. Jagex just updated it so there's a smith 'x' option.
  39. 1 point
    Just sell the account.
  40. ^ Very clear and respectful, thank you I have added a TOS to my sales page, and will refer if I am buying an account or if it ever occurs again!
  41. bought a voucher twice this week, just quick and easy trade, would recommend.
  42. Mate you PM'd half the kids I know saying "I bet swizz is mad because I'm releasing all his scripts free" and then bitched me out over PM... Why can't we have a little fun?
  43. 1 point
    Satan is a retard this account is worth 12m max
  44. I don't fight for banned accounts because I think if I do they will have reason to look into the account and realise I have 20 other accounts coming from the same I.P. as that one and then all shit gets fucked.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.