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.

Gabriel Ramuglia

Members
  • Joined

  • Last visited

  1. What is PA? hw mouse is for stealth injection. no need to use it for mirror.
  2. You could use sandboxie instead of a VM. Definitely use one or the other due to random.dat
  3. If the goal is to sell the accounts as F2P trade-restrictions-removed accounts, why bother putting membership onto the accounts? Just bot some stuff in f2p that doesn't earn much money, but builds up some stats. Then you don't have to earn back the bond cost. It's hard to avoid bans on brand new accounts while doing efficient money makers.
  4. That's stupid. A stick of ram uses like 3w. A fully loaded server like the above will be like 200w under heavy load, closer to 100w idle. Yeah this is much better than the first one you looked at. Dual E5-2680v4 would be even better and should cost about the same. 450w is fine.
  5. Most useful post ever. Exactly what I was looking for.
  6. You still need help with this? I have a solution.
  7. Don't you literally just talk to one NPC with the correct items in inventory and then the quest is done?
  8. nice
  9. The github link doesn't work?
  10. Another way to do it is with scroll wheel up or down, provided the mouse is onscreen: if (zScale > 500) { ctx.log("Z scale > 500. Zooming out. 181 is max zoom out. 1448 is max zoom in). "); if (ctx.getMouse().isOnScreen()) { ctx.getMouse().scrollDown(); sleep(rand(50,150)); ctx.getMouse().scrollDown(); sleep(rand(50,150)); ctx.log("Former Z scale = " + zScale + ". New Z scale = " + thisCamera.getScaleZ()); } } else if (zScale < 300) { ctx.log("Z scale < 300. Zooming in. 181 is max zoom out. 1448 is max zoom in). "); if (ctx.getMouse().isOnScreen()) { ctx.getMouse().scrollUp(); sleep(rand(50,150)); ctx.getMouse().scrollUp(); sleep(rand(50,150)); ctx.log("Former Z scale = " + zScale + ". New Z scale = " + thisCamera.getScaleZ()); } } else { ctx.log("Z scale = " + zScale); }
  11. "Misthalin Mystery", 1535
  12. Can you provide an example of this? Edit: it was easier to just refactor the code to not extend methodprovider, and have all of the functions expect you to pass in the methodprovider context as an argument.
  13. It also types the names of the items and buys the items super quickly, which is unrealistic. Also, the prices it types in are fully random, which is also unrealistic. Users who are trying to pay 13k for a 5k value item aren't going to type out 12,392. Most of the time they might type in 12,400, 12,000, or 13,000. If you must type in a random number for the price, it should be a rounded number at least half the time. Hitting +5% a couple of times for most items is a more human way to buy when you don't mind overpaying. I understand that's not always enough to successfully get an item, so it would require falling back to the old method if the item doesn't buy right away. Not sure if you do this already, but items bought should be bought in a random order. Make a "shopping list" of items to buy, then randomly sort the list, and then buy the items one at a time from the list. If every time a bot does quest X, it buys 7 things in the exact same order, the odds that a human will buy those 7 exact things from the GE in that exact order is almost zero. Especially if combined with any other type of bot profiling, it would be rather simple to detect that your quest bot is running. Especially if there are other ways to complete the quest by buying 6 or 8 things instead, the odds someone buys the 7 items from the GE, in that order, for totally random typed prices way above the list price. purchased at superhuman speed.... you get the idea.
  14. Just clicking the start script option within the script selector within osbot. Actually, I have started osbot with -allow norandoms edit: Starting osbot without "-allow norandoms" and stealth quester was able to load.

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.