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.

Naked

Suspended
  • Joined

  • Last visited

Everything posted by Naked

  1. lol I wasn't going to discuss it until it was finished, but I'm rewriting my dashboard in node.js
  2. Java 8 or 10? Ya need 8
  3. I get that on occasion on Windows. There isn't a limit. Seems to be random when CPU/memory usage is high. Generally have 100 bots going on a single machine. No issues.
  4. I getcha. Odd that you get banned twice a day. I've only noticed the 8:00GMT wave affecting me. Side question: how bandwidth-efficient is your unlocked? I'm using lots of data when unlocking. It's crazy.
  5. My guess is the scaling takes time. Hard to watch 500 bots go through tut+qp. I have one server I do tut+qp on because it's easier to watch.
  6. We aren't pals, buddy
  7. Why so low gp/day given the quantity? I'm facing some scalability issues myself, but expecting 200m/day at your scale, even with the issues.
  8. Was going to do that for dashboard v2 (when I launch more p2p). Didn't have the willingness or time to learn yet. It's fairly basic and unimpressive, but it gets the job done. I might post a screenshot later, but I'll have to redact some stuff.
  9. Obligatory "don't bot if you don't want to get banned." Also, don't bot and play manually in the same day.
  10. 1. Multiple powerful machines. 2. No. 3. Everyone keeps their providers secret. 4. It's expensive to get started. Very expensive.
  11. Php backend (side note, php is awful). I use wmic to shutdown a specific bot (less overhead). Still working on fixing a few bugs. It's almost done and ready for scaling, hopefully. Looks terrible on mobile. Didn't realize. Will fix
  12. Made a web based dashboard for all of my farm statistics. More importantly, I can make any adjustments (turn a server on/off, change prioritization, etc) with a single click.
  13. Why do I feel like PENROSE is the type to catcall a woman on the street?
  14. Locks are pretty brutal. Working on a few methods to try to mitigate these to a manageable amount.
  15. Naked replied to Malcolm's topic in Spam/Off Topic
    I see you're a fan of my Naked AntiBan
  16. Potatoes do not think well. I'll have to check the GP/hr of potatoes. It'd be worth the loss just for the memes. YOU WERE WARNED ABOUT THE POOR FORMATTING. I fixed it. Naked AntiBan best script ever First update added. General status for everyone interested.
  17. Room gets toasty with computer exhaust, so at least part of the time, yes.
  18. Welcome to my Goldfarming Thread! I'm going to keep the goals short, sweet, and simple for now. The goal of this is nothing more than to farm lots and lots of gold primarily through F2P, as automated as possible and all written myself. DAILY GOALS 10M/DAY 25M/DAY 50M/DAY 100M/DAY 250M/DAY 500M/DAY 1000M/DAY TOTAL GOALS 100M 250M 500M 1000M 5000M 10000M Updates will be at milestones and random achievements. UPDATE 01/18/19 Figured I'd do the first update to show where I'm at currently. Farm features in no particular order: Full database integration - This is actually my middleware for the entire thing. Tut -> 7QP -> farming AIO - A few bugs here and there. About 97% of bots get through with no issues (besides locks). Automated Unlocking - Speaks for itself. Automated Muling - Currently only up to tier 1 mules. I trade over manually before the morning ban waves. I'm looking into the different methods of expanding the capacity farm, and how I'm most comfortable doing so. Updates will be made when the time comes. At this current moment, we're able to comfortably run 75-100 bots with no issues. UPDATE 01/22/19 Locks are bad right now. There is a certain rate I can unlock, and we're getting locks at an insane rate, making it difficult to field the account number necessary. To fight this, I'm throwing out the unlocker method and trying a few different methods to not only reduce locks but possibly speed up the entire questing process altogether. UPDATE 02/07/19 Quick update: it's going pretty damn well. I haven't worked on scaling much, but I don't have any issues in its current configuration (~100-125 bots). I'll probably be scaling within the next few weeks once I test a few things to better optimize/reduce costs. I'm specifically looking at proxies, fixing a few really minor bugs, etc. Hoping to pass 250M total shortly, and very close to 50M a day as well. One of the optimizations is getting accounts back into the action faster after ban waves, including training, which can really slow things down. UPDATE 04/02/19 So the farm in this thread was F2P, which is notorious breadcrumbs (but cheap to run) compared to P2P. I got a bit distracted with automating tutorial accounts (shameless plug) and haven't worked on farming much. As that is looking pretty damn good (minus the UX at the moment), I'll be transitioning into farming more in P2P and would like to document that as well (peer pressure is the best motivation). As with all things, I want this farm to be massive and overkill to the highest degree. So the question becomes - should I continue on this thread or create a new one with new huge goals, lessons learned, and a clearer P2P stance? If a new thread, I'd also like any naming suggestions, because I'm not very unique. Most creative wins. Let me know in the poll.
  19. If only by a few hours. In my experience, their software flags you, their team bans you once they're in the office
  20. Naked replied to extatus's topic in Scripting Help
    I'm not sure. I would suggest CLI and a login handler. You'd probably find this one fairly easy to integrate: You can pass the user/pass as a script parameter.

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.