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

  1. Dylan

    Trade With Caution
    11
    Points
    2949
    Posts
  2. Jordan

    Java Lifetime Sponsor
    11
    Points
    26997
    Posts
  3. Smart

    Ex-Staff
    10
    Points
    5276
    Posts
  4. Laz

    Suspended
    10
    Points
    775
    Posts

Popular Content

Showing content with the highest reputation on 02/12/14 in all areas

  1. brb ill go find out for u.
  2. Normally, there's not much we can do against account scammers. It's virtually impossible to stop them from recovering the account and users who are unaware of them end up getting scammed, unfortunately. The staff keeps coming up with restrictions trying to stop scammers dead in their tracks, but this can often prove to be extremely difficult. However, I have a suggestion that can affectively stop repeat scammers. With account selling scammers, I suggest there be made a blacklist thread in the accounts section. This thread will contain the LOG-IN name or e mail of every account recovered. It will publicly be displayed upon the closure of a scam report resulting with the decision that the seller has recovered the account, regardless of whether the money was refunded to the buyer or not. Although the display name (in game name) can be changed, the log in name can never be changed and is unique for every account. With that being implemented, giving that buyers actually read it, it can stop repeat scammers from selling and recovering the same account over and over again. I would also like to add an extra layer of security by having accounts verified (preferably by a staff member or someone with a verified transact or rank) that the account the person is selling hasn't been blacklisted. I'm not sure if this would help out so much, but it might. I can see users trying to take advantage of that and trying to scam saying the account is verified, but it's just a mini suggestion. My next suggestion would be to create a similar thread in the gold selling section with paypals that have chargedback in the past and have been proven guilty and the user banned in a valid scam report. If the above is implemented, and scammers continue scamming, we will shortly have a database of scammers and their accounts which we won't trade with. I know a new scammer can always come and scam, but with this list we can affectively cut out repeat scammers. Once someone gets banned for scamming, they will more than likely create another account to ban evade on to scam again. It's not really easy to catch a random ban evader and you never know how many there are, so this suggestion can prove very useful if action is taken. If this is accepted, all MM's should refer to the blacklisted accounts before continuing through the trade. This can prove to be a very beneficial aspect of the market. With that said, I'd like to hear your thoughts about it and any concerns you may have.
  3. As we've stated many times and times again, the RuneScape client itself uses the most CPU within the OSBot environment. Due to this, I've recently been playing around with methods that can be skipped in the client it-self that will lower the burden the client has on performance. One of the newest features that will be available to OSBot 2 is the "disable client rendering" toggle right next to the "low cpu" toggle. Here it is in action: As you can see, the client is logged in and works normally with the exception that the 3D world is not drawn at all. At the moment this only disables the client's rasterizer (the part of the client that converts 3D points to 2D points and draws them). The client still performs other model calculation data in the background (for calculating menus and such). The feature is undetectable and the bot is able to interact with the client exactly the same way as if the screen was actually drawn. We're planning on further adding more CPU saving systems to the client in the future. Thanks, Sincerely, Laz and the OSBot Team.
  4. 2 points
    Preferably hot with a nice rack.
  5. 2 points
    ITS NOW OMG RUN FOR YOUR LIFE HOLY SHIT
  6. First of all, just wanted to say that this is common sense to people that know Java and I'm writing this quick guide because it was requested. Also, I'm quite sure that OSBot will add proxy feature in the client itself soon. NOTE: There's a small problem. You are setting the proxy to the whole application, so all tabs ran in this client will use the same ip/proxy. Solution: Run multiple clients. NOTE2: People is saying that proxies dont work. You are using dead/slow proxies that you probably found in free lists. You will never be able to bot with that. You need to buy premium lists/private proxies. I turned one of my vps into a proxy (temporarily) so you know that good proxies work well with little latency: -DsocksProxyHost=atscripts.servebeer.com -DsocksProxyPort=69 People saw it worked perfectly so I'm removing it now STEP #1 -Make a new folder -Copy latest osbot client into the new folder -Rename osbot client to "osbot.jar" STEP #2 -Open Notepad -Paste this text on it @echo off java -DsocksProxyHost=PROXY_IP -DsocksProxyPort=PROXY_PORT -jar osbot.jar pause -If you dont want the black cmd window to show, you can use replace "java" with "start javaw" -Replace "PROXY_IP" and "PROXY_PORT" for your respective proxy ip/port. Example: -Save As -> "anyname.bat" (Select all types) -You can simply edit it anytime you want by right-click and chose "Edit" STEP #3 -Double-click the .bat file to open osbot using the proxy. -If you get an error saying "'java' is not a recognized command blablabla", edit your .bat file and do this: -If you get an error saying 'unable to find "osbot.jar" blabla, you probably fucked up renaming osbot.jar and you renamed it to osbot.jar.jar because your OS isnt configured to show all file extensions. FAQyou Q.This guide only shows how to do it on Windows, how can we do it in our operating systems? A.Google. Q.Where can I get Socks5 proxies? A.Google. Q.Why are you so sexy? A.Google.
  7. Ladies and gentlemen, if you didn't already know, OSBot 2 has been under private BETA testing for a week now. Currently people with access are developers, moderators, and $100+ donors. OSBot 2 is nearly finished for final release, we're currently writing all the random event solvers for the public release. Expect a public release within the coming days... OSBot 2 is nearly ready for adoption. Thanks, Sincerely, Laz and the OSBot Team.
  8. The OSBot methods are slow and unreliable so I wrote my own. Thanks to @TheScrub for cluing me in on what interface in the bank had the items! public boolean bankContains(int item) { for (Item i : sI.client.getInterface(12).getItems(6)) { if (i != null && i.getId() == item) { return true; } } return false; } public boolean bankContains(String item) { for (Item i : sI.client.getInterface(12).getItems(6)) { if (i != null && i.getName().equalsIgnoreCase(item.toLowerCase())) { return true; } } return false; } public boolean rightClickBankItem(int item) throws InterruptedException { if (!bankContains(item)) { return false; } int slot = sI.client.getBank().getSlotForId(item); if (!sI.client.getBank().isSlotVisible(slot)) { sI.client.getBank().scrollToSlot(slot); } Rectangle rect = sI.client.getBank().getAbsoluteSlotPosition(slot); sI.client.moveMouseTo(new RectangleDestination((int) rect.getX(), (int) rect.getY(), (int) rect.getWidth(), (int) rect.getHeight()), false, true, true); return sI.client.isMenuOpen(); } public boolean rightClickBankItem(String item) throws InterruptedException { if (!bankContains(item)) { return false; } int slot = sI.client.getBank().getSlotForId(sI.client.getBank().getItemForName(item).getId()); if (!sI.client.getBank().isSlotVisible(slot)) { sI.client.getBank().scrollToSlot(slot); } Rectangle rect = sI.client.getBank().getAbsoluteSlotPosition(slot); sI.client.moveMouseTo(new RectangleDestination((int) rect.getX(), (int) rect.getY(), (int) rect.getWidth(), (int) rect.getHeight()), false, true, true); return sI.client.isMenuOpen(); } public boolean selectOpenMenuOption(String option) throws InterruptedException { if (sI.client.isMenuOpen()) { List<Option> options = sI.client.getMenu(); for (int i= 0; i < options.size(); i++) { if (options.get(i).action.equalsIgnoreCase(option.toLowerCase())) { return sI.client.moveMouse(new RectangleDestination(sI.client.getMenuX(), sI.client.getMenuY()+19+(i*15), sI.client.getMenuWidth(), 15), false); } } } return false; } public boolean withdraw(int id, int amount) throws InterruptedException { if (!bankContains(id)) { return false; } if (rightClickBankItem(id)) { if (sI.client.isMenuOpen()) { List<Option> options = sI.client.getMenu(); for (int i= 0; i < options.size(); i++) { if (options.get(i).action.equalsIgnoreCase("withdraw-" + amount)) { return sI.client.moveMouse(new RectangleDestination(sI.client.getMenuX(), sI.client.getMenuY()+19+(i*15), sI.client.getMenuWidth(), 15), false); } else if (options.get(i).action.equalsIgnoreCase("withdraw-x")) { sI.client.moveMouseTo(new RectangleDestination(sI.client.getMenuX(), sI.client.getMenuY()+21+i*14, sI.client.getMenuWidth(), 10), false, true, false); sI.sleep(MethodProvider.random(615, 963)); sI.client.typeString(Integer.toString(amount)); return true; } } } } return false; } public boolean withdraw(String name, int amount) throws InterruptedException { if (!bankContains(name)) { return false; } if (rightClickBankItem(name)) { if (sI.client.isMenuOpen()) { List<Option> options = sI.client.getMenu(); for (int i= 0; i < options.size(); i++) { if (options.get(i).action.equalsIgnoreCase("withdraw-" + amount)) { return sI.client.moveMouseTo(new RectangleDestination(sI.client.getMenuX(), sI.client.getMenuY()+21+i*14, sI.client.getMenuWidth(), 10), false, true, false); } else if (options.get(i).action.equalsIgnoreCase("withdraw-x")) { sI.client.moveMouse(new RectangleDestination(sI.client.getMenuX(), sI.client.getMenuY()+19+(i*15), sI.client.getMenuWidth(), 15), false); sI.sleep(MethodProvider.random(615, 963)); sI.client.typeString(Integer.toString(amount)); return true; } } } } return false; }
  9. 1 point
    Closed on request, if you need anything else let me know.
  10. Total worth is above. Your logic to try and prove that you didn't scam is flawed as well. (You sold the account, so you got money there + the money you scammed). It all makes sense and you're a scammer. I don't know if what he's saying is 100% true but it seems like it is. All I know is the account was recovered by a third party source which has to be you (unless you lied about being the only owner) and that he shouldn't take a loss for that so you will be forced to refund what he says is lost.
  11. hope it fails and bans legit players, big streamers (sparc mac etc)
  12. 1 point
    Yeah, I'm kind of disappointed that you aren't.
  13. 1 point
    Right now and always.
  14. 1 point
    1) Use breaks. 2) Bot in cold spots. Avoid hot spots like Rock crabs, yaks, woodcutting yews/magics, ect. 3) Ever once in awhile do some of the work yourself. Try talking ingame when something fails i.e. if constantly getting hit during combat try saying "omfg" 4) If you're going to bot overnight, minimize activity during the day. It'll give jagex the sense of you're sleeping at that time instead. 5) After about a long 7-8 days of botting, stay offline for a day or two. Mimicking a player giving the game a break because he's bored of it. 6) After a long time training a certain skill, do another skill or go do minigames/pk/ect for 10-20 mins. 7) Anti-bans such as moving the camera every once in awhile and looking at current xp ARE A JOKE. The only real good anti-ban is looking like a legitimate player, i.e. Every click having a different interval time, sometimes mis-clicking (slightly more mis-clicking after a long game session as a way to show a player is tired), ect. 8) DO NOT turn very defensive if someone calls you a bot. Make them feel stupid instead. i.e.: Good: Snitch: Player1 is a bot Player1: huh? no? Snitch: Yes you are, you're just babysitting Player1: alright dude, whatever you say. Bad: Snitch: Player1 is a bot. Player1: STFU, I'm not a bot. f**git. Snitch: You're awfully defensive about it, babysitter.
  15. 1 point
    It's not over yet.
  16. lets be honest its called a donation on the website but as all businesses, it functions like one.
  17. you can set your own terms when buying/selling accounts, just be smart.
  18. I'm stuck in a parking lot. Dead tire and low on 'E'. Pretty sure AAA ran out so I'm may to have to pay for towing. Fml
  19. I like the tities in your ava.
  20. seems that the people complaining all have a 'anime' based image, could be just a coincidence but its still weird.
  21. Sure, that doesn't mean I want to see it every second I'm on this website though.
  22. even more reason for an 18+ section where this sort of stuff can be put.. to prevent anyone seeing anything they dont want to. There could also be a filter on certain signatures. And a warning on those that are classed as 'pornographic' when you try to view them.
  23. assuming ur referring to a dds stake and using the staff of dead, u cant use the staff of dead special if "Magic" is toggled off nah dude, the stats picture and the quests picture are really small. calm down please.
  24. 1. I bot in world 1 2. I bot 24/7 on my main, risking $500 3. I don't bitch about ban waves 4. I don't do drugs =no bans
  25. I blew up the picture of the stats, the quests are too blurry when blown up
  26. I did this. Was fun watching each one disconnect one after each other every 5 minutes. Good experiment.
  27. Tip 5) Don't bot 20 yew choppers on 1 PC and wonder how they noticed.
  28. 1 point
    That's not what you said on Skype bae. ;)
  29. PVP world. Pest Control. Fight Caves. No randoms ^
  30. It should stop trying to log in after a few failed attempts.
  31. Inception is one of my favourite movies. :lol:
  32. Ill help you bud if theres questin Simon. I love you
  33. Good luck spamming a thread now.
  34. 1 point
    Who is solstice?
  35. Personally I don't understand why people get piercings, so I would recommend taking that shit out.
  36. OSBot 2 has been emulating one of my oldest scripts yet with great success.
  37. 1 point
    uhhh what bot you using? I may use it to gold farm.
  38. 1 point
    Poor guy who lost his stuff thinks otherwise.
  39. 10, got one of ur scripts & it got me banned right away after 2 hours using
  40. LOL! As if 10 messages is a lot. Get over it broski, you write a script and have it paid you better know you're gonna be answering many questions during the day.
  41. 2Gp For 2 defence, seems reasonable. oh there's already been a bid nvm.

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.