Jump 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 04/16/13 in all areas

  1. Well, we might as well just put it our here. We have a massive goal set once again for this week. We've done that in the past and managed to more or less meet our goals within time. We will try to do the same thing this week, however this time it feels as if it's even more and the impact of these updates will make us the best bot out there if we manage to pull it off in time. So let's get to the list: Client related goals: [*]Find the source of invalid logins / unable to login / unable to connect to Runescape. This bug happens only to a select group of users, however we want OSBot to be public to everyone [*]Find the left sources of any freezing issues. I have not encountered it myself, but will try to reproduce the bug and profile it to find its origin. It's most likely a crash of the RS client itself caused by injected callbacks. [*]Fix up the skill hooks [*]Fix up the facing uid hook so we can return the proper facing entity [*]Add facing coordinates, x and y [*]Add the character chat messages, both force chat (used for randoms and such) and regular chat (used to write an AI to talk with other players in RS in the future) [*]Add the ability to provide the walking method with a collection of Position objects to create custom selfmade paths and lower overhead [*]Add a proper enum for hitsplats [*]Add a canReach method not only for entity, which we already have, but also for arbitrary Position objects [*]Find and fix the origin of non running onLoop() methods. This has occurred to me in the past, however not after last update, so we'll once again have to reproduce and find the cause. Non client related goals: [*]Finish up the SDN portal where script developers can login to maintain, update and submit their scripts. Set up the logic on the client and server to handle access to certain scripts (like premium scripts), automatic updates on random event handlers and a secure mechanism of providing the OSBot client with premium scripts that will prevent leaking to protect the creators of the scripts [*]Randoms, like we said, we aim to have most if not all randoms with their first version updated through the SDN once it's setup After writing this list I realized we should stop writing more and put the effort into real code! Yours sincerely, OSBot.org
  2. 2 points
    Ok guys, the bot should be back online!
  3. Someone asked me, so here //Imports herepublic class ScriptName extends Script { private static enum BotState = { STATE_1, STATE_2, STATE_3, STATE_4, STATE_5 }; private BotState state; public int onLoop() { state = setState(); // Method to figure out which state the bot is in return handleState(state); } /*************************************************************** * Method BotState setState() * returns ENUM - BotState * Use this method to calculate the state * Such as, if the players inventory is full * return BotState.BANKING ****************************************************************/ private BotState setState() { // Stuff here return BotState.STATE_5; } /*************************************************************** * Integer handleState * returns integer * Use this method to function * according to which state the script is in/ * Example: if STATE_1, RETURN 1000; (If the bot is in state_1, wait for a second. If not, look for another * state. ****************************************************************/ private int handleState(BotState state) { switch(state) { case STATE_1: //code return 1000; // Wait time before next onLoop() case STATE_2: //code return 710; // wait time before next onLoop() } }}
  4.    Really isn't much to show, if you get it you get it, if you don't you don't. It's very basic scripting and anybody who understands a hello world program using a switch would understand this. /: EDITED with slight comment adjustments
  5. 1 point
    for some reason i dont believe u are scripting this, post a proggy.
  6. 1 point
    Sorry guys for the recent downtime. We were changing our HTTP servers to fix some URL mod_rewriting issues. The forums is now back to normal. IRC Webclient now works: http://osbot.org/chat.html Rules can now be viewed: http://osbot.org/rules.html Thanks, Laz and the OSBot Team. P.S. We have had some users spaming private messages with malicious content. Please do not download anything from a PM unless you trust it. OSBot should ONLY be downloaded from our homepage: http://osbot.org EDIT: We have fixed all issues regarding the website and the bot now. Happy botting!
  7. Probably just some idiots. Don't know why Obama is taking this so seriously, it wasn't an international attack. They didn't send in planes to do the bombs. They were set and then put on a frequency and set off by a cell-phone. It's pretty sad though, an 8 year old died..
  8. Hi. -Obligatory section about how I'm me.- Bye.
  9. 1 point
    Is the server for the client down too?
  10. 1 point
    Yeah posting, PMing, you name is, all has seem to be fixed.
  11. i can feel my post count getting bigger!~~!@~
  12. int onLoop() { int rand = random(5) if(client.getMyPlayer().isMoving()){ if(rand <= 1){ client.typeString("DAMN 1 magic sucks") return 1000 + random(600) } if(rand <= 2 && rand >1){ client.typeString("GOD I HATE WALKING") return 1000 + random(600) } if(rand <= 3 && rand >2){ client.typeString("NEED TO TRAIN MAGIC NAOW") return 1000 + random(600) } if(rand <= 4 && rand >3){ client.typeString("WHY DOES THIS TAKE SO LONG?") return 1000 + random(600) } if(rand >= 4){ client.typeString("30 minutes cooldown on hometeleport? NO!") return 1000 + random(600) } return 600 + random(600) }else{ log("DONT WALK!") return 1000 } }
  13. 1 point
    Do you have any progress updates? I am really excited for this script
  14. 5/10 I beg to differ.

Account

Navigation

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.